- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 19 Oct 2016 21:13:48 +0000
- To: Geoffrey Sneddon <me@gsnedders.com>
- Cc: Ms2ger <ms2ger@gmail.com>, www-archive <www-archive@w3.org>
Received on Wednesday, 19 October 2016 21:14:27 UTC
This changed 3 years ago? And nobody implemented it in 3 years? While everyone had the opposite implemented? Isn't this a pretty clear sign that this change was wrong? On Wed, Oct 19, 2016 at 2:12 PM Geoffrey Sneddon <me@gsnedders.com> wrote: > As Ms2ger said, :first-child now matches elements without a parent > (technically, it matches elements without a parent and without a > previousElementSibling). > <https://www.w3.org/Style/CSS/Tracker/issues/317> is the issue that > led to the change, which was > < > https://github.com/w3c/csswg-drafts/commit/d57fda06a4f0aebb598e3341a2153bd958c171bc > >. > It seems to originate in feedback from bz, wondering why it doesn't > apply. > > /g > > On Wed, Oct 19, 2016 at 5:11 PM, Ian Hickson <ian@hixie.ch> wrote: > > Wow. What was the change, and why? > > > > On Wed, Oct 19, 2016 at 8:47 AM Ms2ger <ms2ger@gmail.com> wrote: > >> > >> Hey Hixie, > >> > >> There seems to have been a spec change on :first-child for elements > >> without a parent. Gecko implemented and started failing Acid3 test 35 > >> (see <https://bugzilla.mozilla.org/show_bug.cgi?id=1311329>). > >> > >> Could you update / disable the test? > >> > >> Thanks > >> Ms2ger > >> > > >
Received on Wednesday, 19 October 2016 21:14:27 UTC