3 ms·

The issue isn't, that Slack doesn'T work. The issue is, that it causes an infinite redirect loop on the slack homepage. (Additionally, I'd argue that while Slac

The issue isn't, that Slack doesn'T work. The issue is, that it causes an infinite redirect loop on the slack homepage. (Additionally, I'd argue that while Slack itself may be a webapp, but its homepage is just a landing page, not a webapp)

zzo38computer 6y ago
I agree. You may want to just access documentation or something like that, and that shouldn't require scripts to be enabled. Web pages that require scripts should display useful information even if the scripts are disabled; simply "You must enable JavaScript" isn't useful. Links to documentation should be included. If there is a source code repository, a link to it should be included. If it is a display of some data, links to the raw data should be included. If it calculates something, a link to documentation or source code describing the algorithm would be useful (actually, it can be useful even if you are using the web app to calculate it; you might want to know its working). If it is a web interface to other protocols such as IRC or NNTP, or some protocol that works over HTTP(S) such as ActivityPub, the relevant information (protocol, host name, port number, channel, newsgroup, etc) should be mentioned.
thro1 6y ago
>.. it causes an infinite redirect loop on the slack homepage. - and on every other page. But with accessibility.blockautorefresh=true and without JavaScript the site is still usable and quite nice. There are few things that could work easily but they don't - as the 'Resources' item in the top bar could be a link as the others - but isn't. Occasionally, on some pages there are items looking [kind of] like links - but clicking on them didn't let me progress further. I can browse through slack app directory, but what I see for every app is only a logo, a name and spinning circle instead of anything else.. Actually.. after looking at the code.. there could be some simple stylish way for fixing most of this stuff - with the Stylish extension: @-moz-document url-prefix("https://slack.com/apps/") { .c-tabs__tab_panel { display:block; } .medium_bottom_margin { display: block !important; visibility: visible !important; } .infinite_spinner { display: none; } } The items looking like links which don't work, I guess, supposed to be 'buttons' in 'application'- what means there is no reference on them to related resources or actions and those are less easy to fix. I don't see really why this site pretends to need JavaScript and tries to enforce it - maybe because of some minor accessibility problems which are attempted to be fixed somehow with bigger accessibility problems, maybe it's needed on some other stages. It happens that the apps pages have most of the necessary information just in place, ready to display, but postpone it to do some network requests and processing of some kind, probably with workers. With JavaScript disabled and provided fixes they show up instantly. :)) That satisfies my use case - be able to evaluate when I could be interested in this platform and to be more in touch with such things, not quite in my focus yet, but which could become important sooner; not being forced much to stuff which I dislike or which break my flow. I mostly can't enjoy JavaScript, being stuck on obsolete browser versions because of Firefox's regression and other browsers not being even close to its earlier abilities. Finally, life is to short to fix random accessibility whatever problems, paying for it with own karma - couldn't we just not unnecessarily force barriers to each others, but gently try to make things easier, as WWW was intended ?

zzo38computer 6y ago

I agree. You may want to just access documentation or something like that, and that shouldn't require scripts to be enabled. Web pages that require scripts should display useful information even if the scripts are disabled; simply "You must enable JavaScript" isn't useful. Links to documentation should be included. If there is a source code repository, a link to it should be included. If it is a display of some data, links to the raw data should be included. If it calculates something, a link to documentation or source code describing the algorithm would be useful (actually, it can be useful even if you are using the web app to calculate it; you might want to know its working). If it is a web interface to other protocols such as IRC or NNTP, or some protocol that works over HTTP(S) such as ActivityPub, the relevant information (protocol, host name, port number, channel, newsgroup, etc) should be mentioned.

thro1 6y ago

>.. it causes an infinite redirect loop on the slack homepage. - and on every other page. But with accessibility.blockautorefresh=true and without JavaScript the site is still usable and quite nice. There are few things that could work easily but they don't - as the 'Resources' item in the top bar could be a link as the others - but isn't. Occasionally, on some pages there are items looking [kind of] like links - but clicking on them didn't let me progress further. I can browse through slack app directory, but what I see for every app is only a logo, a name and spinning circle instead of anything else.. Actually.. after looking at the code.. there could be some simple stylish way for fixing most of this stuff - with the Stylish extension: @-moz-document url-prefix("https://slack.com/apps/") { .c-tabs__tab_panel { display:block; } .medium_bottom_margin { display: block !important; visibility: visible !important; } .infinite_spinner { display: none; } } The items looking like links which don't work, I guess, supposed to be 'buttons' in 'application'- what means there is no reference on them to related resources or actions and those are less easy to fix. I don't see really why this site pretends to need JavaScript and tries to enforce it - maybe because of some minor accessibility problems which are attempted to be fixed somehow with bigger accessibility problems, maybe it's needed on some other stages. It happens that the apps pages have most of the necessary information just in place, ready to display, but postpone it to do some network requests and processing of some kind, probably with workers. With JavaScript disabled and provided fixes they show up instantly. :)) That satisfies my use case - be able to evaluate when I could be interested in this platform and to be more in touch with such things, not quite in my focus yet, but which could become important sooner; not being forced much to stuff which I dislike or which break my flow. I mostly can't enjoy JavaScript, being stuck on obsolete browser versions because of Firefox's regression and other browsers not being even close to its earlier abilities. Finally, life is to short to fix random accessibility whatever problems, paying for it with own karma - couldn't we just not unnecessarily force barriers to each others, but gently try to make things easier, as WWW was intended ?