3 ms·

It's just not the default. As the developer, it's trivial to make text selectable.

by johnecheck 2y ago

johnisgood 2y ago
I meant it as an user.
- johnecheck 2y ago
  Fair. If that's the deciding factor on whether you use a computer program, that's your prerogative. I assume, then, that every app on your phone allows you to select every bit of text in it?
  - deleted 2y ago
    [deleted]
  - johnecheck 2y ago
    Cool. Was hoping to discuss the different expectations we have for a program obtained through a web browser than one obtained through an app store, but I guess downvoting is easier. ¯\_(ツ)_/¯
- tabinno 2y ago
  If the developer has decided you are not allowed to, then you can’t really blame the tool he’s using…
  - johnisgood 2y ago
    I do not blame the tool, but I will avoid using it as long as I am unable to select text. Additionally, see: https://news.ycombinator.com/item?id=43215065 https://news.ycombinator.com/item?id=43215065
chrismorgan 2y ago
You can make text selectable, but it still won’t behave at all like normal text. Selection word boundary things won’t match the local platform behaviour, touch behaviour cannot possibly work properly, things like context menus won’t work properly, and more. The only way you can get the proper behaviour for these things on the web is to use actual DOM text. Some parts of it could in theory be made possible, but I doubt that anything meaningful will ever change—it’s too antithetical to the nature of the web.
- johnecheck 2y ago
  "Proper behavior"... You've defined this term as the precise behavior of the technology that Flutter aims to supplant. Indeed, Flutter will never do everything "properly". But that's not its selling point. It doesn't need to, as long as the number of users reached from a multi-platform release outweighs the users lost because they were offended by a missing native feature. (Assuming you're not some massive company developing a parallel app for each platform)

It's just not the default. As the developer, it's trivial to make text selectable.

johnisgood 2y ago

I meant it as an user.

johnecheck 2y ago
Fair. If that's the deciding factor on whether you use a computer program, that's your prerogative. I assume, then, that every app on your phone allows you to select every bit of text in it?
- deleted 2y ago
  [deleted]
- johnecheck 2y ago
  Cool. Was hoping to discuss the different expectations we have for a program obtained through a web browser than one obtained through an app store, but I guess downvoting is easier. ¯\_(ツ)_/¯
tabinno 2y ago
If the developer has decided you are not allowed to, then you can’t really blame the tool he’s using…
- johnisgood 2y ago
  I do not blame the tool, but I will avoid using it as long as I am unable to select text. Additionally, see: https://news.ycombinator.com/item?id=43215065 https://news.ycombinator.com/item?id=43215065

chrismorgan 2y ago

You can make text selectable, but it still won’t behave at all like normal text. Selection word boundary things won’t match the local platform behaviour, touch behaviour cannot possibly work properly, things like context menus won’t work properly, and more. The only way you can get the proper behaviour for these things on the web is to use actual DOM text. Some parts of it could in theory be made possible, but I doubt that anything meaningful will ever change—it’s too antithetical to the nature of the web.

johnecheck 2y ago
"Proper behavior"... You've defined this term as the precise behavior of the technology that Flutter aims to supplant. Indeed, Flutter will never do everything "properly". But that's not its selling point. It doesn't need to, as long as the number of users reached from a multi-platform release outweighs the users lost because they were offended by a missing native feature. (Assuming you're not some massive company developing a parallel app for each platform)