833623 - cannot print webGL content with HTML element

Status: NEW

(Core :: Printing: Output, defect)

Description

[dchan]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17

Steps to reproduce:

goto http://www.playmapscube.com/
hit ctrl-P or print preview


Actual results:

The preview did not represent the original viewport.


Expected results:

it should match the original view.

Comment 1

[dchan]

Another example

goto maps.google.com and enable mapsGL
hit print preview, you will see that only the map viewport is shown.

Comment 2

[Benoit Jacob [:bjacob] (mostly away)]

Worrying indeed; tagging webgl-conformance to ensure it doesn't fall too far off the radar; don't think that's a too big stretch to call that a conformance bug.

Comment 3

[Benoit Jacob [:bjacob] (mostly away)]

Vlad's LayerScope seems like it would be the right tool to investigate this.

Comment 4

[Paul Silaghi, QA [:pauly]]

Cannot reproduce on FF 18.0.1 on Ubuntu 12.04 x86. Anyway, this might be a more general issue - bug 628978

Comment 5

[dchan]

Attachment: screen shot of print preview pringint webGL with html

Comment 6

[dchan]

attach is the print preview of http://www.playmapscube.com/ with firefox 18.0.1 on linux.  Paul can you describe what is not reproducible ?

Comment 7

[Paul Silaghi, QA [:pauly]]

(In reply to dchan from comment #6)
> attach is the print preview of http://www.playmapscube.com/ with firefox
> 18.0.1 on linux.  Paul can you describe what is not reproducible ?
Sorry, I misunderstood the issue. I hit print preview after clicking start the game.
I confirm the issue on Nightly 21.0a1 (2013-01-28) Win 7 x64

Comment 8

[Mats Palmgren (inactive)]

http://www.playmapscube.com/ is 404.

goto maps.google.com and enable mapsGL

How do I "enable mapsGL" on maps.google.com?

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The severity field for this bug is set to S3. However, the following bug duplicate has higher severity:

• Bug 1853101: S2

:jwatt, could you consider increasing the severity of this bug to S2?

For more information, please visit BugBot documentation.