- From: Shaw via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Dec 2019 13:23:37 +0000
- To: public-css-archive@w3.org
Accessing characters from JS is problematic when you get into Emoji or extended Unicode ranges where some “characters” are actually multiple, like the “family” emojis 👨👩👧👦 The current solution is a messy RegEx pattern matching specific ranges of characters (see some discussion here https://github.com/shshaw/Splitting/issues/25).Having a built in RegEx matched to target ligatures/combined characters Would be a huge help. On Thu, Dec 5, 2019 at 2:08 AM Ilya Streltsyn <notifications@github.com> wrote: > Snapshot profile is dead > <https://github.com/w3c/csswg-drafts/issues/3925#issuecomment-492724267> > (luckily), it's just the draft hasn't been updated accordingly yet (I'm > going to make a relevant PR this weekend). IMO, there is already no problem > with accessing any character of the text (as well as with selecting DOM > elements basing on their contents) from JS APIs. It's *styling* these > things that CSS developers have demanded for years but can't do yet. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/csswg-drafts/issues/3208?email_source=notifications&email_token=AAF5XQ7MDQVJ4DN5ASAPLXLQXCZJJA5CNFSM4F3HPJBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF73SPI#issuecomment-562018621>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAF5XQ4QLOE46TITGGAUZCLQXCZJJANCNFSM4F3HPJBA> > . > -- GitHub Notification of comment by shshaw Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3208#issuecomment-562126745 using your GitHub account
Received on Thursday, 5 December 2019 13:23:39 UTC