You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The caption IDL attribute must return, on getting, the first caption element child of the table element, if any, or null otherwise.
On setting, the first caption element child of the table element, if any, must be removed, and the new value, if not null, must be inserted as the first node of the table element.
The createCaption() method must return
the first caption element child of the table element, if any;
otherwise a new caption element must be table-created, inserted as the first node of the table element, and then returned.
The deleteCaption() method must remove the first caption element child of the table element, if any.
Compatibility
This is a bit of the dark part. It would be good to know, how many tables out there have multiple caption elements with different content. If it's very minor then probably, Safari and Chrome should align to Firefox behavior. If there are a significant number of them, changing the behavior of Chrome/Safari might loose information.
What is the issue with the HTML Standard?
This is an issue to determine if
Currently Firefox shows only one caption while Chrome and Safari show multiple, changing the layout.
Code:
Let's make a table with multiple captions:
Rendering:
Specification:
https://html.spec.whatwg.org/multipage/tables.html#the-caption-element
The table element is defined as:
https://html.spec.whatwg.org/multipage/tables.html#the-table-element
I wonder if the requirement is one and only caption if it should be clearly mentioned here. The
a caption
is vague.Then there is also this section which implies only one.
https://html.spec.whatwg.org/multipage/tables.html#dom-table-caption
Compatibility
This is a bit of the dark part. It would be good to know, how many tables out there have multiple
caption
elements with different content. If it's very minor then probably, Safari and Chrome should align to Firefox behavior. If there are a significant number of them, changing the behavior of Chrome/Safari might loose information.Probably a query could help with that.
WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=286661
The text was updated successfully, but these errors were encountered: