- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 27 Jan 2015 09:49:44 +1300
- To: Simon Fraser <smfr@me.com>
- Cc: "public-fx@w3.org" <public-fx@w3.org>, Greg Whitworth <gwhit@microsoft.com>
Received on Monday, 26 January 2015 20:50:12 UTC
We need a resolution here sooner rather than later, please. It'd be great if someone from the IE or Chrome teams could contribute to the discussion... A bug related to this issue just cropped up in the wild: https://bugzilla.mozilla.org/show_bug.cgi?id=1125767, http://jsfiddle.net/lastw/auv3x2y9/. In that bug, a filtered element E has an abs-pos descendant D for which E is not a containing block ancestor. In Gecko, D is cropped to E's bounds. In Chrome, D is not filtered. I think both of those behaviors seem wrong. Rob -- oIo otoeololo oyooouo otohoaoto oaonoyooonoeo owohooo oioso oaonogoroyo owoiotoho oao oboroootohoeoro oooro osoiosotoeoro owoiololo oboeo osouobojoeocoto otooo ojouodogomoeonoto.o oAogoaoiono,o oaonoyooonoeo owohooo osoaoyoso otooo oao oboroootohoeoro oooro osoiosotoeoro,o o‘oRoaocoao,o’o oioso oaonosowoeoroaoboloeo otooo otohoeo ocooouoroto.o oAonodo oaonoyooonoeo owohooo osoaoyoso,o o‘oYooouo ofooooolo!o’o owoiololo oboeo oiono odoaonogoeoro ooofo otohoeo ofoioroeo ooofo ohoeololo.
Received on Monday, 26 January 2015 20:50:12 UTC