Closed
Bug 1133099
Opened 9 years ago
Closed 9 years ago
[e10s] Add e10s feature detection to window.navigator
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla38
People
(Reporter: billm, Assigned: billm)
References
Details
Attachments
(1 file, 1 obsolete file)
3.01 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
With GDC coming up, there are probably going to be people who want to test our gaming performance in nightly. Since e10s is enabled on nightly, and some gaming features are broken in e10s (WebGL and pointer locking), those users not going to have a very good experience. The idea here is to add a short-term flag to window.navigator so that game developers can detect that nightly is running and suggest that the user switch to aurora. Right now the way this flag works is that it's only defined on navigator if the code doing the test is running in a content process. So it's totally invisible if we're not running in e10s mode. The name is subject to change :-). Not sure if we need a test for this.
Attachment #8564390 -
Flags: review?(jst)
Comment 1•9 years ago
|
||
Please drop "F**k"
Comment 2•9 years ago
|
||
just navigator.e10sEnabled ?
Comment 3•9 years ago
|
||
Also, why can't it just return true, given that it's only exposed in the content process?
Assignee | ||
Comment 4•9 years ago
|
||
New version. Here's a try push. https://treeherder.mozilla.org/#/jobs?repo=try&revision=0df1392f6cfe
Attachment #8564390 -
Attachment is obsolete: true
Attachment #8564390 -
Flags: review?(jst)
Attachment #8564454 -
Flags: review?(jst)
Updated•9 years ago
|
Attachment #8564454 -
Flags: review?(jst) → review+
Assignee | ||
Updated•9 years ago
|
tracking-e10s:
--- → +
Assignee | ||
Comment 5•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/514a4d642fd6
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → wmccloskey
Comment 6•9 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/514a4d642fd6
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•