Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread MiB
nov 19 2013 15.10 Barney Carroll: > On 19 November 2013 14:01, MiB wrote: > I can't vouch for hover as I don't see this element to begin with in Chrome > 31. > > That's very interesting. This is what I get: > http://www.youtube.com/watch?v=QNyGy47YNHc It seems turning off all add-ons make i

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread Barney Carroll
Footnote to this particular X-File: I've seen cases before where people would encounter a Chrome rendering bug and be unable to reproduce the bug on jsfiddle or Codepen – maybe the solution is to sniff for the version number in the user agent and then wrap the contents in an iframe? ;P Regards, Ba

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread David Hucklesby
On 11/19/13, 6:01 AM, MiB wrote: nov 19 2013 14.55 Barney Carroll: David has discovered a bug in Chrome 31 whereby rules featuring concurrent positioning pseudo-classes on the same element are removed from the DOM when the affected element is hovered. I can't vouch for hover as I don't see

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread Barney Carroll
On 19 November 2013 14:01, MiB wrote: > I can't vouch for hover as I don't see this element to begin with in > Chrome 31. > That's very interesting. This is what I get: http://www.youtube.com/watch?v=QNyGy47YNHc Regards, Barney Carroll barney.carr...@gmail.com +44 7429 177278 barneycarroll.c

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread MiB
nov 19 2013 14.55 Barney Carroll: > David has discovered a bug in Chrome 31 whereby rules featuring > concurrent positioning pseudo-classes on the same element are removed from > the DOM when the affected element is hovered. I can't vouch for hover as I don't see this element to begin with in

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread Barney Carroll
tl;dr: David has discovered a bug in Chrome 31 whereby rules featuring concurrent positioning pseudo-classes on the same element are removed from the DOM when the affected element is hovered. In his example, you can see this happen by hovering over the second list item and watching the caret disapp

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread Tom Livingston
Disappears on hover in Mac Chrome 31. On Sun, Nov 17, 2013 at 11:11 PM, David Hucklesby wrote: > Developing a drop-down menu, I'm following an idea I came across that adds a > marker to a menu item that has a following sub-menu[1]. It uses this > selector > that works in CSS3 browsers: > > .nav l

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread MiB
18 nov 2013 kl. 05.11 skrev David Hucklesby: > While this works in modern browsers, the marker disappears in Chrome v.31.0 > for > Mac. In this simplified Pen, it disappears on :hover. With slightly more > complex > CSS it does not appear on Chrome at all. (Okay on Chrome for Windows.) David,

Re: [css-d] Chrome for Mac disowns children

2013-11-19 Thread MiB
nov 18 2013 05.11 David Hucklesby: > If you have Chrome on a Mac, I'd be grateful if you let me know whether you > see > this phenomenon. Could be something to do with my install (on Mavericks, > FWIW). Works in Chrome 29. _

Re: [css-d] Chrome for Mac disowns children

2013-11-18 Thread David Hucklesby
On 11/17/13, 9:52 PM, Karl DeSaulniers wrote: On Nov 17, 2013, at 11:32 PM, Barney Carroll wrote: This sounds uncannily familiar to Georg's reported bug for Chrome v31 3 days ago on this list whereby stateful re-rendering didn't happen. His example involved invisible checkboxes expanding conte

Re: [css-d] Chrome for Mac disowns children

2013-11-18 Thread Chris Rockwell
It *does* work on Version 33.0.1712.0 canary, Windows 7 - maybe the bug has been fixed. On Mon, Nov 18, 2013 at 12:52 AM, Karl DeSaulniers wrote: > > On Nov 17, 2013, at 11:32 PM, Barney Carroll wrote: > > > This sounds uncannily familiar to Georg's reported bug for Chrome v31 3 > days ago on th

Re: [css-d] Chrome for Mac disowns children

2013-11-17 Thread Karl DeSaulniers
On Nov 17, 2013, at 11:32 PM, Barney Carroll wrote: > This sounds uncannily familiar to Georg's reported bug for Chrome v31 3 days > ago on this list whereby stateful re-rendering didn't happen. His example > involved invisible checkboxes expanding content via the :checked pseudo-class. > > My

Re: [css-d] Chrome for Mac disowns children

2013-11-17 Thread Barney Carroll
This sounds uncannily familiar to Georg's reported bug for Chrome v31 3 days ago on this list whereby stateful re-rendering didn't happen. His example involved invisible checkboxes expanding content via the :checked pseudo-class. My take on this is that the Chrome team did some aggressive over-opt

Re: [css-d] Chrome for Mac disowns children

2013-11-17 Thread Karl DeSaulniers
On Nov 17, 2013, at 10:11 PM, David Hucklesby wrote: > Developing a drop-down menu, I'm following an idea I came across that adds a > marker to a menu item that has a following sub-menu[1]. It uses this selector > that works in CSS3 browsers: > > .nav li a:first-child:nth-last-child(2) {...} >

Re: [css-d] Chrome for Mac disowns children

2013-11-17 Thread Chris Rockwell
Marker disappears on hover in chrome 31 on windows 7 also. I would try to help you debug, but all those positional selectors make my head hurt. I think it's cool for dev's to figure out what can be done, but I seriously hope I *never* have to debug a site with CSS like that :D On Sun, Nov 17, 2

Re: [css-d] Chrome for Mac disowns children

2013-11-17 Thread Philippe Wittenbergh
Le 18 nov. 2013 à 13:11, David Hucklesby a écrit : > While this works in modern browsers, the marker disappears in Chrome v.31.0 > for > Mac. In this simplified Pen, it disappears on :hover. With slightly more > complex > CSS it does not appear on Chrome at all. (Okay on Chrome for Windows.) >

[css-d] Chrome for Mac disowns children

2013-11-17 Thread David Hucklesby
Developing a drop-down menu, I'm following an idea I came across that adds a marker to a menu item that has a following sub-menu[1]. It uses this selector that works in CSS3 browsers: .nav li a:first-child:nth-last-child(2) {...} While this works in modern browsers, the marker disappears in Chro