Aha, I see -- so you're saying "content:<image-url>" is expected to work on img-with-alt-text for the same reason that it's expected to work on e.g. span here (and it does work here): ``` data:text/html,<span style="content: url(https://www.w3.org/2008/site/images/logo-w3c-mobile-lg)">Fail ``` That makes sense to me, sure. > I think Chrome is wrong on those. Gotcha. Looking at your github issue, it looks like Tab disagrees, but there's at least agreement on the expectation that `content` should have the same effect across replaced elements. (What that effect is is the part that's up in the air - but you & he agree that it's reasonable to expect consistent results.) Given that.... for completeness, perhaps you could add a variant of your testcase `element-replacement-image-alt.html`, but: - testcase has no alt text - reference case is the same as the testcase, except with s/img/video/ - testcase maybe has a `<link rel="help">` (or some sort of reference) pointing at your github issue, as a callback to a spot where there's agreement that this styling should have the same effect on these elements (whatever the effect is)
Bug 1625805 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Aha, I see -- so you're saying "content:<image-url>" is expected to work on img-with-alt-text for the same reason that it's expected to work on e.g. span here (and it does work here): ``` data:text/html,<span style="content: url(https://www.w3.org/2008/site/images/logo-w3c-mobile-lg)">Fail ``` That makes sense to me, sure. > I think Chrome is wrong on those. Gotcha. Looking at your github issue, it looks like Tab disagrees, but there's at least agreement on the expectation that `content` should have the same effect across replaced elements. (What that effect is is the part that's up in the air - but you & he agree that it's reasonable to expect consistent results.) Given that.... for completeness, perhaps you could add a variant of your testcase `element-replacement-image-alt.html`, with these changes: - testcase has no alt text - reference case is the same as the testcase, except with s/img/video/ - testcase maybe has a `<link rel="help">` (or some sort of reference) pointing at your github issue, as a callback to a spot where there's agreement that this styling should have the same effect on these elements (whatever the effect is)
Aha, I see -- so you're saying "content:<image-url>" is expected to work on img-with-alt-text for the same reason that it's expected to work on e.g. span here (and it does work here): ``` data:text/html,<span style="content: url(https://www.w3.org/2008/site/images/logo-w3c-mobile-lg)">Fail ``` That makes sense to me, sure. > I think Chrome is wrong on those. Gotcha. Looking at your github issue, it looks like Tab disagrees, but there's at least agreement on the expectation that `content` should have the same effect across replaced elements. (What that effect is is the part that's up in the air - but you & he agree that it's reasonable to expect consistent results.) Given that.... for completeness, perhaps you could add a variant of your testcase `element-replacement-image-alt.html`, with these changes: - testcase has no alt text - reference case is the same as the testcase, except with s/img/video/ - testcase maybe has a `<link rel="help">` (or some sort of reference) pointing at your github issue, as a callback to a spot where there's agreement that this `content` styling should have the same effect on these elements (whatever the effect is)