Ok, I'll add a string to Oxide so that we don't break existing apps.
I'll add a deprecation warning for this as well.
I'm just about to merge Chromium 51.0.2679.0 in to trunk. There are a
couple of test failures until this is resolved.
** Changed in: oxide
Importance: Undecided => High
** Changed in: oxide
Status: New => Triaged
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
Triaged
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
