Bug 125080 - When preserve-3d is disabled due to the GPU, it should not be reported as supported
Summary: When preserve-3d is disabled due to the GPU, it should not be reported as sup...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: All Linux
: P1 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-02 10:40 PST by Gleb Smirnov
Modified: 2019-05-03 20:10 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gleb Smirnov 2013-12-02 10:40:58 PST
Overview: 

  On *some* linux boxes running on *some* GPUs preserve-3d is broken in Webkit and browsers based on it (Google Chrome, etc). While the browser recognizes this value for (-webkit-)transform-style, it actually fails to render the corresponding page. Works fine in Mac OS and Windows.

  So, webkit should either reject preserve-3d or render it properly.



Steps to reproduce:

  1) Get your hands on a linux box with a not-so-modern GPU (e.g. Gallium 0.4 on AMD REDWOOD)
  2) Run this fiddle: http://jsfiddle.net/bZ5sE/3/



Actual results:

  Only the text "Looks like we have preserve-3d support - you should see red text below"  is displayed. No red text below is seen.



Expected results:

  a) The text "Looks like we have preserve-3d support - you should see red text below" should be displayed. Below it "should be seen only if preserve-3d is supported" should be seen in red
    
  b) The text "Sad times looks like there is no preserve-3d support - the red text below is probably hidden because of the preserve-3d styles applied." Should be displayed, with no red text following.


Build Date & Platform:
  
  First time encountered, but not investigated somewhere in April of 2013, in Chromium on Linux, GPU unknown.

Additional Builds and Platforms:

  All tested Linux distros and all tested Webkit-based browsers. Except on a laptop packed with Intel HD Graphics 4000, where everything ran smoothly in all tested browsers.

Additional information:
  Related github issues: https://github.com/Modernizr/Modernizr/issues/1116, https://github.com/jmpressjs/jmpress.js/issues/133#issuecomment-29117140
Comment 1 Gleb Smirnov 2013-12-02 10:44:49 PST
Actually, is also reproduced on some Windows machines, see this report: https://github.com/jmpressjs/jmpress.js/issues/133#issuecomment-29392417
Comment 3 Simon Fraser (smfr) 2018-10-10 11:26:43 PDT
This means that whatever WebKit implementation you are running on these machines needs to turn off ChromeClient::ThreeDTransformTrigger on that hardware.