[css-values-5] referrerpolicy(), crossorigin(), and hyphens

[fantasai]

We currently define some URL modifier functions: https://drafts.csswg.org/css-values-5/#request-url-modifiers

They don't have hyphens. Should they? CC @annevk @SebastianZ @tabatkins @cdoublev

[SebastianZ]

Strong yes, they should have hyphens, from my side. We generally use hyphens in names and consider multi-word names missing them like currentColor and nowrap as mistakes.

Also, the keywords they take already do use hyphens. And we also have other function names like linear-gradient() etc. that have hyphens in their names. Plus, the header names like Referrer-Policy also use hyphens.

So I don't see any reason to write them without hyphens.

Sebastian

[annevk]

Yeah, probably. The HTML IDL attributes are spelled referrerPolicy and crossOrigin, which suggests we treat them as multiple words.

cc @noamr @nt1m @weinig

[noamr]

SGTM, the fact that they're missing hyphens is a syntax oversight, nothing with a strong intention.

[nt1m]

The crossorigin HTML attribute is one word, but I think that's because no HTML attribute is dash separated.

The HTTP header is dashed separated though. 🤷

[annevk]

That's the content attribute, I was talking about the IDL attributes, which do clearly indicate what we consider multiple words in HTML.

[astearns]

The CSSWG will automatically accept this resolution one week from now if no objections are raised here. Anyone can add an emoji to this comment to express support. If you do not support this resolution, please add a new comment.

Proposed Resolution: URL modifier functions cross-origin() and referrer-policy() should be hyphenated