Mmm,food cooked in a slow cooker is good.

its basically fake bbq fake ribs

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

CerebraNet:

Yes?

just that

sorry

pressure cooker/slowcooker

pressure cooking is slow cooking while exploiting science

i am tied tho

aren't pressure cookers aimed to make cooking, well, faster?

My mom loves them, I'm very afraid of them

yes but because of science namely how atmospheric pressure works in relation to liquids and gasses and shit

same like the surprisingly complex science behind the humble moka pot

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

for certain applications slowcooking for 4 hours vs pressure cooking for 20 minutes.. I can't tell much of a difference

now if you are including root veggies and such then you must use a slowcooker

a pressure cooker won't do the same job

without some additional prep

for instance a pressure cooker chicken noodle soup works even with sliced carrots but a full on potato stew wouldn't

and if your pressure cooker is ALSO a slow cooker then you have a device that works in either case

Know what would be a good extension for seamonkey? tomman .. a recepie manager..

science technology and food should always have some overlap

good my build vm builds

peace

andr01d: wasn't there a setting for that timeout?

hm, I guess not, nothing seems to match that timeout?

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

bug 260562, see bugzilla.mozilla.org/260562#c12, mozilla-central/f4f56776a112 changes the logic so that it handles 0 as "no timeout"

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?

this all via kb.mozillazine.org/Accessibility.typeaheadfind.enabletimeout#Caveats

njsg this one? xr.thereisonlyxul.org/seamonkey-2.5…kit/content/widgets/findbar.xml#474

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

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?

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

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

well i have a 60gb windows disk 16gbs of ram assigned and 6 cores

njsg we still us the timeout it seems so cn't just backport it 1:1

why doesn't it work?

ah macinfox edge case no wonder the entire feature needs changed

where even in firefox is typeahead used?

wow that feature IS jarring to use

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

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

does anyone actually know why the findbar is on top of the content and not on the bottom?

cause afaik xpfe didn't have a findbar and used model dialogs

no but I really like it this way :)

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

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.

interesting

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

extensions, there is hacking on the source..

when did that stop being the answer to everyone's troubles?

cause that stopped being viable for a lot long before the capability was taken away in Mozilla

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

my guess would be microsoft's "war" to make people believe their way is the only way might have influenced things

and mine?

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

these days you get people claiming UNIX-like systems aren't fit for professional use

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

frg_Away: problem is that as far as I can tell enabletimeout isn't used anywhere, or is it?

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

unfit for multimedia desktop

and by multimedia desktop i mean $currentDay multimedia streaming services and DRM

digital rights management

you know.. tv tv tv sports call of duty

to bring it back to Microsoft..

multimedia and DEs are a drop in the ocean, really

well of course I must now fight for X11 and shit cause I lost my github account over it

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

I called for dev accountability and mutual competition and co-existance.. i was banned

now wayland must be stopped ;)

njsg: yeah but what comples a factory worker to have a linux entertainment system instead of an xbox or example

for*

So why can't one set the pref to 0 or -1 and have the typeaheadfindbar not goaway

cause I didn't read carefully ok..

no code to do that currently, I did a couple changes but I'd have to test them first

njsg: you may also want to update suiteglue migration if that matters that is

I stopped bothering unless it was particularly breaking on my apps long ago

a question is what's the best thing to do here. 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)

i don't understand why it fails to work as-is

for firefox's case

that keeps tripping me up

anyway njsg would you like me to thrash it with your patch?

0 and false have always been the same

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

I would however give the pref a default value where it is being got from

to ensure you don't have an error

IBM Watersnake

good combo from firesomething

but does the timeout function handle 0 that way?

perhaps get pref default 0 if 0 set prop is disabled check if disabled

njsg: i dunno if i can translate that for you atm cause doing thing

the logic.. all it does is create or destroy the timeout event depending on conditions

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

it seems nuts to null out a setTimeout object from within it

what I wonder here is what is the history of this, perhaps it used to work?

the null part is in the code that runs after the timeout, right?

well apperently it makes sense cause the original code did it.. but its strange

my guess is something else relies on that value to re-enable the timeout, I didn't look through the whole file

has it ever worked as intended since toolkit transition?

or maybe it was broken when the findbar was made e10s in 25/26?

well in this case since the binding was created?

this changes it from sync to async

I don't currently have access to a repository with history, or I'd have started checking that

but let me try hg.mozilla.org

here is an older bug mozilla/gecko-dev 502c865

which may have screwed it up

fallout from the inital e10sification

did setTimeout's impl actually change?

before that last commit you linked, it predates mercurial

this doesn't seem right

ehsan/mozilla-cvs-history dcd23e1 / ehsan/mozilla-cvs-history dcd23e1.diff - but one thing to note: does not have the enabletimeout pref?

cool

now I have broken into one of gecko-dev's alt histories

check that out

there is more history than is apperent due to how mangled the conversion is

so you sometimes slip into a different universe if you pick the right commit

where mail and suite were still part of central

unlike mozilla-central the hg repo

so was this something migrated from C++ to JS?

njsg: as I said, xpfe didn't have a findbar

lol

findbar is a toolkit feature

something still in use in cpp form

but the xpfe component part .. what happened to it..

assimilated to toolkit

still in use

so toolkit/[find|typeadheadfind] and the binding have a continuious enough history at least

contigiuous

know what

heh that didn't work

why is this using a js setTimeout when xpcom has a timer?

njsg: hey what about suite/browser/nsTypeAheadFind.js could this be conflicting with the binding?

Hola, I failing a login at a website. They asked: Does the browser support SubtleCrypto? Does anyone know if seamonkey supports this?

wtf is "SubtleCrypto"!?

en.wikipedia.org/wiki/Web_Cryptography_API Oh, so this dog vomit

That's it

we should have partial support

developer.mozilla.org/en-US/docs/We…cryptographic_uses_of_subtle_crypto trying to load this one on SeaMonkey flashes the page for a split second, then... nothing

at the very least

OK, so that API indeed is old, FF34

the newer bits are some newer crypto algorithms

and the secure context requirement stuff

Secure context required @ 75 and HKDF and PBKDF2 @ 119

maybe the website requires one of those newer algos or Secure Contet

andr01d: we have partial support, ask them to provide fallbacks lol

--Context

likely both

cause some off the shelf lib or part of a common framework package

err

do they just need to be enabled?

there it is

Seems like the issue is Promises. I'm on .14 and they weren't added until .15

eh?

I'll upgrade to .18 now, that will hopefully fix this site for me

i don't think it will

if they want the 75 and 119 changes

That doesn't seem to be required

clairify please

They're all about the ECMAScript standards, and require "Promises", the first line in the .15 release notes linked above

yeah and promises has been in the codebase for a long time

you said subtlecrypto

yes, i'm on an old 2.53.14 version. I'll update to 2.53.18 and that should fix this one

It needs the subtlecrypto, but apparently not the 75 and 119 features you sited

They tested w/ .18 and login worked

...

seamonkey 2.53.18

kl

k*

Thanks for your help nsITobin! If I had to go to mozilla for support like this on ff it would be hopeless

I am not sure how I helped.

Just pointing out the release issues

You definitely helped 8-)

andr01d: just rememeber the UI doesn't HAVE to be radically redesigned for web compat to be added

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..

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.

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

Not break in seamonkey, just break in my complete desktop environment as a whole

tell me about it

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

it's why I just have to do it my self..

and you should too ;)

Looks like I'll need the .18, webcomponents is also required

8-/

SeaMonkey doesn't have webcomponents

or not a complete impl

i can't tell if google is using fallbacks or there is just enough webcomponents for it to work

but i damn sure know github doesn't have any fallbacks

there is some support that's off by default, filtering by webcomponents in about:config should show the toggle

odd they were on by default on fedora

I think frg's recommendation was to still leave it disabled, or did that change more recently?

even tho fedora's start page is busted

njsg: bleieve it or not.. hg cloning is faster in a windows vm on linux than it is on windows on bare metal

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

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

njsg: yeah turning off everything except shadows under icon labels and mouse poiter really helped VM performance

ah yes, what I call "the first thing I do when I start interacting with a Windows install"

normally i only turn off aero snap

that if I don't outright open gpedit.msc and go through all the policies and toggle some...

and maybe show windows contents while dragging

but i normally enjoy fade effects

but they slow it down

so.. only compramising on a shadow on the pointer and desktop icons but solid color

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?

njsg: control sysdm.cpl,,3

note it won't affect metro shit

yes comma comma three

so it selects the correct tab for you

hit performance