Skip to content

Tutorial and REPL pages down in MS Edge #3958

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

Closed
caqu opened this issue Nov 20, 2019 · 5 comments
Closed

Tutorial and REPL pages down in MS Edge #3958

caqu opened this issue Nov 20, 2019 · 5 comments
Labels

Comments

@caqu
Copy link

caqu commented Nov 20, 2019

The pages https://svelte.dev/repl/hello-world and https://svelte.dev/tutorial/basics render a 500 Error when loading them using MS Edge.

Logs
SCRIPT1028: SCRIPT1028: Expected identifier, string or number
c1c5dc18-f610-4f7d-85b2-d2ae3bf14230 (1,36070)
Failed to open blob:https:/svelte.dev/c1c5dc18-f610-4f7d-85b2-d2ae3bf14230

To Reproduce
I loaded the pages using Microsoft Edge 44.18362.449.0 Microsoft EdgeHTML 18.18362

image

@caqu
Copy link
Author

caqu commented Nov 20, 2019

Looks like the home page is impacted as well.
The file throwing the error is https://svelte.dev/client/app.243b9da8.js
image

Looks like something about the REPL dependency.
import{R as y}from"./Repl.6c0ac014.js

@Conduitry
Copy link
Member

Duplicate of #3709 / #2621.

@Conduitry
Copy link
Member

Oh sorry, this issue is for Edge, not IE11. Eh. It's probably more likely that we'd be able to get the site working on Edge with a more reasonable amount of effort.

@Conduitry Conduitry reopened this Nov 20, 2019
@Conduitry Conduitry added the site label Nov 20, 2019
@antony
Copy link
Member

antony commented Nov 20, 2019

@Conduitry on January 15th, Edge becomes Chrome.

It's worth examining your site stats before expending any effort on a soon to be obsolete browser. (I think legacy edge will reach a fraction of a percentage, and IE11 will be significantly higher)

@Conduitry
Copy link
Member

Right, I had forgotten that was coming so soon. In that case, no, this probably isn't something we want to expend any time on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants