-
Notifications
You must be signed in to change notification settings - Fork 647
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
[css-display] Do empty text nodes generate text runs? #1808
Comments
The behavior of Firefox looks like a bug. The script doesn't add any white space characters that should be taken into account by |
That's super weird, and it's definitely a bug. Different DOMs that output the same source code should not result in different CSS output, ever. @SelenIT ::before { content: '' } is a little different, it causes the ::before pseudo-element to exist, and empty inline boxes count as content that causes a line box to exist. |
They do, but shouldn't they be treated as "not existing for any other [than positioning out-of-flow descendants] purpose" phantom line boxes? |
@fantasai If I understand correctly, you mean that
Is that correct? |
@Loirooriol A |
@SelenIT That depends on if they are assigned any other styles. :) |
Do text nodes with an empty string value generate a text run or not?
The difference will affect run-in layout:
And it's also observable in flow layout. According to CSS 2.2,
I guess "text" refers to text runs. See https://jsfiddle.net/rs94bpay/
Firefox does not discard the line because of the text node, Chrome and Edge do.
The text was updated successfully, but these errors were encountered: