Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

content-inherit-002 test is wrong? #1133

Closed
hrj opened this issue Sep 30, 2016 · 3 comments
Closed

content-inherit-002 test is wrong? #1133

hrj opened this issue Sep 30, 2016 · 3 comments

Comments

@hrj
Copy link

hrj commented Sep 30, 2016

This test passes on Firefox but fails in Chromium.

According to the spec, content is not inherited, while the test checks for inheritance.

Hence, the test seems to be wrong.

@upsuper
Copy link
Member

upsuper commented Oct 3, 2016

"Inherited" field means whether the property is inherited by default. When inherit keyword is specified, it always inherit the value from its parent regardless of whether it is inherited by default. And apparently the test is trying to check whether inherit keyword works on content property.

However, the test is still wrong, because per spec, content is always computed to normal for elements, so ::after should inherit normal from its parent, rather than PASSED. And content: normal on ::after would be computed to none, thus no text should be showed there.

@gsnedders
Copy link
Contributor

Yeah, spec has changed since that test was written.

@wpt-issue-mover
Copy link
Collaborator

This issue has been moved to web-platform-tests/wpt#5495; please continue all discussion there.

@w3c w3c locked and limited conversation to collaborators Apr 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants