Use new user activation API for notification permission dialog
Categories
(Core :: DOM: Push Subscriptions, task, P1)
Tracking
()
People
(Reporter: annevk, Assigned: johannh)
References
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
As Edgar wrote in bug 1591718 comment 11:
I expect that replacing the
UserActivation::IsHandlingUserInput()
call in ContentPermissionRequestBase with new API in the document should just work.
This would likely fix an active regression on twitter.com (please verify), maybe elsewhere, and is in general a thing we want to be doing.
This probably does not warrant an intent to ship, if indeed it's as straightforward as it seems.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Comment 3•5 years ago
•
|
||
Backed out changeset 209adca8625c (bug 1606839) for multiple failures on browser_permissions_handling_user_input.js
Failures logs: - bc2 https://treeherder.mozilla.org/logviewer.html#?job_id=284850396&repo=autoland
- c2 https://treeherder.mozilla.org/logviewer.html#?job_id=284849976&repo=autoland
- ss https://treeherder.mozilla.org/logviewer.html#?job_id=284866347&repo=autoland
Johann can you please take a look?
Assignee | ||
Comment 5•5 years ago
|
||
Edgar, I would have expected E10SUtils.wrapHandlingUserInput
to set UserActivation::IsHandlingUserInput()
like it does with isHandlingUserInput but it seems like that's not the case yet. Is there already a mechanism to artificially set user activation for tests or would you like me to add one?
Comment 6•5 years ago
|
||
(In reply to Johann Hofmann [:johannh] from comment #5)
Is there already a mechanism to artificially set user activation for tests or would you like me to add one?
There is a chrome only api in document, you could use it to set user activation for tests.
Assignee | ||
Comment 7•5 years ago
|
||
Ah, thanks!
Updated•5 years ago
|
Updated•5 years ago
|
Comment 9•5 years ago
|
||
bugherder |
Assignee | ||
Comment 10•5 years ago
|
||
Comment on attachment 9119765 [details]
Bug 1606839 - Use new user activation API for guarding notification permission prompts. r=edgar,Ehsan
Beta/Release Uplift Approval Request
- User impact if declined: Well-meaning sites which fail to capture user interaction correctly do not get the more prominent notification permission prompts, e.g. twitter.com
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: See bug 1591718
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is a simple change that simply loosens some restrictions around notification prompting, with tests.
- String changes made/needed: None
Assignee | ||
Updated•5 years ago
|
Comment 11•5 years ago
|
||
Comment on attachment 9119765 [details]
Bug 1606839 - Use new user activation API for guarding notification permission prompts. r=edgar,Ehsan
Fixes a regression causing some push notification prompts to not appear on popular sites like Twitter. Approved for 73.0b7.
Comment 12•5 years ago
|
||
bugherder uplift |
Updated•5 years ago
|
Comment 13•5 years ago
•
|
||
Reproduced the initial issue using release version 72.0.1
Verified - Fixed in latest Beta build 73.0b7 (Build id: 20200118195856) and latest Nightly build 74.0a1 (Build id: 20200119213718) using Windows 10, Ubuntu 18.04 and Mac OS 10.15
Description
•