Re: Issue 39044 in chromium: -webkit-backface-visibility not applied

[chro...@googlecode.com]

Comment #2 on issue 39044 by olivier.suritz: -webkit-backface-visibility
not applied
http://code.google.com/p/chromium/issues/detail?id=39044

Safari 4 on Mac works fine for me (i.e. it correctly implements the
-webkit-backface-visibility), as expected given
that Apple itself provides the sample.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #3 on issue 39044 by pkinlan: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

On my Version 4.0.5 (5531.22.7) for Mac the back of the card is visible.

[chro...@googlecode.com]

Comment #4 on issue 39044 by pkinlan: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

The attached image is safari.

Attachments:
Picture 5.png 19.0 KB

[chro...@googlecode.com]

Comment #5 on issue 39044 by cabelsasser: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

This bug still exists even in the latest Chrome developer build (5.0.342.9).

It's really affecting a page we're working on, and since we can't test
around it — webkitBackfaceVisibility behaves
totally normal and returns the right values, just doesn't render properly —
it's driving us nuts. :)

[chro...@googlecode.com]

Comment #6 on issue 39044 by cabelsasser: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

(And in regards to pkinlan comments -- this bug definitely does _not_
appear in Safari.)

[chro...@googlecode.com]

Comment #7 on issue 39044 by pkinlan: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

That screenshot was from safari.. You must be on a slightly different
version as it definatly appears and it
also appears on the cube demos on the web.

It indicates it is likely a webkit issue rather than a chrome only issue.

[chro...@googlecode.com]

Comment #8 on issue 39044 by cabelsasser: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

A-ha!

This works great in Safari 4.0.5 (6531.22.7) — Snow Leopard — but it does
not seem to work in Safari 4.0.5
(5531.22.7) — Leopard.

That at least means it has been fixed, but I admit I don't know how often
Chrome syncs up with WebKit...?!

Attachments:
Snow.png 44.4 KB
Leo.png 71.5 KB

[chro...@googlecode.com]

Comment #9 on issue 39044 by pkinlan: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

Cool - good investigation. I will speak internally to see if I can see
what is happening. (I need the bug fixed).

Just to clarify - I am on Leopard.

[chro...@googlecode.com]

Comment #10 on issue 39044 by cabelsasser: -webkit-backface-visibility not
applied
http://code.google.com/p/chromium/issues/detail?id=39044

I filed a bug with Apple regarding the Leopard / Snow Leopard discrepancy.

They said: "Backface-visibility is only supported when
ACCELERATED_COMPOSITING is enabled,
and in that situation it works. ACCELERATED_COMPOSITING is disabled on
Leopard, depending on the
QuickTime version."

pkinlan, I don't know if this helps you, but it's probably a good place to
start:

Does Chrome support ACCELERATED_COMPOSITING?

Webkit Bug Reference: https://bugs.webkit.org/show_bug.cgi?id=24571

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

[chro...@googlecode.com]

Comment #15 on issue 39044 by samh1...@gmail.com:

-webkit-backface-visibility not applied
http://code.google.com/p/chromium/issues/detail?id=39044

Still an issue in 18.0.1025.168 but only on certain computers. Sporadic.
Adding --enable-accelerated-compositing is not an acceptable solution, as
web developers working on major client-facing sites can't expect users to
run Chrome that way.

This is definitely not fixed

[chro...@googlecode.com]

Comment #16 on issue 39044 by jan.pta...@gmail.com:

-webkit-backface-visibility not applied
http://code.google.com/p/chromium/issues/detail?id=39044

Version 20.0.1132.57 on a mac
Google Chrome is up to date.

needed to use threaded compositing & accelerated animation in
chrome://flags/

[chro...@googlecode.com]

Comment #17 on issue 39044 by John.Pap...@gmail.com:

-webkit-backface-visibility not applied
http://code.google.com/p/chromium/issues/detail?id=39044

Version 22.0.1229.79 on Win7: this is not fixed.

I am seeing *some* of the content through the back face. Giving the element
opacity: 0.99 fixes the problem (i.e. none of the content bleeds through
the back face any more).

[chro...@googlecode.com]

Comment #20 on issue 39044 by lyndonn....@gmail.com:

-webkit-backface-visibility not applied
http://code.google.com/p/chromium/issues/detail?id=39044

Version 25.0.1364.160 Ubuntu 13.04

bug still exists

Attachments:
snapshot1.png 39.7 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings