We might want to normatively reference Unicode, to pull in all its mandatory rendering requirements (like Arabic shaping, correctly handling ZWJ, etc.).
Added
CSS is built on [UNICODE]. UAs that support Unicode must adhere to all normative requirements of the Unicode Core Standard, except where explicitly overridden by CSS. UAs that use a different encoding are not explicitly supported by the CSS specifications; they are, however, expected to fulfill the same text handling requirements by assuming an appropriate mapping between that encoding and Unicode.
Agenda+ to request review.
Sounds good to me, and I like the wording.
The CSS Working Group just discussed Normatively reference Unicode
, and agreed to the following:
RESOLVED: accept the edit to text L3 to normatively reference unicode?
The full IRC log of that discussion
<dael> Topic: Normatively reference Unicode
<dael> github: https://github.com/w3c/csswg-drafts/issues/3474#issuecomment-451288442
<dael> astearns: There was an edit
<dael> fantasai: Asking WG to review the edit. If everyone is happy we're done
<dael> astearns: lgtm. Other comments?
<florian> +1
<dael> astearns: Want a resolution?
<dael> fantasai: Yes. We're in LC so I want ot make sure it's clear
<dael> astearns: Obj to accepting the edit to text L3 to normatively reference unicode?
<dael> florian: No objections and this helped with writing test cases
<dael> RESOLVED: accept the edit to text L3 to normatively reference unicode?
Most helpful comment
Added
Agenda+ to request review.