Open Bug 1645218 Opened 4 years ago Updated 5 months ago

Consider using UserActivation for back button intervention

Categories

(Core :: DOM: Navigation, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: johannh, Unassigned)

References

(Blocks 1 open bug)

Details

It looks like Chrome is using the same criteria as the UserActivation API, meaning that their interaction state does not include scrolling. Since this is a stronger protection we should probably convert to using that, too.

Type: defect → enhancement

Adam, it looks to me that your patch of Bug 1734181 does cover the integration with user interaction state. Should we close this bug as duplicate then?

Flags: needinfo?(avandolder)

Actually, my patch relies on the already existing method of tracking user interaction (https://searchfox.org/mozilla-central/source/dom/events/EventStateManager.cpp#913), which is separate from the UserActivation API, and so our interaction state does include scrolling. This seems like a reasonable followup, however.

Flags: needinfo?(avandolder)
You need to log in before you can comment on or make changes to this bug.