ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: oxide
     Importance: Undecided
         Status: New

** Changed in: oxide
    Milestone: None => branch-1.15

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1556658

Title:
  beforeunload handlers can't specify message text in Chromium 51

Status in Oxide:
  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