Zillow.com Lot Lines Do Not Render Correctly
Categories
(Web Compatibility :: Interventions, defect)
Tracking
(firefox88 wontfix, firefox89 wontfix, firefox90 wontfix)
People
(Reporter: mlammert, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
Go to zillow.com
Look up and address
View the location map
Turn on the lot lines feature
Actual results:
The lot lines appear but are all messed up. They are broken and fragmented. Zooming in and out of the map changes the severity of the broken lot lines.
This appears to be happening on Mac 10.14.6 and Windows 10.
Expected results:
The lot lines should appear correctly and not broken and fragmented.
Comment 1•3 years ago
|
||
Hi,
I was able to reproduce the issue on Windows 10 and MacOS 11 using Firefox 88, Firefox Beta 89 and Firefox Nightly 90.0a1.
I'm setting a component in order to involve the development team in reviewing this issue.
Thank you for reporting!
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3ef766b14c5f37e26fb2ce246443d5570703cfa2&tochange=714bfefe553a5f086fa8d753ede43a5c4a6c534a
If set extensions.webcompat.perform_injections to false and restart browser then the bug is no longer reproduced.
Updated•3 years ago
|
Comment 3•3 years ago
|
||
The original issue we're trying to address with this intervention is https://bugzilla.mozilla.org/show_bug.cgi?id=1662297, and this issue unfortunately still persists.
If you disable interventions, you'll notice that the whole map becomes incredibly slow, it allocates a lot of RAM, frequently even locking up the browser. Unfortunately, Zillow has not yet reacted to our outreach attempts, but we can't really disable that intervention because of the immense performance issues we'd run into. We pretty much have the choice between a sometimes a bit broken map, and a map that doesn't work at all and locks up the browser after a few seconds.
I have just re-pinged them. Since bug 1662297 is still open and is tracking the original issue we're workaround'ing here, I'll mark this as a "duplicate" of that, just so there's a link. We're constantly re-testing all interventions and will notice if it's no longer needed, but unfortunately, that's not the case at this time. :(
Updated•3 years ago
|
Updated•3 years ago
|
Description
•