-
Notifications
You must be signed in to change notification settings - Fork 0
HTML API: Implement active format reconstruction #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| * | ||
| * @see https://html.spec.whatwg.org/#reconstruct-the-active-formatting-elements | ||
| * | ||
| * @return bool Whether any formatting elements needed to be reconstructed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if false | int would be helpful, where we could return false or the number of reconstructed elements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you think of a case where it would be useful?
89a226f to
7939dcb
Compare
f412732 to
55e20cf
Compare
|
Superseded by WordPress#6982 |
Trac ticket: Core-61576
Adds support for active format reconstruction, which occurs when crossing certain HTML boundaries, such as when entering a new
Pelement which implicitly closed the previous one and all of the formatting elements inside it.This raises the question what to do when elements are implicitly created. This appears already with the unexpected
</p>, which creates an emptyPelement.next_tag()never finds these elements even though they appear in the breadcrumbs when moving past them.