When allowing the library to create a new window, the window title is initially empty. Even if the calling code uses SetTitle ASAP, there is a period of time (between the window being created and the browser instance finishing being initialised) when the window title has no text. This is problematic for accessibility clients (e.g. screen readers), as users will be informed about the presence of an untitled window.
It would be good for WebViewOptions to accept a WindowTitle string, allowing the window title to be set as early as possible.
When allowing the library to create a new window, the window title is initially empty. Even if the calling code uses
SetTitle
ASAP, there is a period of time (between the window being created and the browser instance finishing being initialised) when the window title has no text. This is problematic for accessibility clients (e.g. screen readers), as users will be informed about the presence of an untitled window.It would be good for
WebViewOptions
to accept aWindowTitle
string, allowing the window title to be set as early as possible.