Last Comment Bug 705410 - CSS 3D photo rollover effect doesn't render correctly in Nightly
: CSS 3D photo rollover effect doesn't render correctly in Nightly
Product: Core
Classification: Components
Component: Layout: View Rendering (show other bugs)
: 11 Branch
: x86_64 Linux
-- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Jet Villegas (:jet)
Depends on:
  Show dependency treegraph
Reported: 2011-11-26 01:45 PST by blechri
Modified: 2011-12-21 14:17 PST (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

rollover.ogv (310.24 KB, application/octet-stream)
2011-11-26 01:45 PST, blechri
no flags Details

Description User image blechri 2011-11-26 01:45:34 PST
Created attachment 577044 [details]

User Agent: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:11.0a1) Gecko/20111126 Firefox/11.0a1
Build ID: 20111126041059

Steps to reproduce:

Tried the CSS3 3D transforms effect that is talked about and demoed here:
You can test it here:
I am using latest Nightly build on Linux (Ubuntu 11.10 - 64 bit)

Actual results:

The 3d effect does not look like the example on the demo page (which it does in google chrome on the same machine). I am attaching a screencapture of what it looks like.

Expected results:

It should look like the example in the video on the demo-page above.

I first thought it was related to the bug 701656 but that demo is now rendering correctly for me (except for opacity (no transperancy)), so this is probably unrelated.
Not sure what component to set this as.
Comment 1 User image Matt Woodrow (:mattwoodrow) 2011-11-28 13:46:56 PST
This is because the element with perspective (image3d) isn't a direct parent of the transformed element (img).

WebKit seems to be accepting this, which appears to be incorrect with the current spec.


I've sent an email to www-style to clarify whether this is a spec bug, or a WebKit bug.
Comment 2 User image Matt Woodrow (:mattwoodrow) 2011-12-21 14:17:15 PST
Removing tracking-firefox10 flag, since this the appears to be a problem with WebKit not following the spec.

Note You need to log in before you can comment on or make changes to this bug.