[Webkit-unassigned] [Bug 28365] run-in vanishes when placed inside list-item

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Aug 16 16:49:15 PDT 2009


https://bugs.webkit.org/show_bug.cgi?id=28365


Dave Hyatt <hyatt at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hyatt at apple.com




--- Comment #1 from Dave Hyatt <hyatt at apple.com>  2009-08-16 16:49:14 PDT ---
The marker is put inside the run-in since it begins life as a block.  When the
run-in morphs to become an inline, we only pick up one child from the block. 
This is because the loop is buggy in handleRunInChild... it needs to cache
nextSibling before advancing.

However markers aren't supposed to end up inside inline children.  The final
marker placement should actually be inside the block that the inline runs in
to.

getParentOfFirstLineBox could be modified to skip run-ins that are going to
successfully run in, but then the run-in code has to make sure that children
are added after pre-existing markers.  (I think it needs to do this anyway, in
the case where the block you run into is a list-item itself).

Basically there are a bunch of bugs here.

-- 
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