Bug 91509 - Formatting tags nested greater than 3 deep fail to close
Summary: Formatting tags nested greater than 3 deep fail to close
Status: RESOLVED DUPLICATE of bug 96385
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Eric Seidel (no email)
URL: https://dl.dropbox.com/u/175535/bugs/...
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-17 09:33 PDT by James Wheare
Modified: 2012-09-12 17:34 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Wheare 2012-07-17 09:33:59 PDT
Works fine with 3

<u>*<u>*<u>*</u></u></u> This is not underlined

Breaks with 4

<u>*<u>*<u>*<u>*</u></u></u></u> This *is* underlined </u></u></u></u></u></u></u></u></u> This is still underlined.

DOM structure ends up like this:

<u>*<u>*<u>*<u>*</u></u></u> This *is* underlined  This is still underlined.</u>

A closing </pre> tag clears the formatting.

This affects all formatting specific tags I tried, e.g. bold, italic, font, big, small, etc. Check URL https://dl.dropbox.com/u/175535/bugs/webkit/nested-formatting.html for test cases

This *does not* affect formatting applied via span style or class atrributes.

<a> tags are also unaffected.

Whether or not this is invalid, this
Comment 1 James Wheare 2012-07-17 09:35:40 PDT
Oops, truncated description.

Whether or not this is valid (doesn't make sense to nest <u> might make sense to nest <big/small> though) it seems like a pretty bad failure state.
Comment 2 James Wheare 2012-07-17 09:43:59 PDT
This also affects <font> tags, but only if all the nested tags are setting the same property.
Comment 3 Alexey Proskuryakov 2012-07-18 12:21:20 PDT
This changed in r103223. I don't know if this specific change is intentional, but it certainly doesn't match Firefox (I didn't test IE).
Comment 4 Eric Seidel (no email) 2012-09-12 17:34:48 PDT

*** This bug has been marked as a duplicate of bug 96385 ***