[Webkit-unassigned] [Bug 88908] [chromium] webkit-backface-visibility doesn't work with <video>

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 13 18:01:25 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=88908





--- Comment #13 from James Robinson <jamesr at chromium.org>  2012-06-13 18:01:24 PST ---
(In reply to comment #12)
> (In reply to comment #11)
> > (In reply to comment #10)
> > > Some possibilities:
> > >   - canvas 2d might not actually use a separate m_layer and m_contentsLayer ?
> > >   - by fluke, maybe the test cases you set up are not triggering accelerated compositing?
> > 
> > There's a min size for a canvas to be accelerated right? Might be that as well.
> 
> Indeed in my particular example the canvas 2d doesn't create a separate m_contentsLayer (even with compositing forced).

Accelerated 2d canvas is blacklisted in chrome on linux (poor driver quality), so that might explain it if you're testing on linux.  Check about:gpu to see what you are getting (and if you are brave, try --ignore-gpu-blacklist)
> 
> It so-happened that with the WebGL example I created, the snapshot of the backface-visibility that the contents layer did happened before the parent was initialized to the value specified in the HTML.  In principle though, any dynamic change of the backface-visibility would have doomed the patch.
> 
> A patch which has the contents layer reach into its parent layer to determine its visibility produces the correct results and is robust to dynamic changes.  I'll upload once I've cleaned it up (then we can torch it for structural reasons).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list