why tf will ff do such stupid things?

franstam: no idea

ive seen software become unlicensed if u do that to trick the system

well good news is gogs seems still solid and works inside seamonkey so I will go with that again.. Have to recustomize it tho.. May build it from source.

franstam: nsITobin: therube: my guess would be digital signatures, but that's just a guess

does this mean anything to us? should we bring the pitchforks again?

means we need fancier js :)

wow, didn't knew Giggityhub was being "ported" to React, eww

didn't also knew that the modern meaning for "legacy software" was "breaking features and shipping bugs because of enforced JS"

better play some Puyo Puyo Fever instead~

Github is just tra-ash

When you are shadowbanned you can keep your orgs but no one sees your activity can search your commits read your issues even on org repos

I think once i get my repos transfered back to my forge i will get the account properly banned i refuse to be left in limbo. I am either banned or I am free to do as I see fit.

But that's just anger talking

So github is rewriting its fromtend in react huh?

Wait so is legacy software now any long running project even if it modernizes now?

Good morning frg_Away .. I almost done testing prefers-contrast .. I don't think it is worth doing UI for .. apple sees it as a descreet feature while microsoft binds it as part of the accessibility themes mozilla defaults to os in both cases.. in the wild seems only used to provide more contrast.. not less ..

After I finish testing it I wanna see what cloudflare says about it cause it exposed more when I added prefers-color-scheme

nsITobin thanks and hi

Well it was either that or continue raging about gitshrub

;)

custom needs some additional logic.. i mean strictly it doesn't but to make it used as intended it does prefers-contrast: custom implies contrast is decided by force-colors: active which implies you hit the checkbox that says override page colors with MY colors.

so I can just check the pref for that if set return custom else follow the prefers contrast pref

likewsise for force-colors just return true on active if that use my page colors pref is active

well that also works as intended.. though because the older color overrides have not been refactored most style overrides that would match will be overridden again by your colors you picked in preferences or from the system but the query does select properly

frg_Away: do you want it exposed to all.js?

nsITobin what does Fx do?

not give you a choice

defering to OS

at least I couldn't find any override for it

well if a pref is easy to do then yes

the pref does make it easier to test

but i added in the logic if document_color_use is 2 (use my colors unconditionally) or an accessibility theme is detected by XPLookAndFeel to return custom which is as close to spec as I can figure otherwise return what the pref is set to with an unknown value being disabled

otherwise it looks pretty much like prefers-color-scheme

let's see what CF has to say

Reading more into it .. seems like prefers contrast outside apple just ain't much different than indicating forced-colors

implying accessibility theme

do chrome browsers let you pick colors like we do?

no they don't

IE did

You can at least create your own theme in Vivaldi

that's true.. vivaldi is a strange project.. it wants to be opera 12 but with mozilla features on chromium

that was the impression I got when I last used it

nsITobin it at least has potential. Edge was good first but is now the usual MS tech vehicle loaded with crap over crap. Uninstalled everywhere but the partition for paid work

absolutely

I wanted to switch to it a few years ago but just couldn't do it.. I settled on Edge cause it had the PWA features I well I don't want to say wanted but require for now.

but manifest v3

yes but Fx...

true

but the not-tabs

and the style

and the ickyness

frg_Away:

it's an adhoc test so set the value and refresh ;)

pref value*

nsITobin see private window

I have returned from gathering supplies

fuel and coolent

for developing seamonkey

Logged report: about:addons style is no longer complete, about:debugging is part unstiled .. uses australis-era in-content styling, about:devtools needs rebranded so it says SeaMonkey Developer Tools, I dunno if it needs more style or not.. its very modern post-australis perhaps photon.. about:licenses seems less styled than normal, about:networking ain't quite right.. uses pre-quantum blue table style which is color swapped for modern,

about:performance looks partly styled, about:profiles looks partly unstyled, about:telemetry just needs removed if the bulk of it is noop or gone otherwise its half styled uses australis or photonic styling, about:url-classifier is partly styled or just renders well unstyled.. about:webrtc uses toolkit style but not the modern color scheme version.. so yeah lots of improvements to be made for modern theme in about: pages alone.

Add-ons Manager doorhangers no longer offer to restart after a theme is installed acting like a persona or static theme tho the restart is pending per normal

so so SO glad it retains the older about:config styling

Indicates that user has notified the system that they prefer an interface that removes or replaces the types of motion-based animation that either trigger discomfort for those with vestibular motion sensitivity, or distraction for those with attention deficits.

build kicked off for prefers-reduced-motion

nsITobin: [...] either trigger discomfort for those with vestibular motion sensitivity, or distraction for those with attention deficits. <-- or makes it unsmooth without some specific 3D acceleration. or perhaps always unsmooth.

I ain't sayin shit .. there is no way me analyising how that is phrased will work out well for me lol

njsg: I am learning.. takes me a minute.

njsg: how do you feel about pork blade steak

cause it was gooood