webbrowser-app currently doesn’t handle the empty mesage case. We could
make it handle it, of course, but I think your proposal of exposing the
stock message to the existing Oxide API makes sense, as it would mean no
API/behaviour changes.
** Also affects: webbrowser-app (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Apps bug tracking, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1556658
Title:
beforeunload handlers can't specify message text in Chromium 51
Status in Oxide:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
Chromium has dropped the ability for beforeunload handlers to set the
dialog message text. Instead, Chromium will display a stock message,
making it behave the same as Firefox. This will affect Oxide too -
beforeunload dialog components will be created with an empty message
string.
I assume webbrowser-app already handles an empty message string by
displaying its own text, but given that this API exists in Oxide, I
wonder whether we should specify a stock message in Oxide and expose
it via the existing API.
See:
https://chromium.googlesource.com/chromium/src.git/+/141dbc132f8aa2588fad4cf50fbfd7a319234b61
https://bugs.chromium.org/p/chromium/issues/detail?id=587940
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1556658/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-apps-bugs
Post to : ubuntu-apps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-apps-bugs
More help : https://help.launchpad.net/ListHelp
