Closed
Bug 1222261
Opened 10 years ago
Closed 10 years ago
Github doesn't display properly when Nightly is in e10s mode.
Categories
(Core :: DOM: Security, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: husseydevin, Unassigned)
References
()
Details
Attachments
(1 file)
|
164.13 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20151105030433
Steps to reproduce:
I opened https://github.com/ or any subpage in Firefox Nightly 45.0a1 with e10s enabled.
Nightly 45.0a1 (2015-11-05)
OS X 10.10.5
MacBook Mid-2009 (MacBook5,2)
Actual results:
Github displays with no page resources, leaving plain HTML (see screenshot). It looks as if it is in View > Page Style > No style, however it is disabled.
Log in the console (under Security):
19:52:53.488 None of the "sha256" hashes in the integrity attribute match the content of the subresource.1 github.com
Expected results:
GitHub should load properly and display its JavaScript and CSS.
GitHub displays properly in Safari 9.0.1 (10601.2.7.2), Firefox 42.0, and Nightly when e10s is disabled.
No extensions were installed.
For some reason, https://help.github.com/ and its subpages work.
I also reported this to GitHub.
Comment 1•10 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
20151105030433
Works for me.
(In reply to Devin Hussey from comment #0)
> It looks as if it is in View > Page Style > No style, however it is disabled.
Do you mean “Basic Page Style” is selected?
| Reporter | ||
Comment 2•10 years ago
|
||
Yes. Basic Page Style is selected.
| Reporter | ||
Comment 3•10 years ago
|
||
And no messages are in the JS console when e10s is disabled.
| Reporter | ||
Comment 4•10 years ago
|
||
I just got an email from a GitHub support person saying it is working fine in 64-bit Linux. Can someone try 64-bit Windows? Maybe it only affects 32-bit.
| Reporter | ||
Comment 5•10 years ago
|
||
It seems to be working now.
| Reporter | ||
Comment 6•10 years ago
|
||
OK. It wasn't working in the 11/5 build but it is working in the 11/6 build.
Whatever the heck it was, it is fixed.
| Reporter | ||
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•