[css-properties-values-api] Add <string> as a supported syntax name #1103
Comments
|
@andruud @tabatkins does that sound good? |
|
Oh, huh, that's a weird omission. Yes, absolutely we should allow strings. |
|
For reference, Mozilla already added parsing Sebastian |
zrhoffman
added a commit
to zrhoffman/css-houdini-drafts
that referenced
this issue
Aug 3, 2023
zrhoffman
added a commit
to zrhoffman/css-houdini-drafts
that referenced
this issue
Aug 3, 2023
This was referenced Aug 3, 2023
zrhoffman
added a commit
to zrhoffman/wpt
that referenced
this issue
Dec 20, 2023
…Property Probably this should not be merged until w3c/css-houdini-drafts#1103 is resolved/the spec is updated. Interop bug: web-platform-tests/interop#389 Test coverage for `<string>` syntax in `CSS.registerProperty` is in wpt/pull#41308.
zrhoffman
added a commit
to zrhoffman/wpt
that referenced
this issue
Dec 20, 2023
…Property Probably this should not be merged until w3c/css-houdini-drafts#1103 is resolved/the spec is updated. Interop bug: web-platform-tests/interop#389 Test coverage for `<string>` syntax in `CSS.registerProperty` is in web-platform-tests#41308.
zrhoffman
added a commit
to zrhoffman/css-houdini-drafts
that referenced
this issue
Mar 13, 2024
tabatkins
pushed a commit
that referenced
this issue
Apr 4, 2024
lilles
pushed a commit
to web-platform-tests/wpt
that referenced
this issue
Aug 5, 2024
…Property Probably this should not be merged until w3c/css-houdini-drafts#1103 is resolved/the spec is updated. Interop bug: web-platform-tests/interop#389 Test coverage for `<string>` syntax in `CSS.registerProperty` is in #41308.
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this issue
Aug 8, 2024
…erage for <string> syntax in @Property, a=testonly Automatic update from web-platform-tests [css-properties-values-api] Add test coverage for <string> syntax in @Property Probably this should not be merged until w3c/css-houdini-drafts#1103 is resolved/the spec is updated. Interop bug: web-platform-tests/interop#389 Test coverage for `<string>` syntax in `CSS.registerProperty` is in web-platform-tests/wpt#41308. -- wpt-commits: 67cb89fd59b261bfe600534af57324f4621364f5 wpt-pr: 43757
i3roly
pushed a commit
to i3roly/firefox-dynasty
that referenced
this issue
Aug 12, 2024
…erage for <string> syntax in @Property, a=testonly Automatic update from web-platform-tests [css-properties-values-api] Add test coverage for <string> syntax in @Property Probably this should not be merged until w3c/css-houdini-drafts#1103 is resolved/the spec is updated. Interop bug: web-platform-tests/interop#389 Test coverage for `<string>` syntax in `CSS.registerProperty` is in web-platform-tests/wpt#41308. -- wpt-commits: 67cb89fd59b261bfe600534af57324f4621364f5 wpt-pr: 43757
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should add
"<string>"as a valid syntax for custom property registration:https://www.w3.org/TR/css-properties-values-api-1/#supported-names
Chrome got a bug report that
"<string>"was expected to work for registered custom properties to be used in the content property.The text was updated successfully, but these errors were encountered: