tmedwards / sugarcube-2

SugarCube is a free (gratis and libre) story format for Twine/Twee.
https://www.motoslave.net/sugarcube/2/
BSD 2-Clause "Simplified" License
177 stars 41 forks source link

[UX] The `init-screen` messages for old/no JS browsers are so terse they come off as blunt, and they don't give enough context. #121

Closed pygy closed 2 years ago

pygy commented 3 years ago

Describe the bug.

A user with JS disabled, or with an old browser, is shown these messages with no context as to why they would want to turn it on or upgrade...

Rendered:

Screen Shot 2021-05-06 at 19 41 05

It would be nice to have somthing along "We were about to show you some interactive fiction, but we can't because... [... JavaScript is disabled... Please turn it on. / ... your browser is too old or unsupported, please try this in a more recent browser]".

pygy commented 3 years ago

Well, it looks like this is actually a Twine2 issue...

This is totally a drive-by issue report, I'm not familiar with either SugarCube or Twine, and their repo structure is not simple...

Apologies if this should have been reported elsewhere (edit: pointers welcome if this must be reported elsewhere).

tmedwards commented 3 years ago

They're from SugarCube itself, so this is the correct place to raise an issue for those particular messages.

Maybe this is a language thing, or a me thing, but I don't see the problem. Yes, they're plain and to the point. They're supposed to be. Those messages cannot be internationalized, so they need to be as simple and machine-translatable as possible while still getting the point across. Making them more complicated than they need to be doesn't seem useful.

Users receive the JavaScript message if JavaScript is disabled within the browser—how doesn't matter, but generally it's not something that happens without users' knowledge, or shouldn't at least. It tells them to please enable it [JavaScript] to continue. I'm not sure how much more context is needed or possible there. It certainly can't tell the user how to do so.

Users receive the capabilities message if required capabilities are missing/disabled/broken/etc. It tells them to please upgrade it [their browser] or switch to another [browser] to continue. I'm also not sure how much more context is needed or possible there. Several issues are aggregated into the display of that message rather than a single one, so it can't get more specific than that.

I'm not against rewording them a bit, but there's limit to what I can and will do.