---
description: This is a continuation of the ICoreWebView2NewWindowRequestedEventArgs interface.
title: WebView2 Win32 C++ ICoreWebView2NewWindowRequestedEventArgs2
ms.date: 05/04/2023
keywords: IWebView2, IWebView2WebView, webview2, webview, win32 apps, win32, edge, ICoreWebView2, ICoreWebView2Controller, browser control, edge html, ICoreWebView2NewWindowRequestedEventArgs2
---

# interface ICoreWebView2NewWindowRequestedEventArgs2

[!INCLUDE [deprecation-note](../includes/deprecation-note.md)]

```
interface ICoreWebView2NewWindowRequestedEventArgs2
  : public ICoreWebView2NewWindowRequestedEventArgs
```

This is a continuation of the ICoreWebView2NewWindowRequestedEventArgs interface.

## Summary

 Members                        | Descriptions
--------------------------------|---------------------------------------------
[get_Name](#get_name) | Gets the name of the new window.

## Applies to

Product                         | Introduced
--------------------------------|---------------------------------------------
WebView2 Win32            |    1.0.992.28
WebView2 Win32 Prerelease |    1.0.1010

## Members

#### get_Name

Gets the name of the new window.

> public HRESULT [get_Name](#get_name)(LPWSTR * value)

This window can be created via `window.open(url, windowName)`, where the windowName parameter corresponds to `Name` property. If no windowName is passed to `window.open`, then the `Name` property will be set to an empty string. Additionally, if window is opened through other means, such as `<a target="windowName">...</a>` or `<iframe name="windowName">...</iframe>`, then the `Name` property will be set accordingly. In the case of target=_blank, the `Name` property will be an empty string. Opening a window via ctrl+clicking a link would result in the `Name` property being set to an empty string.

The caller must free the returned string with `CoTaskMemFree`. See [API Conventions](/microsoft-edge/webview2/concepts/win32-api-conventions#strings).

