16:29:58 why does https://fonts.adobe.com/fonts/brush-script show a blank page? 16:30:43 the status line says "waiting for www.google-analytics.com..." but I'm not sure that's relevant 16:43:17 rsjw: works fine here (albeit slowly) 16:43:31 hit F12 and check the Console tab for errors 16:43:38 (I'm using the nightlies, FWIW) 16:57:23 huh, a crash 16:57:26 out of the blue 17:05:23 huh. I'm using 2.53.16 from pkgsrc 17:08:57 "SyntaxError: expected expression, got '='" "https://fonts.adobe.com/fonts/brush-script" and then a snippet of out-of context code 17:09:26 "ReferenceError: customElements is not defined" "Timestamp: 1/10/24, 12:04:43 PM EST 17:09:29 Error: ReferenceError: customElements is not defined 17:09:31 Source File: https://afwebcdn.fonts.adobe.com/packs/js/7956-5ac897a5de6afe11542c.js 17:09:38 err 17:10:01 "https://afwebcdn.fonts.adobe.com/packs/js/7956-5ac897a5de6afe11542c.js 17:10:14 " "Line: 2848" 17:10:58 and about 200 warnings 17:11:59 I'm not really sure how to make heads or tails out of all this 17:12:46 a bunch of the warnings are for unknown -moz- properties 17:13:57 -moz-flex-grow, -moz-justify-content, -moz-align-items, -moz-osx-font-smoothing 17:15:15 also for font-smoothing, user-delect, -webkit-box-pack 17:15:37 and a whole lot of other parsing errors and unknown pseudo-class or pseudo-elements 17:18:03 apparently display:-ms-flexbox; and display:-ms-inline-flexbox; give parsing errors. that doesn't sound right 17:48:14 rsjw: 2.53.16 is pretty old 17:48:23 start updating to .18 first 17:48:34 customElements is Google WebComponents crapola 17:48:42 there is now some support for that on recent versions 17:49:54 not sure if .18 now enables it (dom.webcomponents.customelements.enabled and dom.webcomponents.enabled are the two relevant prefs) 18:21:08 correct, https: // fonts.adobe.com/fonts/brush-script will cause a CRASH (so, be aware) 18:21:10 (at first it did display, presumably correctly, then after I disabled uBlock, crasherooo) 18:21:55 hmm ok so I guess upgrading to .18 wouldn't be the thing to do? 18:22:43 https://app.bugsplat.com/v2/crash?database=seamonkey_project&id=8049 18:23:32 rsjw: upgrading is fine. but don't expect it to "fix" adobe.com 18:24:53 that bugsplat page doesn't load in my seamonkey either 18:26:47 "TypeError: browser[name] is undefined" "resource://devtools/client/framework/gDevTools.jsm" Line: 150 18:27:28 "TypeError: menu is null" "resource://devtools/client/framework/browser-menus.js" Line: 223 18:28:21 "NS_ERROR_FILE_NOT_FOUND:" "jar:file:///usr/pkg/lib/seamonkey/omni.ja!/components/devtools-startup.js" Line: 300 18:29:20 "SyntaxError: missing : after property id" "https://app.bugsplat.com/v2/main-YG4A44ZH.js" Line 3, Column: 145 18:29:52 maybe upgrading would help load the bugsplat page though :P 18:46:10 first things first: please do upgrade, some of those newfangled JS things have been implemented 18:46:31 therube: hmmm... I get a white screen here for that one 18:47:00 > SyntaxError: missing : after property id[Conocer más] 18:47:07 that's the deal killer 18:47:16 I'll try to upgrade but I can't get to it quite yet 18:47:28 "re=class{database;application;version;_formData=()=>new FormData;_appKey="";_description="";_email="";_user="";c" 18:47:31 i get a request to log in or some such, but since i have no log in, i didn't bother looking further 18:47:37 OK, some class definition dog vomit there 18:47:41 but... maybe someone who does have a log in, can ? 18:50:51 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. 18:51:35 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. 18:52:53 upps no 2.53.18.1 won't help so disregard. 18:54:45 I did got a crash here on the nightly, but I had already closed that Adobe page long ago 18:55:42 dunno why that crash, it was another of those "the whole thing was alone and then *boom~!* goes the dynamite" 19:02:26 crash is because of in Shadow DOM which isn't 100% supported. 19:02:56 even if it's not 100% supported it shouldn't cause a crash though 19:03:09 nsStyleLinkElement.cpp: 19:03:11 if (!doc || !doc->CSSLoader()->GetEnabled()) { 19:03:24 rsjw yes I agree. 19:59:31 yes, crashes. 20:00:30 libxul.so, 50 or so times in the backtrace