W3C mailing list search service
Search among 2,298,771 messages in the W3C mailing list archives:
Closed: [i18n-activity] i18n-ISSUE-352: normalization of custom property names (#40)
- Date
- Fri, 20 May 2022 01:55:56 +0000
- Author
- Fuqiao Xue via GitHub <sysbot+gh@w3.org>
xfq closed this issue. See https://github.com/w3c/i18n-activity/issues/40 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Re: [i18n-activity] i18n-ISSUE-352: normalization of custom property names (#40)
- Date
- Thu, 26 Mar 2020 15:50:58 +0000
- Author
- r12a via GitHub <sysbot+gh@w3.org>
@aphillips is about to address the root cause, which is related to an HTML issue. So leave open until then. -- GitHub Notification of comment by r12a Please view or discuss this issue at https://gith
Re: [i18n-activity] i18n-ISSUE-352: normalization of custom property names (#40)
- Date
- Thu, 31 Oct 2019 14:04:44 +0000
- Author
- Addison Phillips via GitHub <sysbot+gh@w3.org>
I added a comment to their issue. While I don't have a *normative* problem with their resolution, I do think that the documentation of "case-sensitive" is lacking. Probably we should raise an issue o
Re: [i18n-activity] i18n-ISSUE-352: normalization of custom property names (#40)
- Date
- Thu, 31 Oct 2019 03:12:14 +0000
- Author
- himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
Closed as invalid, 'case-sensitive' in the state is defined as code-point to code-point comparison without any modification like normalization. -- GitHub Notification of comment by himorin Please vie
Re: [css-variables][I18N-ISSUE-352] normalization and matching of custom property names
- Date
- Mon, 9 Jun 2014 17:34:01 -0700
- Author
- "Tab Atkins Jr." <jackalmage@gmail.com>
The reason I called that one out specifically is because normal CSS properties are ASCII case-insensitive. The behavior of custom properties is identical to normal properties wrt normalization. You c
Re: [css-variables][I18N-ISSUE-352] normalization and matching of custom property names
- List
- www-style
- Date
- Mon, 9 Jun 2014 17:34:01 -0700
- Author
- "Tab Atkins Jr." <jackalmage@gmail.com>
The reason I called that one out specifically is because normal CSS properties are ASCII case-insensitive. The behavior of custom properties is identical to normal properties wrt normalization. You c
[css-variables][I18N-ISSUE-352] normalization and matching of custom property names
- Date
- Thu, 29 May 2014 19:41:15 +0000
- Author
- "Phillips, Addison" <addison@lab126.com>
Hello CSS, I am forwarding the following issue on: http://www.w3.org/TR/css-variables-1/ This issue is a personal comment, as the I18N WG has not had an opportunity to consider it yet. == Section 2 s
[css-variables][I18N-ISSUE-352] normalization and matching of custom property names
- List
- www-style
- Date
- Thu, 29 May 2014 19:41:15 +0000
- Author
- "Phillips, Addison" <addison@lab126.com>
Hello CSS, I am forwarding the following issue on: http://www.w3.org/TR/css-variables-1/ This issue is a personal comment, as the I18N WG has not had an opportunity to consider it yet. == Section 2 s
I18N-ISSUE-352: normalization of custom property names [.prep-CSS-Variables-1]
- Date
- Thu, 29 May 2014 18:14:51 +0000
- Author
- "Internationalization Working Group Issue Tracker" <sysbot+tracker@w3.org>
I18N-ISSUE-352: normalization of custom property names [.prep-CSS-Variables-1] http://www.w3.org/International/track/issues/352 Raised by: Addison Phillips On product: .prep-CSS-Variables-1 Section 2
Help and hints for using this service
W3C Member? Check the Member-only interface. W3C staff? Use the Team-only interface.