1327927 - [e10s] only a small part of canvas is used in this testcase from http://js1k.com/ [minecraft]

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[arni2033]

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open http://js1k.com/2014-dragons/demo/1854 with minecraft landscape 
2. Reload the page using Ctrl+Shift+R

AR:  Canvas takes all free place on the page, however, landscape only appears in top left corner
ER:  Landscape should be stretched to the whole <canvas>, just like in IE, GoogleChrome and non-e10s

Notes:
1) This is unconfirmed, because WHO KNOWS, probably testcase is using something that was broken
   intentionally in e10s. Somebody (probably me?) will have to debug it first.
2) All testcases on js1k are extremely minimized, but this one has readable sources.
   My plan was (first) to reproduce the same bug using readable sources (second) and then debug it

Comment 1

[Loic]

I cant reproduce the issue with the latest Nightly.

Comment 2

[Simona Badau, Desktop QA]

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0

I'm also unable to reproduce this issue. Tested on Windows 7 x64bit using the latest Nightly 53.0a1 (Build ID: 20170103030204), Nightly 49.0a1 (Build ID: 20160526082509) and Firefox 50.1.0 release (Build ID: 20161208153507). I used the exact steps as in the Description while e10s was enabled. 

Arni2033, is this still reproducible for you on the latest Nightly or Firefox release?

Comment 3

[arni2033]

I figured out what happens.
Many demos on that site break when they're resized (separate bug in each demo,not worth reporting IMO)
The reason web page gets resized in e10s mode is that e10s shows notification "A web page is slowing down your browser", that resizes content area. This is similar (but not equal!) to bug 1327313.

Comment 4

[Simona Badau, Desktop QA]

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Build ID: 20170123030211

Closing this as Resolved Worksforme since I'm still unable to reproduce this issue when following the STR from the Description.

If anyone else can provide more useful information that could lead to reproducing this issue (on the latest Firefox versions), please reopen the bug.

Comment 5

[Firefox Bug Husbandry Bot]

Moving from Core::Untriaged to Core::General https://bugzilla.mozilla.org/show_bug.cgi?id=1407598