the more I learn about Google WebComponents™, er, CustomElements, the more I wonder on why webdevs are so allergic to server side frameworks nowadays

why punt the complexity to client side, and make JavaScript a hard dependency of it!?

exactly

XBL and XML was the way to go

tomman: one day I will write a lib that eats an XBL-like file and construct the custom element for you

well tomman tell me the logic in prefering HTML because XML syntax checking is too hard or annoying but then its all javascript where every error is fatal

and you get no parsing error and often not even an error page

just a blank white page

why is a blank white page on error better than an XML Parsing Error message

no, it should be a blank page with two words only: Something Happened.

nothing else.

and a ref code

tomman: seriously blank white pages are still a thing for js failures

see, JS even fails at failing!

well javascript is an abomination even eich agrees

but classical use in Mozilla was pretty good until a while ago

Okay so some fuzzy animal musta hit my keyboard lol Good morning everyperson

nsITobin greetings

sup

god I hate mozconfigure

unlike mozbuild it doesn't just operate as sandboxed python it has some strange decorator thing that just screwes with what I expect the execution code paths to be.. its like stuff exists but not but sometimes

finally

'MOZILLA_COMPATVERSION': '"91.0"',

'MOZILLA_COMPATVERSION_U': '91.0',

build/milestone-compat.txt

I thought confvar and I thought configure option with defaults and i already did the pref this is just less of a hassle lol

else I'd be duplicating too much or it being all convoluted

thinking about it .. if you can set site specific user agents why does the user need to twiddle with the compat version on a global level

seems more like something they will forget they have done because it worked and they got on with it at the time and cause more support issues than needed

later

nsITobin some sites alredy give me grief with 91. Thought about trying setting to 128 and see how it goes.

Need to fix theip branch. Private files also sin out of control now on websites. It s*cks. Wonder what is next. Mandatory WASM on all sites probably....

if wasm was used for things like that damn good winamp clone in html .. i'd be more for it.. but we know it won't be

and why is blackbox js executed code better than isolated (theoretically) plugins?

it's all a bit nuts

Granted I don't subscribe to "but mah security sandbox" very heavily it has its place but I am still struggling to find what is so stellar and better about this stuff vs 10 years ago

it just seems more complicated and shifted around at best

oh my build successfully completed.. lets see if it works now

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 SeaMonkey/2.53.20

privacy.resistFingerprinting;true

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0 Gecko/20100101 Firefox/91.0

... i dropped a parenthisis somewhere

User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0 Gecko/20100101 Firefox/91.0

is it supposed to be Windows 7?

I'd think that would make you stand out like a sore thumb these days

eh that's a different patch lol

frg_Away: bugzilla.mozilla.org/attachment.cgi?id=9421942&action=diff

more what you were looking for?

nsITobin yes. Thsnks. Will take a deeper look later.

and patch for 1737436 hardcoded revision and firefox version to use the build var is up but it does depend on the snakeoil patch

Testing 2.53.19 right now and do some backups. Will check both later. Might be something for todays or tomorrows 2.53 for a wider audience.

fun times

i just got back from the store

2.53 is much easier to follow by bug i dunno why I have such an issue with central.. just seems to activate my disaster recovery fix the everything senses i guess

nsITobin just tested 2.53.19. Your bug is next but maybe a bit later. Time flies.

its cool dude just glad to help clear some of the bug queue and move it into the patch queue

I need to resist the urge to be too clever about shit.. going overboard all at once on changes.

so it can be allocated where it really needs it when it is actually needed

if that makes any sense

I could easily get lost on some chunk of the codebase spending days and days doing half a dozen barely related things and yeah it would be great but is it NEEDED that sort of thing

or i can do half a dozen barely related tthings that actually NEED fixed

hiya

?

hi

ok

it's working right

see y'all

?

k

lol

Rest well frg

is it time for Saturday Night SeaMonkey?

tomman

Hello Artea