-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is <slot> a replaced element or not? #564
Comments
There's disagreement between WebKit and Blink as to what is correct here. @rniwa et al feel quite strongly |
I think whether we treat |
When users specify an author rule, Does it mean I do not fully understand the impact of letting it being a replaced element. What is a user visible impact? |
@hayatoito It's stated in CSS Generated Content Module Level 3:
|
Thanks! Then, I propose the status quo; Regarding the current behavior in Blink, please do not take it seriously. No explicit intention there. |
Let me close this with status quo since this issue did not get the attention. |
Per the WHATWG HTML Spec, the
<slot>
element is listed in the section "Non-replaced elements". However, given its presentation hint (display: contents
), it seems that<slot>
might better be treated as a replaced element. Also Chrome 53+ seems have implemented it as such (::before
and::after
selectors no longer work on<slot>
)The text was updated successfully, but these errors were encountered: