Skip to content

[cssom] Ambiguous double negation in serialize a selector #6926

@cdoublev

Description

@cdoublev

I'm really sorry to add another issue on top of an ever growing stack, especially if it should have been more obvious to me than it is right now, because english is not my native language or because I'm missing some skills, but does the definition of step 2 in CSSOM - Serialize a selector targets a simple selector (<type-selector> or <subclass-selector>) that is a <type-selector> whose <ns-prefix> is omitted (default namespace)?

Otherwise, for each simple selector in the compound selectors that is not a universal selector of which the namespace prefix maps to a namespace that is not the default namespace serialize the simple selector and append the result to s.

I'm also aware that there might be some reasons to keep such a wording.

EDIT:

I'm now more confortable with the terminology used in Selectors and Namespaces, and I understand that the above quote means "for each simple selector in the compound selectors, except an universal selector qualified with a namespace that is not the default namespace, serialize the simple selector and append the result to s.

I guess this wording is used because of the definition of a default namespace and "no namespace", which are different things.

I let this issue open in case you would decide that this wording deserves to be improved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions