01:22:44 <nsITobin> well here are the likely simple non-intrusive save for a couple patches to the style system that can be scraped from UXP https://dpaste.org/CskWj/raw
02:22:52 <XP_TOBIN> logbot test
06:16:08 <frg_Away> nsITobin if you added prefs for this I would need a patch for the prefs window only. I can check this into comm-central then and strings should be exposed in pontoon. It might no longer work but then we need to figure out something else. As of 3 days ago I still see translation updates but might not apply to new strings. TB was supposed to move central to gitlab without us.
14:11:04 <nsITobin> frg_Away: would have to be two patches anyway comm vs mozilla but yeah would be nice to know if cc can still provide translations for us for the moment. here is a comparison screenshot of the added bits from Borealis also sidenote no idea what is going on with the color buttons but not my problem .. https://ibb.co/HqVhPkQ
14:12:28 <nsITobin> you ok with the english strings as I did em .. at the time I wanted to keep the general tone all over preferences .. another reason why copy and paste to Pale Moon should have been different cause the tone and using radios is distinctly communicator preferences
14:13:52 <nsITobin> also good morning ;)
14:15:58 <nsITobin> Also that list I pasted I believe I can complete most of them
14:16:23 <nsITobin> but that's hope talking the code will decide if it will cooperate lol
14:17:25 <frg_Away> looks good to me
14:17:38 <nsITobin> other changes they did are either too large or dependant on their shadowdom impl being accounted for
14:17:51 <nsITobin> and would deff block the queue
14:17:59 <frg_Away> is anything from Firefox or TB similar? The we could borrow the l10n strings
14:18:44 <nsITobin> I'll take a look see but I think it was just dealt with via the add-ons manager
14:18:55 <nsITobin> by selecting the whole program scheme
14:19:02 <nsITobin> or relying on system
14:19:31 <nsITobin> actually why am I speculating
14:20:24 <nsITobin> However, frg_Away there is another source for translations of exactly those strings
14:20:27 <nsITobin> know where?
14:20:31 <nsITobin> PM Langpacks
14:20:53 <nsITobin> wonder how many they got it translated into
14:26:34 <nsITobin> chinese simplified chinese traditional arabic dutch likely translated by moonchild himself french german greek hungarian indonesian itailian .. there are a number
14:29:07 <nsITobin> https://repo.palemoon.org/MoonchildProductions/pale-moon-localization/search?page=1&q=prefersColorScheme&t=&l=
14:35:42 <frg_Away> better than noting is translations are not working. We need to figure out something then. I would rather kick pontoon then but we will see.
14:35:57 <frg_Away> ^than nothing
14:38:39 <nsITobin> and now my github account is shadowbanned from ALL content
14:38:55 <nsITobin> because I was taking part in the anti-wayland gist
14:39:50 <nsITobin> my issues are gone to everyone everything but mechanical git reponess is completely crippled
14:40:05 <nsITobin> Fine.
14:43:36 <nsITobin> yep complete shadowban
14:43:46 <nsITobin> Github is a social network.
14:46:08 <frg_Away> you need to come around and embrace the path of freedom and innovation
14:49:38 <nsITobin> Well github is full of my prior directionless spastic attempts to find direction perhaps it is for the best.. besides didn't I run a git forge for like a year.. I can do that.
14:51:28 <frg_Away> I relly would love to switch to linux but it is an even bigger mess than Windows. MS is working on changing this and the gap has narrowed with 11 :)
14:52:25 <frg_Away> So use if for backups and try to stay ith stable distros like Rocky 8 and opensuse 15.6. When Opensuse switches to ALP I will either stop upgrading or switch to Rocky on the hardware too.
14:52:56 <frg_Away> They could put the immutable stuff where the sun does not shine.
14:53:30 <mrnhmath> rocky 8 is great
14:53:52 <mrnhmath> also i'm doing a new fork of gnome 2 frg_Away
14:54:38 <mrnhmath> https://i.redd.it/7ao641bwahed1.png
14:55:18 <frg_Away> I really like opensuse 15.6. 15.5 was the first version where verything did go smooth. And now they are throwing it away for some alp crap or your daily does of tumbleweed change.
14:57:55 <frg_Away> ^daily dose
15:19:05 <frg_Away> mrnhmath btw. I am a solid kde user :)
15:21:12 <nsITobin> frg_Away: plasma works for you?
15:21:19 <nsITobin> it's a damned disaster on here
15:21:22 <frg_Away> yes
15:21:35 <mrnhmath> plasma is a dud
15:27:17 <nsITobin> well even they admit it most of the plasma tech has been leeched out since 4 but it is still qml
15:27:34 <nsITobin> and qml at least on here just doesn't act right
15:28:52 <nsITobin> but then again frg_Away which distro? and what do you think of plasma workspace 6?
15:29:02 <nsITobin> opensuse?
15:30:37 <nsITobin> thing is on here the last version of KDE 5 fedora released was ACTUALLY not too bad .. had some glitches but it was pretty ok least for my laptop where a more freeform window manager or environment like openbox isn't as good to use.. Then i updated my laptop.
15:31:01 <frg_Away> nsITobin Rocky 8 vm and opensuse 15.6 hardware
15:31:22 <mrnhmath> lol nsITobin
15:31:24 <mrnhmath> classic
15:31:53 <frg_Away> didn't look at 6 yet. Will probably a big improvement. Can't be as bad as 3.51 to 4 but maybe they try to top it.
15:32:55 <nsITobin> well you will have to set the taskbar qml widget back to being a bar.. its a pseudo-dock now and I think the style looks worse too
15:34:45 <nsITobin> no x11 session on fedora .. and kde 6 will drop the x11 session sometime mid-stream
15:34:51 <nsITobin> just so you are aware frg_Away
15:35:02 <nsITobin> for everyone
15:36:17 <frg_Away> nsITobin I know. Can't change the world alone and of no one starts backporting SeaMonkey will stop working sometime in the future
15:36:26 <nsITobin> Now when I said KDE 5 on here wasn't too bad? I meant KDE 5 on x11 .. kde6 for fedora not ONLY took the x11 session away but also kde6 is a new qt version new kde frameworks version and stuff has been touched.
15:38:12 <nsITobin> I need to look into wayland support for seamonkey
15:38:46 <nsITobin> but should setup and test it under xwayland at least
15:39:13 <frg_Away> xwayland should work for now
15:40:03 <nsITobin> I do not personally trust xwayland to persist once majorDistros[] drop xorg proper
15:40:24 <nsITobin> but likely will have it for the rest of the decade
15:40:47 <nsITobin> 2029 is gonna be a huge year for death of systems projects and technology I am forecasting
15:42:00 <nsITobin> Getting through 2025 is gonna be rough as well I expect across the board.
15:47:12 <nsITobin> compared to 115 and 128 you seem to have backported a lot of the widget stuff but not the gfx stuff
15:48:03 <nsITobin> the fact I can run a diff between sm and a late model esr on certain components is a tesiment to your efforts btw.. don't underestimate that
15:48:12 <nsITobin> and have it make sense*
16:34:42 <frg_Away> widget needs about 5000 backports if we want to stay close. I usually filter on the directory and export with thg. Then I have a lot of files and the list can go into the series.
16:35:18 <frg_Away> gfx is at about 60. Want to tackle this once I finished js.
16:39:40 <frg_Away> nsITobin can take out patches if I see they are not good for the system or stash the away for later in the series:
16:39:41 <frg_Away> https://ibb.co/sW0Z5g3
16:40:07 <frg_Away> if the patches are consistent can do about 100 to 200 on a good day.
16:40:15 <frg_Away> usually 40 to 50
16:46:28 <nsITobin> not sure anything from uxp gfx wise is gonna be of much use its more heavily moonchild's than most other areas.. he has opinons about the gfx system especially thebes
16:48:25 <frg_Away> gfx is not a big problem. Usally patches could be applied clean and need minimum rebasing if literally in series
16:49:13 <frg_Away> Tried to update nss to latest esr128 but failed. Needs stulff in security fixed. Not backwards compatible it seems.
16:49:27 <nsITobin> where are you at in nss?
16:49:34 <nsITobin> as if i couldn't check lol
16:49:42 <frg_Away> esr 115 latest 3.90.3
16:49:51 <nsITobin> further than I got
16:50:32 <frg_Away> can't update sqlite too. Some cache stuff prevents it.
16:51:25 <frg_Away> Pale Moon did but they don't have the quota stuff in.
16:53:12 <nsITobin> I never got past 3.64
16:53:25 <nsITobin> on nss
16:53:45 <frg_Away> Bug 1781116 for sqlite
16:53:54 <nsITobin> Pale Moon is stuck at 3.90 i believe
16:54:37 <frg_Away> As satted tried a quick update but needs fixes in security. Then I stopped. No time.
16:55:21 <frg_Away> nss qupdates apply totally clean for the most part so not much work to update it. Same for nss.
16:55:27 <nsITobin> sqlite doesn't seem to bad
16:57:54 <nsITobin> k heading back to winders to do mah patches for prefers-color-scheme even if the UI bits can't be landed cause of l10n delays the gecko parts shouldn't be any issue and can be configured in about:config and would solve a webcompat issue just not all of clownflare lol
16:58:50 <frg_Away> I got some in but this is entangled with the vfs in telemetry. This need to go first.
17:12:41 <frg_Away> nsITobin for the sqlite update I need to do Bug 1819535 first
17:12:57 <frg_Away> fortunately not many changes til then.
17:15:26 <nsITobin> yeah
17:19:02 <frg_Away> as a bonus the telemetryvfs can go then. More crap removed.
17:20:06 <nsITobin> that i think we killed .. might have been me .. can't search the repo for my name cause on rpmo I am a Ghost on Github I don't exist currently soooooo
17:21:07 <nsITobin> checked the spec for prefers-color-scheme.. no-preference is still depercated and no one has added anything like sepia or whatnot
17:21:30 <frg_Away> If no quota manager I would have killed it already.
17:22:17 <nsITobin> well if it wouldn't impact porting I'd say the best way to squeeze some efficiency back out of the codebase is remove all telemetry
17:22:35 <frg_Away> nsITobin I don't think clor schemes should have been added to css but might be wrong.
17:23:06 <frg_Away> hot code is already gone. Check the killtelemetry patches in the queue
17:24:18 <nsITobin> that's gonna be a pain to maintain
17:24:40 <nsITobin> by firefox 200 i bet 3 quarters of the code will be telemetry related
17:27:11 <nsITobin> yeah to be honest prefers-color-scheme really shouldn't have been added and in practicality very few dark sites to light mode or light mode to dark actually look good.. Really the reader mode was the proper solution for this.
17:29:07 <nsITobin> seems overall the css media query really just enables framework sites to just invert the very basic choices provided for color scheme.. wheras sites that added the feature them selves before anyone supported it typically did a much much better job
17:30:31 <nsITobin> and aside from njsg and my self not many people seem to express a preference for a REAL dark mode where on say an amoled screen it is silky smooth like looking into the monolith
17:31:17 <nsITobin> prefers-dim-colors would have sufficed for all the good prefers-color-scheme is used for in practice
17:32:03 <nsITobin> and I THOUGHT the whole black pixels are off not only provides a better aesthetic style but actually saves on electricity on illuminating black.
17:34:24 <frg_Away> nsITobin I started with 3270 screens so I can't stand dark modes. Really like not too white backgrounds and black text.
17:34:35 <nsITobin> according to what I read, and it may be wrong, but on android applications have to actually directly request that mode because despite it being a google phone everything is illuminated dark
17:35:02 <nsITobin> and has an amoled screen
17:35:47 <nsITobin> frg_Away: for barring is the grey on xref too grey or too bright?
17:38:09 <nsITobin> my personally after staring at it for years I needed to dim it a bit
17:39:54 <frg_Away> The only dark mode I care about: https://mainframenation.com/wp-content/uploads/2020/11/ISPF-Panel-1024x576.png
17:40:15 <frg_Away> xref is ok
18:08:05 <nsITobin> my traditional development flow just swap out workbench for source tree https://ibb.co/8B5qNYJ
18:15:33 <nsITobin> newoldexplorer really fills in the gap where openshell leaves off shame the guy which I believe is the glass8 guy has vanished
18:22:17 <nsITobin> Remember to save your files before expecting the code to work.
18:52:02 <nsITobin> after more than just a casual test the code is working exactly as intended 1 for light 2 for dark 0 or any other value will be like it isn't there.
18:52:13 <nsITobin> https://ibb.co/M9Xxg51
18:54:13 <nsITobin> frg_Away: okay I am at working directory with all the patches not applied after the stop patch above it.. what should I do now to create this patch correctly
18:54:28 <nsITobin> in workbench
18:55:02 <frg_Away> "hg qnew -D mypatchname.patch" best done in console
18:55:34 <frg_Away> If new files do an add first. Can do this in workbench on the pink files with mouse popup
18:55:43 <nsITobin> no new files
19:01:59 <frg_Away> if you change something use hg qrefresh. Will update the last patch at the end of the queue  lifo
19:03:34 <nsITobin> how do I set the commit message?
19:05:27 <nsITobin> hold on i may have it
19:12:05 <nsITobin> so uhh yeah that's edit and qrefresh that's easy .. says the person trying to make a commit in hg after a decade of git
19:18:15 <nsITobin> frg_Away: https://files.thereisonlyxul.org/adhoc/patches/TOP-NOBUG-nsstyle-prefers-color-scheme-uxp1752-athenian200.patch
19:18:26 <nsITobin> is that the patch file form you are looking for?
19:21:04 <frg_Away> nsITobin looks goods. the Tabs in nsCSSProps::KTableEntry need to go and replaced with spaces.
19:21:21 <nsITobin> there are tabs.. IN MY PATCH?!
19:21:37 <nsITobin> I'll fix it lol
19:21:44 <frg_Away> yes also in nsStyleConsts.h
19:21:46 <nsITobin> tabs are evil
19:23:35 <nsITobin> huh
19:24:19 <nsITobin> ok i see em now
19:28:36 <nsITobin> should be fixed now depending on your browser cache https://files.thereisonlyxul.org/adhoc/patches/TOP-NOBUG-nsstyle-prefers-color-scheme-uxp1752-athenian200.patch
19:29:44 <nsITobin> hi buc
19:29:51 <nsITobin> the logbot is up
19:29:56 <nsITobin> ;)
19:30:16 <buc> Fine! URL?
19:30:41 <nsITobin> https://logbot.thereisonlyxul.org/seamonkey/
19:30:46 <nsITobin> of course!
19:31:41 <nsITobin> i wonder how we can feed it the dumps from glob
19:31:49 <nsITobin> id really like that history back
19:31:53 <nsITobin> including mozirc history
19:32:33 <nsITobin> on the other hand do I really want logs of 2010s me still floating around on a public service I run?
19:32:41 <nsITobin> something to consider ;)
19:32:42 * buc tries to guess which account this logbot is using...
19:32:56 <nsITobin> its own
19:33:07 <nsITobin> oh nick
19:33:07 <nsITobin> ye
19:34:10 <nsITobin> buc: also enjoy the visually refresh cross-reference now with more trees
19:34:17 <nsITobin> but sadly not all the trees yet
19:35:20 <nsITobin> ok onto the comm part of mah patch for some radio buttons
19:36:04 <nsITobin> which unlike the media query code was actually done by me not just under my supervision
19:36:12 <frg_Away> buc hi
19:36:24 <buc> hi frg
19:38:34 <frg_Away> nsITobin the diff seems to contain the revision can you check git format in hg global settings. I think this takes care of it. Just do a hg qrefresh afterwards.
19:39:20 * a-865 waves to buc
19:39:27 <nsITobin> right you did mention that some days ago i think
19:39:41 <nsITobin> seeing if I can work it out before asking how ;)
19:39:41 * buc waves to a-865
19:41:52 <frg_Away> nsITobin not a big problem. Use thg file->settings
19:44:01 <nsITobin> MQ Git Format to Yes?
19:44:02 <nsITobin> frg_Away:
19:44:12 <frg_Away> yes
19:44:27 <buc> ˙ǝɹoɟǝq sɐ ʅʅǝʍ sɐ pǝɓɓoʅ sᴉ ɐʇɐp 8-ɟʇn ǝɥʇ ɟᴉ ʇsǝʇ oʇ sǝᴉɹʇ ǝW
19:44:42 <frg_Away> sorry the one stays unspecified. The one above it
19:44:55 <buc> OK, fine.
19:44:58 <frg_Away> Git format true
19:45:24 <frg_Away> buc playing with mirrored fonts?
19:45:36 <buc> Yep, :)
19:46:28 <nsITobin> frg_Away: same url
19:48:47 <frg_Away> nsiTobin looks good now 99%. There is a date line and the date in clear. usually the date in clear is not used. Usually only my exported patches have it.
19:49:44 <nsITobin> ok how do i get rid of it
19:56:08 <frg_Away> don't see anything Mabe the qnew setting in mercurial.ini https://paste.debian.net/1324274/
19:56:22 <frg_Away> [defaults]
19:56:24 <frg_Away> qnew = -DUe
19:57:38 <frg_Away> anyway not important. I can alsways use an editor to cut it out. If you do the prefs please do a bug in bugzilla. We can put this in for reference too under it then.
19:58:27 <nsITobin> yeah I just wanted to get the patch format right so I don't have to go through this every time nor create a bunch of extra work
19:59:02 <buc> nsITobin: Regarding history: Old freenode archives are at https://archive.logbot.info/, SM one exists: https://logbot-archive.s3.amazonaws.com/mozilla/seamonkey.gz .
19:59:10 <frg_Away> nsITobin really good don't worry.
20:00:37 <nsITobin> can I just remove it manually or will the patch break?
20:01:05 <frg_Away> nsITobin you can remove it manually.
20:01:31 <frg_Away> I edit headers all day a few times.
20:01:45 <nsITobin> i tried to do it for git but it just rejects it after I do
20:01:50 <buc> And we can only hope that hrosik will appear someday and provide access to similar archives of his log (ie. after Freenode era and before the current one).
20:02:22 <nsITobin> i hope they are ok
20:02:28 <nsITobin> whomever they are lol
20:03:03 <frg_Away> Same for the series. Just need to make sure you edit nothing in the applied patches area there. See the status file.
20:03:26 <frg_Away> Tried to mail him but the old opensuse address bounced.
20:03:38 <nsITobin> just a sec i found a couple trailing spaces
20:04:27 <frg_Away> anyway need some sleep. back tomorrow.
20:04:56 <frg_Away> nighty night
20:06:32 <nsITobin> there
20:06:38 <nsITobin> oh rest well frg
20:07:27 <buc> nsITobin: Just wondering what nickname your logbot uses here?
20:07:55 <nsITobin> yeah i removed the front page for the moment that lists :P
20:08:02 <nsITobin> lists it
20:08:18 <nsITobin> at most you will ONLY have 45 wrong guesses buc
20:08:30 <nsITobin> 44 if you don't guess yourself or me
20:09:33 <nsITobin> buc: if you give up I'll tell you.. didn't wanna spoil any fun
20:09:59 <nsITobin> Our new collective memory is:
20:10:11 <nsITobin> *dramatic pause*
20:10:14 <nsITobin> xulio
20:10:29 <buc> Ups...
20:11:33 <nsITobin> frg came up with it
20:11:50 <nsITobin> now if i only owned xul.io it would be perfect
20:13:03 <buc> Previously, in cases where the logbot became unavailable for some reason, knowing this nickname made it possible to determine whether the logbot itself was working or whether there were other problems.
20:13:50 <nsITobin> yeah
20:14:22 <nsITobin> with the bot here I don't need to mainain a presence with XP_TOBIN anymore
20:14:31 <nsITobin> its kinda liberating
20:14:45 <nsITobin> i can go.. OR stay lol
20:15:15 <buc> Oh, "Real name: There is only XUL Log Bot". Was so easy to find! :)
20:21:51 <njsg> 0724|15:43:50 <+nsITobin> Github is a social network. <-- I've for a long time described GitHub as "facebook for coders" :-P (it *is*, in a way, part of the motivation of GitHub seems to be to make a social network around git
20:21:59 <njsg> could have been much better designed at that
20:23:08 <njsg> Re moving to linux, I honestly at this point would suggest looking into other systems like BSD, just in case it's a better path. Things aren't looking that stellar for Linux-land, freedesktop will likely now pretend "linux on the desktop" means wayland, etc.
20:27:39 <nsITobin> I mean I have other accounts that aren't shadowbanned
20:28:36 <nsITobin> and I suspected something like this might happen if I poked too many people..
20:28:52 <njsg> buc: a lot of squares I see, I'll have to read in the logbot I guess :-D
20:29:55 <nsITobin> you know what?
20:30:02 <nsITobin> I never setup that stats cron job
20:30:07 <nsITobin> need to do that
20:30:39 <buc> njsg: But do you see something in logbot? Maybe some fonts are missing.
20:31:12 <nsITobin> well its all in the unicode range isn't it? not all fonts support all chars.. surprised verdana did
20:31:39 <njsg> buc: oh yes, it's squares but in the terminal emulator. one of the reasons why I'm using this one is that it *doesn't* do font fallback
20:31:58 <nsITobin> verdana dice or dominos are a common sight in mah memory .. the on in my head not the logbot lol
20:32:11 <njsg> in the browser all is well and I'm guessing all the utf8 is still there in the terminal, just not shown because of the font
20:32:30 <nsITobin> latin1 forever
20:32:44 <njsg> ääkköset eivät enää ole ongelma <-- just another test :-P
20:33:21 <njsg> I guess as far as you don't try to mail the irc log via AOL/Yahoo/Verizon/..., that it'll be fine
20:33:48 <nsITobin> hey now you better not be puttin 7bit encodin on blast
20:33:51 <nsITobin> :P
20:34:09 <buc> 抱怨不再是问题 <-- yet another test :)
20:34:23 <njsg> nsITobin: latin1 is more DEC VT-compatible than utf8! :-P (but hey, here's to the power of utf8, using it until the part where it has to be translated for display ensures everything stays there, correctly, etc. and iconv with //TRANSLIT is cool too
20:34:42 * njsg probably has a table somewhere in Emacs too to handle a few glyph translations when in a latin1 terminal
20:37:46 <nsITobin> njsg: think frg will let me re-add gtk1 support LOL
20:38:54 <njsg> it's probably going to be tricky, I guess the goal is mainly to avoid deviating too much so that patches can be more easily backported
20:39:31 <njsg> do you have experience/knowledge about that one, or is it something you'd still need to work/figure out how exactly to do? how much code would need to change?
20:40:07 <nsITobin> no idea i'd never seriously suggest it unless i had something working to draw on
20:40:13 <nsITobin> was just a stray thought
20:40:19 <nsITobin> cause mozilla once supported gtk1
20:41:56 <nsITobin> njsg: with that short list i compiled last night i was paying close attention to small but impactful feature edits that help overall webcompat that wouldn't get in the way and that I could maintain
20:42:09 <nsITobin> for css
20:43:19 <nsITobin> if no-preference was still in the spec for prefers-color-scheme it would have been possible to just never have it
20:43:42 <nsITobin> but i swear they made it HAVE to be something so it is basically manditory to impl
20:43:45 <njsg> brb/bbl, my stomach requests food procurement
20:44:15 <nsITobin> absolutely food is more important than my semi-entertaining blathering.. in fact food sounds like a great idea
20:46:01 <nsITobin> gonna do spinach and feta chicken sasuages in the upside down electric stove coil over a metal pot aka an airfrier with some mushrooms and onions.
21:37:45 <njsg> nsITobin: at that rate, I'd say the chicken is in the way of feta and spinach, less chicken, more room for these two and mushrooms
21:40:35 <nsITobin> they are quite green but the herby green not the bad chicken green
21:41:21 <nsITobin> how many langpacks does seamonkey support?
21:43:04 <nsITobin> njsg: least i can produce a proper patch now ;)
22:26:14 <nsITobin> https://postimg.cc/JyfZ0tMt
22:31:37 <njsg> nsITobin: is that how Firefox exposes it? I'm wondering if there shouldn't be a "Use the OS/platform setting" option
22:31:51 <nsITobin> njsg: requires more plumbing
22:32:14 <njsg> ah, ok
22:32:14 <nsITobin> you need to be able to get it from the widget code
22:33:09 <nsITobin> firefox hooked it up to system first i believe then bound it to the theme system
22:33:23 <nsITobin> then the theme system is told to be system light or dark
22:33:32 <nsITobin> it also requires that we would have to skin a lot more
22:34:40 <nsITobin> and i'd be just fine with skinning everything.. with modern :P
22:36:00 <nsITobin> my original plan for UXP was first .. get this in under user control first and foremost then expand it to have a setting to follow system setting once we got that bit in..
22:36:18 <nsITobin> has to be in one way or another or sites may break
22:37:40 <nsITobin> progress to adding dark mode to the toolkit style from look and feel and fill the gap where needed.
22:39:25 <nsITobin> https://bugzilla.mozilla.org/show_bug.cgi?id=1529323
22:41:15 <nsITobin> SystemColorScheme
22:41:15 <nsITobin> No matching files
22:41:15 <nsITobin> No results found
22:41:36 <nsITobin> yep lots more plumbing to do it Firefox's way
22:46:34 <nsITobin> But ideally imo it would be prefers light/dark/follow theme then theme is either light dark or follow system. Maximum choice minimal complexity to make it happen instead of just system light and dark for everything only.
22:47:10 <nsITobin> can easily add a prop to install manifest to desinate skins as either light or dark
22:47:41 <nsITobin> that was my grand vision to give max user choice to the limited preferences offered
22:48:32 <nsITobin> but i am not gonna demand that's the way SM has to do it.. This is just webcompat with a sprinkle of valueadd
22:49:15 <nsITobin> hope that all makes sense njsg
22:59:15 <nsITobin> did I say a lot of plumbing.. make that a ton of plumbing..
22:59:56 <nsITobin> In mozilla today.. preferscolorscheme is a dom feature
23:00:46 <nsITobin> and widget/lookandfeel and layout/style and stylo
23:14:45 <nsITobin> https://bugzilla.mozilla.org/show_bug.cgi?id=1909743
23:16:24 <nsITobin> Services.startup.quit(Ci.nsIAppStartup.eAttemptQuit);