MapsGL maps.google.com renders blurry on machines Chrome doesn't allow MapsGL enabling on

NEW
Unassigned

Status

()

Core
Canvas: WebGL
5 years ago
3 years ago

People

(Reporter: Ioana (away), Unassigned)

Tracking

8 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(5 attachments)

(Reporter)

Description

5 years ago
Created attachment 656852 [details]
MapsGL screen shot

Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 (20120829042009)

STR:
1. Load http://maps.google.com in the browser.
2. Enable MapsGL.
3. Search for a location, or just zoom in on the map.

Actual Results:
The map elements (including text) are blurry. I could track this issue back to Firefox 8.0 - couldn't convince it to use MapsGL on the older versions. It works the same on the 08/30 Beta, Aurora, and Nightly.

I could only reproduce this issue on a machine for which Google Chrome gives the following message when trying to enable MapsGL:

"We detected that your computer does not meet the system performance requirements for MapsGL. Learn more about the system requirements for MapsGL"


about:support Graphics section:

Adapter Description  Tungsten Graphics, Inc -- Mesa DRI Intel(R) G41 x86/MMX/SSE2
Vendor ID  Tungsten Graphics, Inc
Device ID  Mesa DRI Intel(R) G41 x86/MMX/SSE2
Driver Version  2.1 Mesa 8.0.2
WebGL Renderer  Tungsten Graphics, Inc -- Mesa DRI Intel(R) G41 x86/MMX/SSE2 -- 2.1 Mesa 8.0.2
GPU Accelerated Windows  0    
AzureCanvasBackend  cairo
AzureFallbackCanvasBackend  none
AzureContentBackend  none
This is related to, if not the same bug as 779822.
See Also: → bug 779822
I think this is probably Google's bug. If they don't support MapsGL on Intel hardware in Chrome, they shouldn't for other browsers too. Probably UA sniffing is what's going on here.

I'm not sure we can do anything here.
We may be giving the wrong data back for something like max texture size.

How does that machine do on this conformance suite:
https://www.khronos.org/registry/webgl/conformance-suites/1.0.1/webgl-conformance-tests.html
Ioana, can you please run the WebGL conformance tests Jeff called out in comment 3 on the machine you reported this bug? Please report your results here when complete. Thanks.
QA Contact: ioana.budnar
(Reporter)

Comment 5

5 years ago
I ran the WebGL conformance suite on the same machine and 8862 of 8882 passed.
Twenty tests failed with the following output:

conformance/textures/texture-size-cube-maps.html (342 of 362 passed)

    failed: 0, 0, 2, 1 should be blue
    failed: 0, 1, 2, 1 should be yellow
    failed: 0, 0, 2, 1 should be yellow
    failed: 0, 1, 2, 1 should be green
    failed: 0, 0, 2, 1 should be cyan
    failed: 0, 1, 2, 1 should be blue
    failed: 0, 0, 2, 1 should be green
    failed: 0, 1, 2, 1 should be cyan
    failed: 0, 0, 2, 1 should be blue
    failed: 0, 1, 2, 1 should be green
    failed: 0, 0, 2, 1 should be cyan
    failed: 0, 1, 2, 1 should be magenta
    failed: 0, 0, 2, 1 should be magenta
    failed: 0, 1, 2, 1 should be yellow
    failed: 0, 0, 2, 1 should be red
    failed: 0, 1, 2, 1 should be cyan
    failed: 0, 0, 2, 1 should be yellow
    failed: 0, 1, 2, 1 should be red
    failed: 0, 0, 2, 1 should be cyan
    failed: 0, 1, 2, 1 should be yellow

Comment 6

4 years ago
I noticed today that Google Maps are unreadable in Firefox, and users can no longer opt out of MapsGL. Is this bug the right place for the issue illustrated by the two attached screen captures?

Comment 7

4 years ago
Created attachment 8385077 [details]
Google Maps as seen in Firefox

Comment 8

4 years ago
Created attachment 8385079 [details]
Google Maps as seen in Internet Explorer
(In reply to Jerry Baker from comment #6)
> I noticed today that Google Maps are unreadable in Firefox, and users can no
> longer opt out of MapsGL. Is this bug the right place for the issue
> illustrated by the two attached screen captures?

I think what you're seeing is slightly different. Based on the screenshots you've provided text isn't as crisp on Firefox as compared to IE. If you look at the original screenshot attached to this bug you'll see that the text rendering is completely broken, which is what this bug is meant to report.

That said, this is a long standing bug. It's probably worth it for you to file a new bug and report your hardware, driver versions, and an ouput of Graphics from about:support.

Comment 10

3 years ago
I can confirm this bug on FF 30 , Ubuntu 13.10, NVidia G86 with nvidia-319 (319.32)

Comment 11

3 years ago
Created attachment 8448762 [details]
Google maps on FF

Comment 12

3 years ago
Created attachment 8448763 [details]
Google maps on Chromium

Comment 13

3 years ago
I can confirm the same issue that Rodrigo and Jerry are seeing, but not the one Ioana reported initially (That is, text is blurry, but not rendered in a strange, bold font). 
Firefox 33.1.1, on arch linux, in a thinkpad x220 with  Intel HD Graphics 4000.
I tested on chromium 38.0.2125.122 and no rendering issues there.

Should a new bug be opened for this second issue? Or is it likely to be related to the original issue? Is the original issue still a problem? it was reported 2 years ago...

Comment 14

3 years ago
Further information, someone on this thread seems to think it has to do with subpixel rendering:
https://productforums.google.com/forum/#!topic/maps/y0WbYyqdKxA

I should also mention that in my case WebGL is working both on firefox and chromium, so my case does not fall under the category of "machines Chrome doesn't allow MapsGL enabling on". Further reason to open this as a separate bug?
You need to log in before you can comment on or make changes to this bug.