[Webkit-unassigned] [Bug 45095] absolutely positioned list in inline element crashes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Sep 2 08:29:54 PDT 2010


--- Comment #4 from Shinichiro Hamaji <hamaji at chromium.org>  2010-09-02 08:29:55 PST ---
Thanks for your review!

> The comment says the the first found node is used, but you changed it to be the first found node that is rendered as a block. Why is this the right thing to do? What if the document element itself is not a RenderBlock? Can this function return 0?

I think we still have <html> as the last block element? Can this be missing or inline? I think I've never seen the case where the HTML element is inline, but of course I may be wrong. If I'm wrong, Could you tell me how I can make the root element inline? I've updated the comment for now.

By the way, I don't really know what we should do when there are no <ul> and <ol>. I guess this case is not specified well. FYI, Firefox seems to output "0", not "II" for the test case. If we should prefer Firefox's behavior, I'll update my patch. I like the current WebKit's behavior though.


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