[Webkit-unassigned] [Bug 33479] Replacing hidden element causes first-child selector to behave weirdly
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Mar 13 22:03:28 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=33479
--- Comment #1 from Joseph Pecoraro <joepeck at webkit.org> 2010-03-13 22:03:28 PST ---
Created an attachment (id=50668)
--> (https://bugs.webkit.org/attachment.cgi?id=50668)
[REDUCTION] Simple HTML/CSS/JS Showing The Problem
Attached a simpler reduction. Whenever a new first child element is inserted
into a :first-child position where a :first-child selector has display:none,
then any existing element affected by the :first-child selector is not updated
correctly. Notes: This is not specific to <td>s. The exact same problem
happens with :last-child and inserting the new element as the last child
(appendChild instead of insertBefore). I did not test :only-child.
--
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