beforeunload handlers can't specify message text in Chromium 51
Bug #1556658 reported by
Chris Coulson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Fix Released
|
High
|
Chris Coulson | ||
| webbrowser-app (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
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:/
https:/
Related branches
| Changed in oxide: | |
| milestone: | none → branch-1.15 |
Revision history for this message
| Olivier Tilloy (osomon) wrote | #1 |
Revision history for this message
| Chris Coulson (chrisccoulson) wrote | #2 |
| Changed in oxide: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| assignee: | nobody → Chris Coulson (chrisccoulson) |
| Changed in oxide: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
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.