This looks like a bug, which has finally been reported. If you add a CSS rule for divCombine CSS Attribute and Pseudo-Element Selectors?
anywhere in your stylesheet with at least one declaration, your divCombine CSS Attribute and Pseudo-Element Selectors?:after
rule will magically apply. For example:
div:after {
content: "NO";
}
divCombine CSS Attribute and Pseudo-Element Selectors? {
display: block;
}
divCombine CSS Attribute and Pseudo-Element Selectors?:after {
content: "YES";
}
See the updated fiddle.
It also seems to have something to do with your second div
having or not having certain HTML attributes, as shown in the comments below.