Crashes completely on new firefox browser

[muho-asta]

Hello,

I'm using the latest sandstorm version and since today all of my etherpad grains crash using the latest firefox(57.0) on OSX (El Capitan, 10.11.6). (But for the first days it went fine with it). Then:

An error occurred while loading the pad ReferenceError: require is not defined in https://.................sandcats.io/p/main (line 858)

//

The first time I got another error, something like "type error: c is null..." But now I just get the above for every single existing document and for any new ones I try to create.

– In Chromium it just works fine.

Any idea?

P.S: I'm not sure, if "crash" is the right word, the App opens, but the View is completey crashed (CSS not working) and no content or way to edit...

[kentonv]

Hi,

Can you check if etherpad outside of Sandstorm is affected? Try creating a pad at: https://beta.etherpad.org

[kentonv]

FWIW I can't reproduce this in Firefox 57.0.1 64-bit on Linux. But, I heard a similar report from another user a month or two ago (which we never figured out, unfortunately).

[muho-asta]

Hey,

thanks for the fast reply. It works better, but not completely:

I can write, but there is still the „Loading…“ Part and no tools at the top. No error…

But Console errors:

Error: Failed assertion: Invalid changeset (checkRep failed)

TypeError: self.dropdowns is undefined

Error: Failed assertion: mismatched composition of two changesets

Some errors occur multiple times.

Good luck :)

[muho-asta]

Maybe another hint from the developer tools console inside sandstorm:

"Content Security Policy: 'x-frame-options‘ ignored due to 'frame-ancestors‘-directive

and

"Content Security Policy: The directive 'frame-src‘ shouldn’t be used anymore. Please use 'child-src‘ instead.

Am 16.12.2017 um 19:27 schrieb Kenton Varda [email protected]:

FWIW I can't reproduce this in Firefox 57.0.1 64-bit on Linux. But, I heard a similar report from another user a month or two ago (which we never figured out, unfortunately).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kentonv/etherpad-lite/issues/45#issuecomment-352201499, or mute the thread https://github.com/notifications/unsubscribe-auth/AdovTwF2E5iym92mpSSHeW1lJUqg-Zteks5tBAt7gaJpZM4REWOX.

[kentonv]

Hmm, well, if beta.etherpad.org is affected, then this is a problem in Etherpad proper, not in the Sandstorm port. You'll need to file a bug against them.

(FWIW, the content-security-policy warnings are harmless.)

[muho-asta]

Sure, you’re right!

But still it’s a little difference, I may send you a picture of how it looks inside of sandstorm, if I did not include in on github?

Am 16.12.2017 um 19:34 schrieb Kenton Varda [email protected]:

Hmm, well, if beta.etherpad.org is affected, then this is a problem in Etherpad proper, not in the Sandstorm port. You'll need to file a bug against them.

(FWIW, the content-security-policy warnings are harmless.)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kentonv/etherpad-lite/issues/45#issuecomment-352201917, or mute the thread https://github.com/notifications/unsubscribe-auth/AdovT4BhodCyDKiraVtGtq-E_KBPqsm6ks5tBA1PgaJpZM4REWOX.