nsWinMetroUtils GetSupported prop can't read the d3d registry key

VERIFIED FIXED in mozilla30

Status

defect
P1
normal
VERIFIED FIXED
5 years ago
28 days ago

People

(Reporter: jimm, Assigned: jimm)

Tracking

Trunk
mozilla30
x86_64
Windows 8.1
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: p=1 s=it-30c-29a-28b.3 r=ff30 [qa+])

Attachments

(1 attachment, 1 obsolete attachment)

990 bytes, patch
jimm
: review+
Details | Diff | Splinter Review
(Assignee)

Description

5 years ago
Should have caught this before this landed. ACCESS_WRITE does not imply ACCESS_READ.
(Assignee)

Updated

5 years ago
Assignee: nobody → jmathies
(Assignee)

Comment 1

5 years ago
Posted patch fix (obsolete) — Splinter Review
Attachment #8384914 - Flags: review?(tabraldes)
(Assignee)

Updated

5 years ago
Whiteboard: p=1
Attachment #8384914 - Flags: review?(tabraldes) → review+
(Assignee)

Comment 2

5 years ago
Posted patch exportSplinter Review
Thanks!
Attachment #8384914 - Attachment is obsolete: true
Attachment #8384935 - Flags: review+
(Assignee)

Updated

5 years ago
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/3b9d5ba3af0b
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Blocks: metrobacklog
QA Contact: kamiljoz
Whiteboard: p=1 → p=1 s=it-30c-29a-28b.3 r=ff30 [qa+]
Whiteboard: p=1 s=it-30c-29a-28b.3 r=ff30 [qa+] → p=1 s=it-30c-29a-28b.3 r=ff30
This will be tested at the same time as Bug #969831
Whiteboard: p=1 s=it-30c-29a-28b.3 r=ff30 → p=1 s=it-30c-29a-28b.3 r=ff30 [qa+]
Priority: -- → P1
Went through the verification process using the following Nightly build:
- http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014-03-06-03-02-01-mozilla-central/

- Set HKEY_CURRENT_USER/SOFTWARE/Mozilla/Firefox/MetroD3DAvailable = 0
- Once set, run firefox.exe from the command prompt and ensure that the above key stays "0" and not changing to "1"
- Also ensured that setting the reg key to "1" and running firefix.exe through the command prompt didn't change it back to "0"

Went through the above test case using both the X1 Carbon and the Surface Pro 2 without any problems.
Status: RESOLVED → VERIFIED

Updated

28 days ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.