Incorrect imagery display on Firefox

mapillary / mapillary-js

Interactive, extendable street imagery map experiences in the browser, powered by WebGL

https://mapillary.github.io/mapillary-js

MIT License

440 stars 84 forks source link

Incorrect imagery display on Firefox #462

Open willemarcel opened 3 years ago

willemarcel commented 3 years ago

Basic information

After some minutes of use of Mapillary website or using the Mapillary layer on iD editor (osm.org), the images start to be rendered incorrectly.

MapillaryJS version: current System/Browser: macOS BigSur / Firefox 91.0.1 (64-bit)

Steps to Reproduce Behavior

Go to the Mapillary website, start navigating on the images, or start using the Mapillary layer on osm.org iD editor.

Expected behavior

...

Actual behavior

oscarlorentzon commented 3 years ago

Thanks for reporting.

I cannot reproduce this behavior. Can you share more detailed steps or a screen capture showing how to reproduce? Can you share image IDs for areas where the problem occurs?

oscarlorentzon commented 2 years ago

@willemarcel Does this problem still occur?

willemarcel commented 2 years ago

@oscarlorentzon I used mapillary for a long time session today both in mapillary.com and in osm.org and the errors didn't happen.

willemarcel commented 2 years ago

The problem occurred 2 times again, but every time I try to record my screen, the error didn't happen.

oscarlorentzon commented 2 years ago

OK, thanks for notifying. It would be great if you could share an image ID/link next time it happens. A video (with Firefox dev tools opened) would also help.

oscarlorentzon commented 2 years ago

@willemarcel Can you make sure to open the developer tools in your browser the next time the error occurs and grab a screenshot of the console output? That would help with debugging.

Also, can you describe in more details the exact steps you take for the error to occur and provide an image ID? I can't seem to reproduce it.

willemarcel commented 2 years ago

Some images from errors in the console

This one happened in another session: