3 ms·

Web text fields should also support that functionality, so it may be a question of GitHub breaking/disabling it in some way.

by _bxg1 7y ago

judge2020 7y ago
Kind of odd, is doesn't look like there's a built-in spell checker available in Chromium since you need a spell check provider[0]. I imagine Google injects it into their Chrome when deploying. 0: https://github.com/electron/electron/blob/master/docs/api/web-frame.md#webframesetspellcheckproviderlanguage-provider https://github.com/electron/electron/blob/master/docs/api/we...
- _bxg1 7y ago
  That is interesting; I assumed it hooked into the OS-level functionality but it doesn't appear to. Hmm.
bitwize 7y ago
It's probably a question of the 2010s equivalent of Windows custom control masturbation ("look mom, I can create my own buttons!"): replacing perfectly good HTML elements with ground-up reimplementations written in DIV soup with JavaScript event handlers.
Razengan 7y ago
You're right; I just tested it in Discord, which does have a spell checker, and it seems to use the system dictionary (but it seems one way when teaching it new words), but it's still missing other global text field functionality: https://i.imgur.com/qpOU9dz.png https://i.imgur.com/qpOU9dz.png The point remains: Electron apps generally lose many of the features that the host OS gives native apps for free.
- _bxg1 7y ago
  But the native web, used properly, includes many of them itself. Things like accessibility, metadata, etc. You only really lose features if you're circumventing native web functionality.
  - johnisgood 7y ago
    The problem is that the developers of Electron apps explicitly disable those features. Why?
    - _bxg1 7y ago
      Sometimes web developers will circumvent core HTML features because they don't do everything they want and aren't extensible enough, although this is generally considered bad practice if it's at all avoidable. Sometimes they just don't bother to write semantic HTML even when they could. But the platform itself has the infrastructure; it's possible to write bad software on any platform.

Web text fields should also support that functionality, so it may be a question of GitHub breaking/disabling it in some way.

by _bxg1 7y ago

Web text fields should also support that functionality, so it may be a question of GitHub breaking/disabling it in some way.

judge2020 7y ago

Kind of odd, is doesn't look like there's a built-in spell checker available in Chromium since you need a spell check provider[0]. I imagine Google injects it into their Chrome when deploying. 0: https://github.com/electron/electron/blob/master/docs/api/web-frame.md#webframesetspellcheckproviderlanguage-provider https://github.com/electron/electron/blob/master/docs/api/we...

_bxg1 7y ago
That is interesting; I assumed it hooked into the OS-level functionality but it doesn't appear to. Hmm.

bitwize 7y ago

It's probably a question of the 2010s equivalent of Windows custom control masturbation ("look mom, I can create my own buttons!"): replacing perfectly good HTML elements with ground-up reimplementations written in DIV soup with JavaScript event handlers.

Razengan 7y ago

You're right; I just tested it in Discord, which does have a spell checker, and it seems to use the system dictionary (but it seems one way when teaching it new words), but it's still missing other global text field functionality: https://i.imgur.com/qpOU9dz.png https://i.imgur.com/qpOU9dz.png The point remains: Electron apps generally lose many of the features that the host OS gives native apps for free.

_bxg1 7y ago
But the native web, used properly, includes many of them itself. Things like accessibility, metadata, etc. You only really lose features if you're circumventing native web functionality.
- johnisgood 7y ago
  The problem is that the developers of Electron apps explicitly disable those features. Why?
  - _bxg1 7y ago
    Sometimes web developers will circumvent core HTML features because they don't do everything they want and aren't extensible enough, although this is generally considered bad practice if it's at all avoidable. Sometimes they just don't bother to write semantic HTML even when they could. But the platform itself has the infrastructure; it's possible to write bad software on any platform.