Unrecognized embed elements should render with some sort of fallback content ("an indication that no plugin could be found for element, as the contents of element")
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: dholbert, Unassigned)
References
Details
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
Spinning this off from bug 1840788 comment 2.
STR:
- Load attached testcase.
EXPECTED RESULTS:
The embed element should render with some sort of indication that we could not find a plugin for the requested content.
ACTUAL RESULTS:
The embed element renders like an empty inline element, i.e. it's got zero width and no content and doesn't paint anything other than its border.
Quoting my notes from bug 1840788 comment 2 regarding the WHATWG html spec:
- It seems this corresponds to the scenario when the html spec's "Determine the type of the content" algorithm returns null (i.e. doesn't recognize the type).
- That makes the embed setup steps decide to "Display no plugin for element."
- The "Display no plugin" process says "Display an indication that no plugin could be found for element, as the contents of element.
(That seems to be calling for something along the lines of my "expected results" here, rather than rendering an empty element.)
There was some discussion in https://github.com/whatwg/html/issues/3876 about this too. qDot noted there that, when implementing our current behavior, they "didn't realize that was suppose to go to "unsupported plugin". That'll take a bit more logic on our end but I think is doable."
|
Reporter | |
Comment 1•1 year ago
|
||
|
|
Reporter | |
Updated•1 year ago
|
Description
•