-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Report lack of support of preserve-3d in Chrome if it's disabled thanks to the GPU #1116
Comments
Have you reported this to crbug or webkit's bugzilla? |
@patrickkettner not as of yet, I'm still trying to figure out where exactly the problem lies. As soon as it's clear, I will do so. (I've also looked for open issues there, but found none) |
You already have a pretty reduced test-case. I wouldn't wait, personally. Could be something very simple for them to fix, always hard to tell without being intimately familiar with the guts of the browser. |
Corresponding issue on webkit bugzilla: https://bugs.webkit.org/show_bug.cgi?id=125080 (really did take me long) |
Did you open one up on crbug.com as well? |
beauty. thanks |
Unfortunately there isn't anything we can do in this case, as it is effectively a browser bug and only in certain situations ( not to mention that the GPU could crash in between the time that modernizr runs its test and your code runs ). Closing as a result, though am more than open to being persuaded otherwise. |
@patrickkettner yeah, it indeed can't be fixed by Modernizr. Pity, really, as nobody has reacted to the bugs I posted to Chromium/Webkit. Do you happen to know if there is some way I can get someone to look at it? (Yeah, I know I could look at it myself :) ) |
@paulirish may know someone, but its sortof a weird bug :/ The best thing we can do is to get as many people as possible to star the issue, as that is how google ranks its importance. |
I think the problem is due to the software renderer. In theory render of both hardware and software should produce exactly the same result. However it seems that 'preserve-3d' has not been implemented correctly in the software renderer which results in different outputs. |
(From #762 (comment))
There is a peculiar case of when the browser reports that it "supports" preserve-3d, but actually doesn't. Reproduces on most linux machines in Google Chrome.
The thing is that it does not render preserve-3d on some hardware.
See this test case:
http://jsfiddle.net/bZ5sE/3/ -- on my machine (see the configuration here: jmpressjs/jmpress.js#133) it says "Looks like we have preserve-3d support - you should see red text below", but the red text itself is not visible.
I do realize that this is likely a bug to be reported to Webkit/Chromium, but it could take ages before it's fixed, and everyone has updated. So a workaround is a good idea.
The text was updated successfully, but these errors were encountered: