- From: DeeDeeG via GitHub <sysbot+gh@w3.org>
- Date: Sun, 25 Mar 2018 14:19:52 +0000
- To: public-css-archive@w3.org
I thought about this some more. I don't think this property would be much harder to implement than the others. My reasoning is: implementations already need to know the list of Presentation Participating Code Points (PPCP) to implement the other values for `font-variant-emoji`. The hard part is just knowing the up-to-date list of PPCP (and wiring up the logic to have this affect font selection). Beyond the requirements of the other values, this value would only require a binary/boolean value associated with each PPCP. Each PPCP just needs to be noted as "default text" [per Unicode] or "default graphic" [per Unicode]. Thinking as an [amateur] programmer, I predict that a each PPCP codepoint number, and its corresponding default presentation per Unicode, can be thrown in an array, and there you go. (The programming logic to have this affect font selection shouldn't be much of a stretch beyond what it takes to do "always text-style" font selection, and "always graphic-style" font selection.) Again, getting the list of PPCP (and being set up to do logic based on the list of PPCP) apears to be the bulk of the work, and I suspect adding a value to use the text/graphic default presentaion [per Unicode] would not be very hard. -- GitHub Notification of comment by DeeDeeG Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1223#issuecomment-375974002 using your GitHub account
Received on Sunday, 25 March 2018 14:19:55 UTC