00:14:36 <CerebraNet> Mmm,food cooked in a slow cooker is good.
00:18:34 <nsITobin> its basically fake bbq fake ribs
00:20:01 <nsITobin> aka sholder strips/chunks seasoned and seared then slowcooked for 20min on high then 15 min natural release then pop it take em out throw em on a pan sauce em and put em under the broiler till the sauce is to your liking.. fake bbq fake ribs
00:20:06 <nsITobin> CerebraNet:
00:22:45 <CerebraNet> Yes?
00:26:16 <nsITobin> just that
00:26:18 <nsITobin> sorry
00:26:48 <nsITobin> pressure cooker/slowcooker
00:27:27 <nsITobin> pressure cooking is slow cooking while exploiting science
00:28:13 <nsITobin> i am tied tho
00:28:29 <tomman> aren't pressure cookers aimed to make cooking, well, faster?
00:28:45 <tomman> My mom loves them, I'm very afraid of them
00:29:29 <nsITobin> yes but because of science namely how atmospheric pressure works in relation to liquids and gasses and shit
00:30:26 <tomman> same like the surprisingly complex science behind the humble moka pot
00:31:40 <nsITobin> well you think about it if you live at high elevations it changes the conditions of cooking the pressure cooker is just more extreme.. and if you like stove top models that's some extreme livin
00:33:33 <nsITobin> for certain applications slowcooking for 4 hours vs pressure cooking for 20 minutes.. I can't tell much of a difference
00:33:53 <nsITobin> now if you are including root veggies and such then you must use a slowcooker
00:34:01 <nsITobin> a pressure cooker won't do the same job
00:34:09 <nsITobin> without some additional prep
00:35:11 <nsITobin> for instance a pressure cooker chicken noodle soup works even with sliced carrots but a full on potato stew wouldn't
00:36:34 <nsITobin> and if your pressure cooker is ALSO a slow cooker then you have a device that works in either case
00:38:50 <nsITobin> Know what would be a good extension for seamonkey? tomman .. a recepie manager..
00:39:07 <nsITobin> science technology and food should always have some overlap
02:15:00 <nsITobin> good my build vm builds
02:15:05 <nsITobin> peace
11:42:26 <njsg> andr01d: wasn't there a setting for that timeout?
11:46:23 <njsg> hm, I guess not, nothing seems to match that timeout?
11:54:24 <njsg> ok accessibility.typeaheadfind.enabletimeout didn't have an effect so far in my testing but it appears accessibility.typeaheadfind.timeout has an effect - but only after opening a navigator window, won't affect already open windows
12:02:37 <njsg> bug 260562, see https://bugzilla.mozilla.org/show_bug.cgi?id=260562#c12, https://hg.mozilla.org/mozilla-central/rev/f4f56776a112 changes the logic so that it handles 0 as "no timeout"
12:03:16 <njsg> from what I can see, at least in this older build, chrome://global/content/bindings/findbar.xml does not have this - or am I looking at the wrong place?
12:03:52 <njsg> this all via http://kb.mozillazine.org/Accessibility.typeaheadfind.enabletimeout#Caveats
13:55:24 <frg_Away> njsg this one? http://xr.thereisonlyxul.org/seamonkey-2.53/source/toolkit/content/widgets/findbar.xml#474
13:57:12 <frg_Away> http://xr.thereisonlyxul.org/seamonkey-2.53/source/comm/suite/components/pref/content/pref-findasyoutype.xul
15:04:43 <njsg> frg_Away: yeah, disabling the timeout doesn't work, from what I can see, maybe I didn't test well enough. bug 260562 removes that and changes it so that a timeout of zero does it instead
15:05:45 <njsg> but perhaps it'd be better to make the separate "enable timeout" pref work as intended, I guess that'll make the pref ui code simpler?
15:10:48 <nsITobin> well my windows build vm can build release in ~35 minutes tho I'd need to add another virtual disk if I am gonna do hg patchqueue in a vm there is only enough space for the tools and headroom for one build roughly
15:18:09 <frg_Away> nsITobin I use a 100GB boot disk and 250GB data disk with repos, build objects and so on.  Buil time is about 25 minutes without tets. With tests I think aber 40 or more
15:19:09 <nsITobin> well i have a 60gb windows disk 16gbs of ram assigned and 6 cores
15:19:24 <frg_Away> njsg we still us  the timeout it seems so cn't just backport it 1:1
15:21:54 <nsITobin> why doesn't it work?
15:23:32 <nsITobin> ah macinfox edge case no wonder the entire feature needs changed
15:24:14 <nsITobin> where even in firefox is typeahead used?
15:28:58 <nsITobin> wow that feature IS jarring to use
15:31:43 <frg_Away> nsITobin I have mozbuild on c: and also the profile. If you use bootstrap and add a few rust versions it fills up pretty quick
15:34:11 <frg_Away> I use 10 GB. Usually the link step and rust gobble up memory. but this seem to be ok. 8 cores or one numa node E5-2667 v3
15:37:21 <nsITobin> does anyone actually know why the findbar is on top of the content and not on the bottom?
15:37:39 <nsITobin> cause afaik xpfe didn't have a findbar and used model dialogs
15:37:50 <frg_Away> no but I really like it this way :)
15:41:03 <nsITobin> see its strange i find it jaring when the UI changes like autohide menubar or tabbar or the findbar when on top but on bottom doesn't bother me and indeed i don't mind infobars pushing content down
15:44:58 <frg_Away> if only one or two hits dont car if bottom or top but for "long" sites and many hits I can keep better tracke where I am if top.
15:46:32 <nsITobin> interesting
15:54:53 <nsITobin> butcha know what? the findbar's position in the UI is not an argument to really have because there are at LEAST three avenues that it could be altered and only one of those involves patching and building AND it is a goal of mine to make building if not "easier" than "easier to accomplish should the mood strike you" and that means I don't need to argue about trivial UX decisions.. no one really does.. there is skinning, there is user chrome, there are
15:54:53 <nsITobin> extensions, there is hacking on the source..
15:57:03 <nsITobin> when did that stop being the answer to everyone's troubles?
15:58:47 <nsITobin> cause that stopped being viable for a lot long before the capability was taken away in Mozilla
15:59:34 <nsITobin> One day I will find the answers to these tough questions.. for now there is more pressing stuff to do and accomplish so shutting up for a little bit.. also food
16:01:33 <njsg> my guess would be microsoft's "war" to make people believe their way is the only way might have influenced things
16:01:55 <nsITobin> and mine?
16:02:38 <njsg> but to be fair there were probably two quite distinct realms, one of happy hacking with lisp machinery or unices or..., and one very corporate, so perhaps it's more about one of them taking the reins of what was perceived as mainstream computing
16:02:50 <njsg> these days you get people claiming UNIX-like systems aren't fit for professional use
16:03:27 <njsg> the same systems that drove a lot of scientific an aerospace work, the same systems that drove and drive the Internet, the same systems that control the gates of Jurassic Park
16:03:47 <njsg> frg_Away: problem is that as far as I can tell enabletimeout isn't used anywhere, or is it?
16:04:14 <nsITobin> they are barely fit for multimedia desktop use outside irix and wayland ain't helping that's true but for basic or custom tailored workstations for a speific environment and also headless systsems like servers unix-like is second to none.. actual unix but not mac is better but they are even less graphical workstation capable
16:05:50 <nsITobin> unfit for multimedia desktop
16:06:16 <nsITobin> and by multimedia desktop i mean $currentDay multimedia streaming services and DRM
16:06:33 <nsITobin> digital rights management
16:06:58 <nsITobin> you know.. tv tv tv sports call of duty
16:07:19 <nsITobin> to bring it back to Microsoft..
16:07:48 <njsg> multimedia and DEs are a drop in the ocean, really
16:08:17 <nsITobin> well of course I must now fight for X11 and shit cause I lost my github account over it
16:08:17 <njsg> and then these cases of multimedia desktop also are far from meaning it can't be used for multimedia work, my go-to example on this has been a certain TLA: ILM
16:08:41 <nsITobin> I called for dev accountability and mutual competition and co-existance.. i was banned
16:08:47 <nsITobin> now wayland must be stopped ;)
17:26:27 <nsITobin> njsg: yeah but what comples a factory worker to have a linux entertainment system instead of an xbox or example
17:26:41 <nsITobin> for*
17:29:08 <nsITobin> So why can't one set the pref to 0 or -1 and have the typeaheadfindbar not goaway
17:32:51 <nsITobin> cause I didn't read carefully ok..
17:55:15 <njsg> no code to do that currently, I did a couple changes but I'd have to test them first
17:57:17 <nsITobin> njsg: you may also want to update suiteglue migration if that matters that is
17:58:00 <nsITobin> I stopped bothering unless it was particularly breaking on my apps long ago
18:02:10 <njsg> a question is what's the best thing to do here. http://njsg.sdf-eu.org/findbar-timeout.diff.txt pretty much introduces "0 is also disable" as in the firefox bug (if it works, done a bit too quickly and untested, so might be outright broken)
18:27:26 <nsITobin> i don't understand why it fails to work as-is
18:27:34 <nsITobin> for firefox's case
18:27:51 <nsITobin> that keeps tripping me up
18:36:17 <nsITobin> anyway njsg would you like me to thrash it with your patch?
18:36:19 <WG9s> 0 and false have always been the same
18:38:08 <WG9s> in fact back in te day when unix systems used to not quite agree on the correct value of true we used to do in a .h file false = 0; true=not false
18:38:12 <nsITobin> I would however give the pref a default value where it is being got from
18:38:24 <nsITobin> to ensure you don't have an error
18:47:06 <nsITobin> IBM Watersnake
18:47:17 <nsITobin> good combo from firesomething
18:53:48 <njsg> but does the timeout function handle 0 that way?
18:56:15 <nsITobin> perhaps get pref default 0 if 0 set prop is disabled check if disabled
18:57:31 <nsITobin> njsg: i dunno if i can translate that for you atm cause doing thing
19:04:16 <nsITobin> the logic.. all it does is create or destroy the timeout event depending on conditions
19:05:21 <njsg> what that patch does is if it is 0 it does not set a timer, it also sets the stored value to 0 if the enabletimer pref is disabled
19:05:28 <nsITobin> it seems nuts to null out a setTimeout object from within it
19:05:31 <njsg> what I wonder here is what is the history of this, perhaps it used to work?
19:05:51 <njsg> the null part is in the code that runs after the timeout, right?
19:06:24 <nsITobin> well apperently it makes sense cause the original code did it.. but its strange
19:06:28 <njsg> my guess is something else relies on that value to re-enable the timeout, I didn't look through the whole file
19:07:15 <nsITobin> has it ever worked as intended since toolkit transition?
19:07:33 <nsITobin> or maybe it was broken when the findbar was made e10s in 25/26?
19:08:01 <nsITobin> well in this case since the binding was created?
19:10:14 <nsITobin> https://github.com/mozilla/gecko-dev/commits/6a1c6379e67e6d86630a7e77f04cfad918c511e5/toolkit/content/widgets/findbar.xml
19:15:43 <nsITobin> https://github.com/mozilla/gecko-dev/commit/3929672b94b5368040355cc66db7124949f772d9
19:16:36 <nsITobin> this changes it from sync to async
19:16:47 <njsg> I don't currently have access to a repository with history, or I'd have started checking that
19:16:51 <njsg> but let me try hg.mozilla.org
19:18:28 <nsITobin> here is an older bug https://github.com/mozilla/gecko-dev/commit/502c86582b8d0c887e05b00bd0663bd02e827436
19:18:34 <nsITobin> which may have screwed it up
19:19:13 <nsITobin> fallout from the inital e10sification
19:20:00 <nsITobin> did setTimeout's impl actually change?
19:22:43 <njsg> before that last commit you linked, it predates mercurial
19:22:54 <njsg> https://hg.mozilla.org/mozilla-central/annotate/a01eebc8baf9a56a06d072ccc80dbbcc9422398e/toolkit/content/widgets/findbar.xml#l407
19:25:15 <nsITobin> this doesn't seem right
19:26:35 <njsg> https://github.com/ehsan/mozilla-cvs-history/commit/dcd23e1f20ea7148b4cadd2a5be207930d7e032a / https://github.com/ehsan/mozilla-cvs-history/commit/dcd23e1f20ea7148b4cadd2a5be207930d7e032a.diff - but one thing to note: does not have the enabletimeout pref?
19:28:35 <nsITobin> cool
19:28:47 <nsITobin> now I have broken into one of gecko-dev's alt histories
19:28:48 <nsITobin> https://github.com/mozilla/gecko-dev/tree/015f043c53b44e164672d2905f551b166c6f845e
19:28:51 <nsITobin> check that out
19:29:21 <nsITobin> there is more history than is apperent due to how mangled the conversion is
19:29:57 <nsITobin> so you sometimes slip into a different universe if you pick the right commit
19:30:13 <nsITobin> where mail and suite were still part of central
19:30:24 <nsITobin> unlike mozilla-central the hg repo
19:34:13 <njsg> https://bugzilla.mozilla.org/show_bug.cgi?id=176296
19:34:24 <njsg> so was this something migrated from C++ to JS?
19:35:46 <nsITobin> https://github.com/mozilla/gecko-dev/tree/3ec464b55782fb94dbbb9b5784aac141f3e3ac01/xpfe/components/find
19:37:17 <nsITobin> https://xr.thereisonlyxul.org/nglayout-1.7/source/xpfe/components/find/
19:37:25 <nsITobin> njsg: as I said, xpfe didn't have a findbar
19:37:28 <nsITobin> lol
19:37:37 <nsITobin> findbar is a toolkit feature
19:38:32 <nsITobin> https://xr.thereisonlyxul.org/aviary-1.9.2/source/toolkit/components/typeaheadfind/src/nsTypeAheadFind.cpp
19:40:51 <nsITobin> something still in use in cpp form
19:41:07 <nsITobin> but the xpfe component part .. what happened to it..
19:42:03 <nsITobin> assimilated to toolkit
19:42:51 <nsITobin> still in use
19:44:54 <nsITobin> so toolkit/[find|typeadheadfind] and the binding have a continuious enough history at least
19:45:13 <nsITobin> contigiuous
19:47:01 <nsITobin> know what
19:50:19 <nsITobin> heh that didn't work
19:50:44 <nsITobin> why is this using a js setTimeout when xpcom has a timer?
19:55:25 <nsITobin> njsg: hey what about suite/browser/nsTypeAheadFind.js could this be conflicting with the binding?
20:09:38 <andr01d> Hola, I failing a login at a website. They asked: Does the browser support SubtleCrypto? Does anyone know if seamonkey supports this?
20:10:27 <tomman> wtf is "SubtleCrypto"!?
20:10:48 <tomman> https://en.wikipedia.org/wiki/Web_Cryptography_API Oh, so this dog vomit
20:11:01 <tomman> https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API
20:11:09 <nsITobin> https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto
20:11:15 <andr01d> That's it
20:11:51 <nsITobin> we should have partial support
20:11:56 <tomman> https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API/Non-cryptographic_uses_of_subtle_crypto trying to load this one on SeaMonkey flashes the page for a split second, then... nothing
20:11:57 <nsITobin> at the very least
20:12:25 <tomman> OK, so that API indeed is old, FF34
20:12:35 <tomman> the newer bits are some newer crypto algorithms
20:12:54 <tomman> and the secure context requirement stuff
20:13:05 <nsITobin> Secure context required @ 75 and HKDF and PBKDF2 @ 119
20:13:32 <tomman> maybe the website requires one of those newer algos or Secure Contet
20:13:35 <nsITobin> andr01d: we have partial support, ask them to provide fallbacks lol
20:13:35 <tomman> --Context
20:13:47 <nsITobin> likely both
20:14:07 <nsITobin> cause some off the shelf lib or part of a common framework package
20:17:24 <nsITobin> https://bugzilla.mozilla.org/show_bug.cgi?id=1333140
20:18:39 <nsITobin> https://bugzilla.mozilla.org/show_bug.cgi?id=1200341
20:18:43 <nsITobin> https://bugzilla.mozilla.org/show_bug.cgi?id=1021607
20:18:47 <nsITobin> err
20:19:05 <nsITobin> do they just need to be enabled?
20:29:01 <nsITobin> https://bugzilla.mozilla.org/show_bug.cgi?id=1851928
20:29:03 <nsITobin> there it is
20:31:59 <andr01d> Seems like the issue is Promises. I'm on .14 and they weren't added until .15
20:32:11 <nsITobin> eh?
20:32:26 <andr01d> I'll upgrade to .18 now, that will hopefully fix this site for me
20:32:36 <nsITobin> i don't think it will
20:32:59 <andr01d> https://www.seamonkey-project.org/releases/seamonkey2.53.15/
20:33:07 <nsITobin> if they want the 75 and 119 changes
20:33:18 <andr01d> That doesn't seem to be required
20:34:02 <nsITobin> clairify please
20:34:34 <andr01d> They're all about the ECMAScript standards, and require "Promises", the first line in the .15 release notes linked above
20:37:32 <nsITobin> yeah and promises has been in the codebase for a long time
20:37:40 <nsITobin> you said subtlecrypto
20:38:08 <andr01d> yes, i'm on an old 2.53.14 version. I'll update to 2.53.18 and that should fix this one
20:38:58 <andr01d> It needs the subtlecrypto, but apparently not the 75 and 119 features you sited
20:39:14 <andr01d> They tested w/ .18 and login worked
20:39:19 <nsITobin> ...
20:39:28 <andr01d> seamonkey 2.53.18
20:39:30 <nsITobin> kl
20:39:34 <nsITobin> k*
20:40:21 <andr01d> Thanks for your help nsITobin! If I had to go to mozilla for support like this on ff it would be hopeless
20:40:47 <nsITobin> I am not sure how I helped.
20:41:07 <andr01d> Just pointing out the release issues
20:41:14 <andr01d> You definitely helped 8-)
20:42:51 <nsITobin> andr01d: just rememeber the UI doesn't HAVE to be radically redesigned for web compat to be added
20:43:37 <nsITobin> but don't let that lul you into a false sense of not keeping it up to date.. it is a browser more so it is a powerful xul suite..
20:44:36 <andr01d> Its not that I was waiting for new UI (in fact I hope the UI doesn't change much) It's just that I don't update often.
20:45:25 <andr01d> I find that the most frequent time things break, is when I update. So I on;y do it when something like this forces me
20:45:42 <andr01d> Not break in seamonkey, just break in my complete desktop environment as a whole
20:45:59 <nsITobin> tell me about it
20:46:46 <nsITobin> ever since I left Windows 7 i have had nothing more than pseudo-stable windows 10 ltsc 2019 and a succession of fedora versions which are all crap except one .. and then later package updates crappified it so it is more like the next version
20:47:51 <nsITobin> it's why I just have to do it my self..
20:47:58 <nsITobin> and you should too ;)
20:52:53 <andr01d> Looks like I'll need the .18, webcomponents is also required
20:52:56 <andr01d> 8-/
20:55:36 <nsITobin> SeaMonkey doesn't have webcomponents
20:55:50 <nsITobin> or not a complete impl
21:01:44 <nsITobin> i can't tell if google is using fallbacks or there is just enough webcomponents for it to work
21:01:56 <nsITobin> but i damn sure know github doesn't have any fallbacks
21:24:13 <njsg> there is some support that's off by default, filtering by webcomponents in about:config should show the toggle
21:24:34 <nsITobin> odd they were on by default on fedora
21:24:34 <njsg> I think frg's recommendation was to still leave it disabled, or did that change more recently?
21:24:45 <nsITobin> even tho fedora's start page is busted
21:26:09 <nsITobin> njsg: bleieve it or not.. hg cloning is faster in a windows vm on linux than it is on windows on bare metal
21:32:46 <njsg> may possibly be because it's in memory? I mean, I suppose Windows NT has, at least currently, a decent filesystem layer with caching etc, but there could still be a speedup if the hardware reads and writes are cached in the host memory
21:33:46 <njsg> there'll still be the usual 30 second dirty buffers write, unless otherwise configured, but that's probably enough for a writing speedup, and won't matter for reading
22:37:02 <nsITobin> njsg: yeah turning off everything except shadows under icon labels and mouse poiter really helped VM performance
22:44:20 <njsg> ah yes, what I call "the first thing I do when I start interacting with a Windows install"
22:44:39 <nsITobin> normally i only turn off aero snap
22:44:41 <njsg> that if I don't outright open gpedit.msc and go through all the policies and toggle some...
22:44:49 <nsITobin> and maybe show windows contents while dragging
22:44:58 <nsITobin> but i normally enjoy fade effects
22:45:03 <nsITobin> but they slow it down
22:45:21 <nsITobin> so.. only compramising on a shadow on the pointer and desktop icons but solid color
22:45:30 <njsg> At least Windows 4 had that dialog/tab where you could uncheck all checkboxes, IIRC it made it at least to NT5.1, isn't it also the same in NT6.1, somewhere in the computer properties?
22:46:22 <nsITobin> njsg: control sysdm.cpl,,3
22:46:47 <nsITobin> note it won't affect metro shit
22:47:30 <nsITobin> yes comma comma three
22:47:38 <nsITobin> so it selects the correct tab for you
22:47:40 <nsITobin> hit performance