frg_Away: can confirm, it ts fixed :)

hello, many sites are saying unsuppported broswer, is there a fix ?

Deirdre: what specific sites?

many are hardcoded to reject anything that isn't Chrome or "latest Firefox", but depending on the site that might (or might not) be easy to bypass

as an example: for some Google services a UA string change is all you need (Search), others need specific addons to provide missing features (Docs), and others... only care about Chrome

"TypeError: t.customElements is undefined"

that website requires WebComponents

...why a LEGACY taxi service needs WebComponents?!

sever al si t3es in my local a rea are like that

OK, enabling "dom.webcomponents.enabled" and "dom.webcomponents.customelements.enabled" does the trick for that site

where are those ?://www.laramietaxi.com/

you may want to try with those, but remember that WebComponents support on SeaMonkey is still experiemntal

do that on about:prefs

about:config

oh, that

maybe it's the time for me to just leave then on for daily usage then?

tomman did it for a few weeks already. But according to reports there are sites that break with it.

wonder if it will interact (negatively) with Palefill

Meh, I'll just leave them on and report~

that work3ed

thank you

tomman there are now literally hundreds of patches in to enable stylo and go forward here but it is just urgkkkk... One thing for sure. If someone at work wants to push rust one day it is the day I quit.

tell them that Teslas also rust :D

not if they're in space

thanks again for the help, take care all

quite hard to drive one there, tho~

tell thet to elon musk

decided to try Google's Monorail with both webcomponents prefs enabled

His rantings will drive it.

...it still wont work because "SyntaxError: invalid identity escape in regular expression"

remind me what was that one...

tomman my second pet project. Landed a few more js patches this week to go beyond 60.

anythng google is just edil

the offending regex: /[\p{L}\p{N}]/u)

evil

it's the /u flag at the end AKA Unicode support AKA ES2015

stackoverflow.com/a/280762 this, indeed

so this time it's not good ol' emoji expressions or named capture groups, but /u that looks kinda useful for non-English languages

developer.mozilla.org/en-US/docs/We…xpressions/Unicode_Property_Escapes of course /u often comes with \p{Emoji_Junk} expressions

now I'm torn: letting \w catch non-English alphabets is something I could actually use in real life

but anything involving emojis is EVIL and JUNK

tomman /u is in since 46 Bug 1135377

Probably Bug 1361876

new regexp

weird then

if I try /[\p{L}\p{N}]/u I get the dreaded invalid identity escape error

but if I try /[\p{L}\p{N}]/, it actually compiles

yeah, /[\w]/u works

so it must be the \p property escapes

could be that they're ignored if u flag is not present?

(according to the spec, u is required anyway for them to work at all)

frg_Away: i decided to take your advance and not try and redefine the mozilla directory structure for existing code.. i will live in a subdir or three and assimilate into there leaving everything else in place

advice

I am restoring the cvs layout

for platform runtime codebase II turbo whatever I am calling it this hour

that kind of shit only works when you have .. direct support

but not when you are a crazy on the fringes of the fringes

lol

frg_Away: I GET THERE IN THE END DAMN IT lol

oh gawd

MercadoLibre also wants this Unicode property escape crapola on their BLOATY mess

(and yet they always find a new way to screw up with me so I do not DARE selling my stuff online, because they're busy pivoting into Latam's Amazon)