Applies to uievents, uievents-key and uievents-code specs.
Given the reasons enumerated in https://github.com/w3c/i18n-activity/issues/240 that javascript escapes are not great for representing code point values, why you are using that notation (eg. \u003D) to identify code points rather than the standard notation (eg. U+003D)?
Using the U+ makes it easier to refer in the specs to a character such as 𣧂 or to emoji - ie. you would write U+239C2 rather than the completely unhelpful \uD84E\uDDC2.
We propose you change this notation throughout the three specs.
Applies to uievents, uievents-key and uievents-code specs.
Given the reasons enumerated in https://github.com/w3c/i18n-activity/issues/240 that javascript escapes are not great for representing code point values, why you are using that notation (eg. \u003D) to identify code points rather than the standard notation (eg. U+003D)?
Using the U+ makes it easier to refer in the specs to a character such as 𣧂 or to emoji - ie. you would write U+239C2 rather than the completely unhelpful \uD84E\uDDC2.
We propose you change this notation throughout the three specs.