Some web pages shown with a single dot only. Example: https://fromyouflowers.evyy.net/c/10579/79467/2009?SubID1=ebs3494535610sbe
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: jcurbaniak, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
Navigated to the site from www.rakuten.com and selected FromYouFlowers.com
Actual results:
blank screen with a border and just 1 central white dot pixel. Try this web address: https://fromyouflowers.evyy.net/c/10579/79467/2009?SubID1=ebs3494535610sbe
Expected results:
A picture I think.
Comment 1•5 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
| Reporter | ||
Comment 3•5 years ago
|
||
How do I get into safe mode? What is meant by a fresh profile?
Comment 4•5 years ago
|
||
I've tried to reproduce this on Linux, and the page seems to load fine for me.
There are instructions here for starting Firefox in troubleshooting mode:
https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
Updated•5 years ago
|
| Reporter | ||
Comment 5•5 years ago
|
||
I am still getting this error. Seems ok if I go direct to FromYouFlowers.com without going thru Rakuten.com first.
Comment 6•5 years ago
|
||
Please open about:support, click on "Copy text to clipboard" and paste it here. Thanks!
Can the website be fixed by scrolling or by zooming in? (bug 1732743 comment 6)
| Reporter | ||
Comment 7•4 years ago
|
||
In all cases it appears I was re-directed to cj.dotomi.com .
This is a marketing website apparently introduced by some malware in my computer.
I went to this site: https://malwaretips.com/blogs/remove-cj-dotomi-com/
and followed their suggestions.
Fortunately, the problem now appears corrected.
Definitely not a Firefox problem.
Thanks so much for all of the help.
Comment 8•4 years ago
|
||
Thanks for letting us know; I'll close this report, as it turns out not to be a Firefox bug after all. Glad you were able to resolve the problem!
Description
•