Closed
Bug 1196452
Opened 10 years ago
Closed 9 years ago
Dev tools shows black when opened in docked mode on WebVR content.
Categories
(Core :: WebVR, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: caseyyee.ca, Unassigned)
References
Details
(Whiteboard: [webvr])
Attachments
(1 file)
|
104.22 KB,
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36
Steps to reproduce:
1. Download Firefox Nightly + WebVR addon (mozvr.com/downloads)
2. Navigate to www.mozvr.com, click on the goggles button to enter VR mode.
3. Open dev-tools using CTRL-SHIFT-I
Actual results:
Dev tools renders black in area where it should be docked.
It appears that dev tools is actually working. Mousing over the black area where the inspector is open, I get highlights in the window showing the element that I am inspecting.
Expected results:
Dev tools should be visible.
Related bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1188113
I should also mention that this also occurs on Mac. The work-around for now is to use devtools in detached/window mode.
Comment 3•10 years ago
|
||
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
Nightly 45.0a1 Build ID: 20151125030231
and Firefox 42.0
I am able to see the Dev tools.
@Casey, Are you still able to reproduce it in the latest version ?
Component: Untriaged → Developer Tools
Flags: needinfo?(caseyyee.ca)
Yes, this is still happening to me with the latest version:
45.0a1 (2015-11-26)
Flags: needinfo?(caseyyee.ca)
Updated•10 years ago
|
Comment 5•10 years ago
|
||
Changing the status to NEW as the issue still reproduces.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•9 years ago
|
||
This has been fixed with the WebVR 1.1 implementation.
Status: NEW → RESOLVED
Closed: 9 years ago
Component: DOM → WebVR
Resolution: --- → FIXED
Comment 7•8 years ago
|
||
I re-verified using Fx 57.0b5 and Fx 58.0a1 (build ID: 20171004100049) on Windows 10 x64 and I can confirm this issue is fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•