You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is an example how to a bit more friendly use that new functionality in JS.
This isn't looks like a problem for VSCode, because basically it is working inside Electron and mostly chromium based environments. But other projects who based on Monaco stack they don't want to get broken clients in FF browser. Include vscode.dev
What u think so? Do we need some fallbacks or support check for Intl.Segmenter
The text was updated successfully, but these errors were encountered:
Hi guys!
Lets discuss a problem that was come from VScode last update here
That's because VSCode need to work better with chinese locales, emojis and other text stuff... described #50045
This compatibility list is looks really bad for Segmenter https://caniuse.com/?search=Intl.Segmenter. Its turned off many FF versions except latest.
Here is an example how to a bit more friendly use that new functionality in JS.
This isn't looks like a problem for VSCode, because basically it is working inside Electron and mostly chromium based environments. But other projects who based on Monaco stack they don't want to get broken clients in FF browser. Include
vscode.dev
What u think so? Do we need some fallbacks or support check for
Intl.Segmenter
The text was updated successfully, but these errors were encountered: