Open
Bug 1088196
Opened 11 years ago
Updated 3 years ago
Bogus JS 'resize' events are fired when transitioning a canvas between fullscreen modes.
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
NEW
People
(Reporter: jujjyl, Unassigned)
References
(Blocks 1 open bug)
Details
STR:
1. Visit https://dl.dropboxusercontent.com/u/40949268/emcc/bugs/bogus_resize_event.html
2. Click the button "Fullscreen bare" on the page.
3. Press esc to transition back to Windowed mode.
4. Open the web console and observe the results:
Observed: The web console prints something like in this image: https://dl.dropboxusercontent.com/u/40949268/emcc/bugs/bogus_resize_event_firefox.png
Note that there are two 'resize' events received for a unexplainable 1936x1056 size, and when transitioning back to windowed mode, the resize event for 300x300 is triggered twice.
The test in the page was conducted on a dualmonitor setup where the main monitor is of size 1920x1080, and a secondary monitor with size 1440x900, although suspecting that this does not matter.
Expected: The log should read
"TO FS: CSS size: 300x300, RTT Size: 300x300" bogus_resize_event.html:78
"RESIZED! New CSS size: 1920x1080, RTT Size: 300x300" bogus_resize_event.html:91
"RESIZED! New CSS size: 300x300, RTT Size: 300x300"
without extraneous resize events.
Not sure if I reported this to the proper Component, so please correct me if I got this wrong.
Comment 1•11 years ago
|
||
I expect that issue is that as we transition to fullscreen we do resize events in the usual way, which happens to be partway through the transition...
Component: Graphics → DOM
Comment 2•8 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
| Assignee | ||
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•