New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
www.google.com – Unable to view user’s review photos #7299
Comments
There are missing steps, such as
I indeed get a spinner. This is not happening on desktop + responsive + chrome ua. It is working. I wonder if it's related to touchstart handling. |
ah no WebGL…
|
Maybe related to https://bugzilla.mozilla.org/show_bug.cgi?id=1341979 |
I've updated the issue with the correct link https://goo.gl/2SiYVI. It should work now. |
I can't even tap on the photos on my phone; it does nothing, including no messages being logged to the console. Desktop Firefox in responsive design mode does work, and the problem seems to be on actual Android devices, no |
Hmm. This is a weird one. The error is indeed what @karlcow reported: I've added some logging to see what the arguments are for the function call that's throwing the TypeError, and I saw this output:
So the first two times, the arguments are correct, but for the third call, the WebGLShader is null. However, it doesn't seem to be caused by nightly's shader validation, as turning on I wonder if it's related to the other warning I'm seeing logged: Also note that when I wrap the failing call in a try/catch block (and then do the same for the related errors which snowball from doing so), then the image seems to load just fine, so I wonder what the point of the shaders is. I'll see if I can't build a custom nightly that raises the limit to 16, as I see hints online that 16 may be the limit of WebGL contexts that Chrome enforces, rather than 2. |
Ah, indeed a custom build of Fennec with the WebGL context limit bumped up to 16 is able to view the page. I see that in the source code, the limit was set to 2 because some devices don't support more than 8 overall contexts, but if Chrome is now using a higher limit, then perhaps it would be better to adopt their heuristics in the interests of webcompat. I've filed bug 1421481 to investigate this. |
Thanks a lot. |
Update: https://bugzilla.mozilla.org/show_bug.cgi?id=1421481 has landed on inbound (likely in a Nightly within a day or two, unless it bounces) to match what Chrome Mobile is doing for contexts. |
I've just confirmed that the patch in the bug Mike just mentioned will fix the issue here. |
URL: https://google.com
Browser / Version: Firefox Mobile Nightly 55.0a1 (2017-06-06) - Chome UA
Operating System: Samsung Galaxy S6 (Android 7.0) - Resolution 1440 x 2560 pixels (~577 ppi pixel density)
Problem type: Mobile site is not usable
Steps to Reproduce
Expected Behavior:
Photo is displayed.
Actual Behavior:
Photo is not displayed. A loading spinner is displayed indefinitely.
Note:
06-07 15:06:02.180 15416-15499/? E/GeckoConsole: [JavaScript Error: "TypeError: Argument 1 of WebGLRenderingContext.shaderSource is not an object." {file: "https://www.google.ro/xjs/_/js/k=xjs.uv.en.YxCh7sJcVvA.O/m=v/rt=j/d=1/t=zcms/rs=ACT90oF0KsJ6_3uETvphxxHjmwteZ9W3EA" line: 462}] uv_.shaderSource@https://www.google.ro/xjs/_/js/k=xjs.uv.en.YxCh7sJcVvA.O/m=v/rt=j/d=1/t=zcms/rs=ACT90oF0KsJ6_3uETvphxxHjmwteZ9W3EA:462:420 uv_3x@https://www.google.ro/xjs/_/js/k=xjs.uv.en.YxCh7sJcVvA.O/m=sy13,syv,syz,sy1g,sy4e,whr/rt=j/d=0/rs=ACT90oF0KsJ6_3uETvphxxHjmwteZ9W3EA:44:306 uv_0x@https://www.google.ro/xjs/_/js/k=xjs.uv.en.YxCh7sJcVvA.O/m=sy13,syv,syz,sy1g,sy4e,whr/rt=j/d=0/rs=ACT90oF0KsJ6_3uETvphxxHjmwteZ9W3EA:44:446 uv_4x@https://www.google.ro/xjs/_/js/k=xjs.uv.en.YxCh7sJcVvA.O/m=sy13,syv,syz,sy1g,sy4e,whr/rt=j/d=0/rs=ACT90oF0KsJ6_3uETvphxxHjmwteZ9W3EA:44:611 uv_.im@https://www.google.ro/xjs/_/js/k=xjs.uv.en.YxCh7sJcVvA.O/m=sy13,syv,syz,sy1g,sy4e,whr/rt=j/d=0/rs=ACT90oF0KsJ6_3uETvphxxHjmwteZ9W3EA:80:129 uv_dC.prototype.Rb@https://www.google.ro/xjs/_/js/k=xjs.uv.en.Y
Watchers:
@softvision-sergiulogigan
@softvision-oana-arbuzov
sv; gs
From webcompat.com with ❤️
The text was updated successfully, but these errors were encountered: