Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Javascript fallback support #178

Open
ara4n opened this issue Sep 22, 2015 · 6 comments
Open

Javascript fallback support #178

ara4n opened this issue Sep 22, 2015 · 6 comments
Labels
A-New-Users O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Tolerable Low/no impact on users T-Defect X-Needs-Design

Comments

@ara4n
Copy link
Member

ara4n commented Sep 22, 2015

To quote from #vector: "a quick feedback: Registration went well (as you can see), I just had to figure out that I not only have to switch on js for vector.im but also for matrix.org. Both is not shown. The page is just plain blank without."

@ara4n ara4n modified the milestone: Ragnarok Nov 29, 2015
@ara4n ara4n removed this from the Ragnarok milestone Apr 13, 2016
@resynth1943
Copy link
Contributor

What's the status on this?

Element technically has a <noscript>, but it's pretty bad:

image

How about we create a static page (blue gradient background) with more instructions? Then again, that would play havoc with translation; I've no idea how that would work.

@jryans
Copy link
Collaborator

jryans commented Oct 26, 2020

Well, I'm not really sure what kind of fallback @ara4n had in mind in 2015... It does at least present a simple message now, but agreed it could be better styled.

@jryans jryans added T-Defect defect S-Tolerable Low/no impact on users labels Oct 26, 2020
@resynth1943
Copy link
Contributor

Hmm, yeah that's understandable. I'd vote for a static page which explains how to enable JavaScript (probably link to one of those "Enable JavaScript" sites), and that it needs to be enabled for Element to function. 😄

Not 100% sure how that would work without JavaScript, but it seems like a solid baseline.

@jryans
Copy link
Collaborator

jryans commented Oct 27, 2020

We have various static pages for e.g. incompatible browsers, so perhaps we could leverage some of that.

@t3chguy
Copy link
Member

t3chguy commented Oct 27, 2020

Is this as simple as putting an iframe inside the noscript?

@jryans
Copy link
Collaborator

jryans commented Oct 27, 2020

Hmm, perhaps that would work, worth a try at least. We'd probably want a separate static page to give a clear message instead of just "incompatible" since we know exactly what the issue is in this case.

@jryans jryans removed defect labels Mar 4, 2021
@uhoreg uhoreg added O-Uncommon Most users are unlikely to come across this or unexpected workflow A-New-Users and removed P2 labels Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-New-Users O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Tolerable Low/no impact on users T-Defect X-Needs-Design
Projects
None yet
Development

No branches or pull requests

5 participants