-
-
Notifications
You must be signed in to change notification settings - Fork 717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maplibre GL Layers Not Printing in Firefox #3076
Comments
Can you try and print the webgl test page with Firefox compared to other browsers? |
Chrome does print the WebGL element: Firefox does not print the WebGL element: This appears to be a known issue in Firefox as recorded here. However, in that discussion a comment is made that setting Thank you for your assistance in tracking this down. Would it be appropriate to add a note about this somewhere in the README? |
Possibly related or the same issue: webcompat/web-bugs#111887 |
I'm not sure where you would place that info, maybe in the comments of the |
Feel free to open a PR here, I'm not sure where I'd put this info though... |
Closing this issue, if anyone would like to open a PR to improve the docs, feel free to do so. |
maplibre-gl-js version: 3.3.1
browser: Firefox
Steps to Trigger Behavior
Link to Demonstration
A thorough test was done by @gavin-maps from the
esri-leaflet-vector
project. The results can be seen here.The same behavior can be seen on the MapLibre GL JS Documentation. Printing in Chrome / Safari / Brave works, but not Firefox. I do not notice this same behavior with other instances of
canvas
elements, so I do not believe the issue is directly with the element type.I believe there is some issue within Firefox which distinguishes it from the other browsers, but perhaps there is something within the MapLibre GL JS project which can also be changed to accommodate Firefox.
Expected Behavior
Printing a page with a MapLibre GL rendered map will be successful.
Actual Behavior
Printing a page with a MapLibre GL rendered map shows up as a grey background.
The text was updated successfully, but these errors were encountered: