- From: k-j-kim via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Sep 2021 17:24:36 +0000
- To: public-css-archive@w3.org
k-j-kim has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-variables-1] Specification is not clear on usage and behaviour of custom string as a CSS custom property value == Link: https://www.w3.org/TR/css-variables-1/#syntax The specification is not clear on defining custom string as a CSS custom property value, and browser implementations are inconsistent. ## Repro: - https://codepen.io/kj-kim-sfdc/pen/zYzBNyg ## Expected: - ??? ## Actual: Chrome (Version 93.0.4577.63 (Official Build) (x86_64)): ``` naked: /2.02106e+7/s/assets/images/logo-alpine-group.svg double quotes: "/20210629/s/assets/images/logo-alpine-group.svg" single quotes: "/20210629/s/assets/images/logo-alpine-group.svg" ``` Firefox (91.0.2 (64-bit)): ``` naked: /20210629/s/assets/images/logo-alpine-group.svg double quotes: "/20210629/s/assets/images/logo-alpine-group.svg" single quotes: '/20210629/s/assets/images/logo-alpine-group.svg' ``` Safari (Version 14.1.2 (15611.3.10.1.5, 15611)): ``` naked: /20210629/s/assets/images/logo-alpine-group.svg double quotes: "/20210629/s/assets/images/logo-alpine-group.svg" single quotes: "/20210629/s/assets/images/logo-alpine-group.svg" ``` ## Suggestions: - Specification should be clear on the expected usage and behaviour of strings in CSS custom property value. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6572 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 September 2021 17:24:38 UTC