w3c / fxtf-drafts

Mirror of https://hg.fxtf.org/drafts
https://drafts.fxtf.org/
Other
68 stars 49 forks source link

[css-compositing][css-masking] Force rendering whitespaces around combinators #523

Closed cdoublev closed 11 months ago

cdoublev commented 11 months ago

The basic syntax definition of <blend-mode> and <mask-layer> is rendered in browsers without a whitespace where the first line break of a <pre> appears in the Bikeshed source text:

<blend-mode> = ... |color-burn | ...
<mask-layer> = ... ||<repeat-style> || ...

I do not know why Bikeshed removes the line break therefore I am not sure this PR is appropriate.


<blend-mode> values have been grouped as in popular graphic design softwares.


Aside

I do not know if the missing whitespace is a syntax error, or if a css value definition parser should handle it.

initial-value (in @property) may support combinations in the future and authors may use line breaks in combinations.

The CSS value definition syntax may have to define if 1. one or more whitespaces and/or line breaks should always appear between symbols in combinations, or if 2. they can be omitted in some cases.

@property --custom {
  initial-value: "<foo><bar>"; /* valid? */
  initial-value: "foo\
    bar";                      /* valid? */
}
tabatkins commented 11 months ago

I suspect this is a Bikeshed bug, but in any case there's no reason to put text on the same line as the <pre> opening tag, that was an old pre-Bikeshed requirement.