Closed
Bug 1580072
Opened 5 years ago
Closed 5 years ago
History manipulation intervention
Categories
(Core :: DOM: Navigation, enhancement)
Tracking
()
RESOLVED
DUPLICATE
of bug 1515073
Webcompat Priority | ? |
People
(Reporter: karlcow, Unassigned)
References
()
Details
Not sure this is the right component.
See https://github.com/WICG/interventions/issues/21
and https://groups.google.com/a/chromium.org/forum/?#!msg/blink-dev/T8d4_BRb2xQ/WSdOiOFcBAAJ
https://bugs.chromium.org/p/chromium/issues/detail?id=907167
for background reading.
What's happening:
- A user goes to a site.
- The site creates two entries in the history
- The user taps/clicks the back browser button
Expected:
The users expect to return to the previous screen they have actually seen
Actual:
The users go to the previous page in the history (which sometimes recreates an entry on reload).
This creates webcompat report because it doesn't meet the expectations and/or it doesn't behave the same than in chrome.
Reporter | ||
Updated•5 years ago
|
See Also: → https://webcompat.com/issues/39484
Updated•5 years ago
|
Component: Networking → Document Navigation
Updated•5 years ago
|
Flags: needinfo?(bugs)
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(bugs)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•