Reloaded vogue.com article is blank (Uncaught DOMException: The operation is insecure)
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | wontfix |
| firefox147 | --- | wontfix |
| firefox148 | --- | fixed |
| firefox149 | --- | verified |
People
(Reporter: cpeterson, Unassigned)
References
(Regression, )
Details
(Keywords: regression, webcompat:platform-bug, webcompat:site-report)
User Story
user-impact-score:600 platform:windows,mac,linux,android impact:site-broken configuration:general affects:some branch:release diagnosis-team:dom
Steps to reproduce
- Load https://www.vogue.com/slideshow/the-best-street-style-photos-from-the-fall-2026-menswear-shows-in-milan
- Wait for the page to finish loading.
- Reload the page using Ctrl+R or Cmd+R.
Expected behavior
The reloaded page should look the same as before.
Actual behavior
The reloaded page is blank. The problem only seems to affect this one article. I can't reproduce on other vogue.com pages.
Here's a Firefox profile:
https://share.firefox.dev/462hcwu
I can reproduce in a clean Firefox user profile on Windows and macOS, even with ETP disabled and no ad blocker extensions. I can reproduce in builds as old as Firefox 135 (2025-02-04). I can't reproduce in Chrome or Safari.
The devtools console shows some interesting errors:
Too many calls to Location or History APIs within a short timeframe. 32 presenter-galleries.0d148fc8215652800cc9.js:378:3526
Uncaught DOMException: The operation is insecure.
Gt https://www.vogue.com/verso/static/presenter-galleries.0d148fc8215652800cc9.js:378
nu https://www.vogue.com/verso/static/1702.056344368fc03e871040.js:2
...
Comment 1•6 months ago
|
||
Regression window:
https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=1fc628c0a72ab96c716298834261229000f0ad5f&tochange=8cee2583590d6c07ae6f6cb21468e99a17617e94
Comment 2•6 months ago
|
||
:wwen, since you are the author of the regressor, bug 1913000, could you take a look?
For more information, please visit BugBot documentation.
Updated•6 months ago
|
Comment 3•6 months ago
|
||
If I disable the rate limit, I can't reproduce this issue.
This looks like the same issue as bug 1995636
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
| Reporter | ||
Comment 4•6 months ago
|
||
Resolving this bug as fixed. Bug 1995636 ought to fix this bug, though I'm no longer able to reproduce this bug, even in older builds.
Updated•6 months ago
|
Updated•6 months ago
|
Updated•5 months ago
|
Description
•