[Bug 12835] FIGCAPTION should be allowed to NOT be exactly first/last child of FIGURE ("The figcaption element" spec section)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=12835

--- Comment #15 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
The browser never has to find the image, it just walks the tree and renders it
wherever it is. The caption, though, might be something you need to find for
semantic reasons (e.g. an AT could read it out when requested).

Making the blank space not clickable seems like a styling issue.


> Besides, figure and figcaption are basically just block-level div tags with
> a semantic meaning -- who cares whether the browser "knows" that figcaption
> is a child of figure?

That's what it means for it to have "semantic meaning".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 12 November 2014 19:00:14 UTC