washingtonpost.com articles render briefly and then turn white
Categories
(Core :: Graphics, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox72 | --- | affected |
People
(Reporter: cpeterson, Unassigned)
References
()
Details
Steps to reproduce
- Enable
fission.autostart
and restart - Load https://www.washingtonpost.com/climate-environment/2019/11/05/ok-boomer-year-old-lawmaker-shuts-down-heckler-during-climate-change-speech/
Expected result
The page should load and can be read and scrolled.
Actual result
The page loads and renders to the screen for half a second, but then the page turns white.
AFAICT, this happens on any washingtonpost.com article page, but not on the home page https://www.washingtonpost.com/ or subsections like https://www.washingtonpost.com/climate-environment/.
Is this a duplicate of bug 1586519 or white YouTube player bug 1565786? I didn't move my browser window or switch tabs, which were part of those bugs' STR.
Comment 1•5 years ago
|
||
Seems to work fine for me in nightly 2019-11-03 (which the about dialog reports is up to date, but I suspect updates were disable for display list bug) on macOS.
Comment 2•5 years ago
|
||
Same result in 2019-11-06 via mozregression.
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Timothy Nikkel (:tnikkel) from comment #1)
Seems to work fine for me in nightly 2019-11-03 (which the about dialog reports is up to date, but I suspect updates were disable for display list bug) on macOS.
I don't think this is a Fission bug. I can reproduce this problem with or without Fission. I just happened to see this problem immediately after enabling Fission. I can't reproduce in a clean profile, so I need to debug what is unique about my main profile.
I'm running Windows 10.
Reporter | ||
Comment 4•5 years ago
|
||
This problem was user error. I had disabled all cookies for washingtonpost.com (weeks ago) and that seems to have confused some new script. Once I accepted washingtonpost.com cookies, the page loaded correctly.
When the page loads, I see the expected content for a moment, but then some script loads and unloads the content. The devtools inspector shows no content in the <body> and the body size as 1535x0.
Description
•