-
rsjw
-
rsjw
the status line says "waiting for www.google-analytics.com..." but I'm not sure that's relevant
-
tomman
rsjw: works fine here (albeit slowly)
-
tomman
hit F12 and check the Console tab for errors
-
tomman
(I'm using the nightlies, FWIW)
-
tomman_
huh, a crash
-
tomman_
out of the blue
-
rsjw
huh. I'm using 2.53.16 from pkgsrc
-
rsjw
"SyntaxError: expected expression, got '='" "
fonts.adobe.com/fonts/brush-script" and then a snippet of out-of context code
-
rsjw
"ReferenceError: customElements is not defined" "Timestamp: 1/10/24, 12:04:43 PM EST
-
rsjw
Error: ReferenceError: customElements is not defined
-
rsjw
-
rsjw
err
-
rsjw
-
rsjw
" "Line: 2848"
-
rsjw
and about 200 warnings
-
rsjw
I'm not really sure how to make heads or tails out of all this
-
rsjw
a bunch of the warnings are for unknown -moz- properties
-
rsjw
-moz-flex-grow, -moz-justify-content, -moz-align-items, -moz-osx-font-smoothing
-
rsjw
also for font-smoothing, user-delect, -webkit-box-pack
-
rsjw
and a whole lot of other parsing errors and unknown pseudo-class or pseudo-elements
-
rsjw
apparently display:-ms-flexbox; and display:-ms-inline-flexbox; give parsing errors. that doesn't sound right
-
tomman
rsjw: 2.53.16 is pretty old
-
tomman
start updating to .18 first
-
tomman
customElements is Google WebComponents crapola
-
tomman
there is now some support for that on recent versions
-
tomman
not sure if .18 now enables it (dom.webcomponents.customelements.enabled and dom.webcomponents.enabled are the two relevant prefs)
-
therube
correct, https: // fonts.adobe.com/fonts/brush-script will cause a CRASH (so, be aware)
-
therube
(at first it did display, presumably correctly, then after I disabled uBlock, crasherooo)
-
rsjw
hmm ok so I guess upgrading to .18 wouldn't be the thing to do?
-
therube
-
therube
rsjw: upgrading is fine. but don't expect it to "fix" adobe.com
-
rsjw
that bugsplat page doesn't load in my seamonkey either
-
rsjw
"TypeError: browser[name] is undefined" "resource://devtools/client/framework/gDevTools.jsm" Line: 150
-
rsjw
"TypeError: menu is null" "resource://devtools/client/framework/browser-menus.js" Line: 223
-
rsjw
"NS_ERROR_FILE_NOT_FOUND:" "jar:file:///usr/pkg/lib/seamonkey/omni.ja!/components/devtools-startup.js" Line: 300
-
rsjw
"SyntaxError: missing : after property id" "
app.bugsplat.com/v2/main-YG4A44ZH.js" Line 3, Column: 145
-
rsjw
maybe upgrading would help load the bugsplat page though :P
-
tomman
first things first: please do upgrade, some of those newfangled JS things have been implemented
-
tomman
therube: hmmm... I get a white screen here for that one
-
tomman
> SyntaxError: missing : after property id[Conocer más]
-
tomman
that's the deal killer
-
rsjw
I'll try to upgrade but I can't get to it quite yet
-
tomman
"re=class{database;application;version;_formData=()=>new FormData;_appKey="";_description="";_email="";_user="";c"
-
therube
i get a request to log in or some such, but since i have no log in, i didn't bother looking further
-
tomman
OK, some class definition dog vomit there
-
therube
but... maybe someone who does have a log in, can ?
-
frg_Away
2.53.18 is probably the messagechannel crash. 2.53.18.1 works. If someone wants to test I can upload the genuine en-US x64 fresh off the builder. exe only for Windows or tar.bz2 for Linux.
-
frg_Away
For bugsplat you currently need another browser but you won't be able to check the bugs without an account anyway. As usual life is not perfect. sigh.
-
frg_Away
upps no 2.53.18.1 won't help so disregard.
-
tomman
I did got a crash here on the nightly, but I had already closed that Adobe page long ago
-
tomman
dunno why that crash, it was another of those "the whole thing was alone and then *boom~!* goes the dynamite"
-
frg_Away
crash is because of in Shadow DOM which isn't 100% supported.
-
rsjw
even if it's not 100% supported it shouldn't cause a crash though
-
frg_Away
nsStyleLinkElement.cpp:
-
frg_Away
if (!doc || !doc->CSSLoader()->GetEnabled()) {
-
frg_Away
rsjw yes I agree.
-
njsg
yes, crashes.
-
njsg
libxul.so, 50 or so times in the backtrace