Closed
Bug 1230716
Opened 10 years ago
Closed 10 years ago
WebGL renders certain content upside down on Windows
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: evanw, Unassigned)
Details
(Keywords: testcase, Whiteboard: [parity-chrome][parity-opera])
Attachments
(1 file)
|
7.44 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36
Steps to reproduce:
Open the attached file trace.html and view it in both Firefox (42.0) and Chrome (47.0.2526.73 m) on Windows. The attached file contains an extracted and reduced test case from our app (the WebGL design tool at figma.com). The machine is a HP Stream if that matters (http://store.hp.com/webapp/wcs/stores/servlet/ContentView?eSpotName=Stream11&storeId=10151).
Actual results:
Chrome renders right-side up while Firefox renders upside down. We've received a number of complaints from people using Firefox on Windows that the editor is unusable and were lucky enough to have a machine that reproduced the issue.
Expected results:
The Firefox rendering is wrong.
The graphics section of about:support says this:
Adapter Description: Intel(R) HD Graphics
Adapter Drivers: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
Adapter RAM: Unknown
Asynchronous Pan/Zoom: none
Device ID: 0x0f31
Direct2D Enabled: true
DirectWrite Enabled: true (6.3.9600.17999)
Driver Date: 8-28-2014
Driver Version: 10.18.10.3925
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 00000000
Supports Hardware H264 Decoding: true
Vendor ID: 0x8086
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0
Changing webgl.force-enabled and webgl-disable-angle to true makes the problem go away.
Comment 1•10 years ago
|
||
It looks like this was already fixed. Please test the current Firefox Developer Edition and reopen this report if you can still reproduce the issue.
https://www.mozilla.org/firefox/developer/all/
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0
20151029151421
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
20151203163240
Reproducible.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:44.0) Gecko/20100101 Firefox/44.0
20151204004006
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:45.0) Gecko/20100101 Firefox/45.0
20151203053521
Works for me, whether e10s is enabled or not.
Adapter Description: NVIDIA GeForce 210
Adapter Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM: 128
Asynchronous Pan/Zoom: none
Device ID: 0x0a65
Direct2D Enabled: true
DirectWrite Enabled: true (6.2.9200.17461)
Driver Date: 7-2-2014
Driver Version: 9.18.13.4052
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 34ee1458
Supports Hardware H264 Decoding: Yes
Vendor ID: 0x10de
WebGL Renderer: Google Inc. -- ANGLE (NVIDIA GeForce 210 Direct3D11 vs_4_1 ps_4_1)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Component: Untriaged → Canvas: WebGL
Keywords: testcase
Product: Firefox → Core
Resolution: --- → WORKSFORME
Whiteboard: [parity-chrome][parity-opera]
| Reporter | ||
Comment 2•10 years ago
|
||
Yes, it works for me in Firefox Developer Edition. Thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•