06:06
<annevk>
Was it ever discussed to add a then method to IDBRequest?
13:53
<substan[e>
sup
13:55
annevk
finds https://github.com/inexorabletash/indexeddb-promises/issues/7
13:55
<substan[e>
how are you folks
13:55
<substan[e>
im looking at xhr.spec.whatwg.org - reading abuot using xmlHTTPreq
13:55
<substan[e>
isnt this all redone, better, in jquery???
13:57
<annevk>
substan[e: how do you think jQuery works?
13:57
<substan[e>
I know its based off xmlhttpreq
13:57
<substan[e>
isnt it a 'front end' to doing it the old way?
13:57
substan[e
is kinda new to this. sorry
13:57
<substan[e>
didnt jq summarizse alot of work with this stuff with like gets() puts() ???
13:57
<annevk>
Although I suppose jQuery could use fetch() these days, I don't really know
13:58
<substan[e>
How do you code socket stuff
13:58
<substan[e>
do you do it using xmlHTTPreq?
13:58
<substan[e>
or with jq?
13:58
<substan[e>
(my friend told me forget about xmlhttpreq and only learn jq)
13:58
<substan[e>
is that wrong?
13:58
<annevk>
substan[e: what do you want to learn?
13:58
<substan[e>
basically.
13:59
<substan[e>
im learning nodeJS on the side. but i want to learn client side JS first
13:59
<substan[e>
. i want ot understand how to open a socket for reading or a RESTful API call or something
13:59
<substan[e>
to another one of my servers
13:59
<substan[e>
.. i understand XML or json is how i would send/format the data. right?
14:00
<annevk>
substan[e: you could learn jQuery for that I suppose, but you might as well start with https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch and avoid a dependency on a library
14:00
<substan[e>
really?
14:01
<substan[e>
.. i totally will. i want to understand how its workin fully, before using something that makes it work w/o knowin whats happening rihgt?
14:02
<Domenic>
annevk: for "_bc_'s WindowProxy's [[Window]] value", do you prefer "active window", "active `Window`", "current window", or "current `Window`"? Or other?
14:02
<substan[e>
annevk: you seem like you know whats up. i wrote my page https://tranceattic.com in vim/notepad++ with jquery.. if you let it load and inspect element i cant figure out where or how to fix these console errors
14:03
<substan[e>
there is only like 2 main ones.. Uncaught Type error cant acces prop "defaults"
14:03
<substan[e>
but to the right . its not listing a file i am fam. with it says : line 1 > scriptElement
14:03
<substan[e>
.. i have a feeling this has to do with the ordering of loading my JQ/BS js / css scripts.
14:03
<annevk>
Domenic: I suppose active window, though I'm not sure why active document isn't enough
14:05
<annevk>
substan[e: I recommend using StackOverflow or some IRC equivalent
14:06
<substan[e>
kk will do. im readin that doc now. i appreciate it
14:06
<substan[e>
mind if i idle here?
14:06
<annevk>
subz: not at all
14:07
<subz>
thx.. id like to actaully hang in an irc channel where people discuss code [and the topic of the channel[
14:07
<subz>
and not like efnet. where everychannel is #polotics or #whatihadforbreakfast ;p
14:08
<subz>
annevk: are you into any nodeJS?
14:20
<andreubotella>
annevk: So in encoding#215 it was bugging me a bit that token queues were defined as simple data structures with no reference to I/O, and I think I've come up with a simple-ish way to make the definition reflect reality
14:21
<annevk>
andreubotella: that sounds interesting
14:22
<andreubotella>
annevk: Have each token in a token queue be one of "immediate" or "blocking", specifying that reading blocking tokens might block, and say something like "all tokens created by this spec are immediate, but blocking tokens can be created through implementation-defined ways"
14:22
<andreubotella>
And now we can define "wait" (as in BOM sniff)
14:23
<annevk>
andreubotella: and read would also have to wait?
14:23
<andreubotella>
there's a comment in the source saying that read would block, and to blame SimonSapin if that was a problem
14:24
<annevk>
andreubotella: heh, that was written a long time ago, but other than that HTML issue that you largely solved it hasn't really come up I think
14:25
<annevk>
so maybe it was not a problem
14:26
<andreubotella>
I don't think there are any cases where implementations can't make read async
14:26
<SimonSapin>
andreubotella: source for what?
14:26
<annevk>
andreubotella: but yeah, it might make sense for the queue to return "nothing available" and "end-of-stream" as distinct in certain cases
14:26
<andreubotella>
SimonSapin: the encoding spec
14:27
<andreubotella>
https://github.com/whatwg/encoding/blob/master/encoding.bs#L110
14:27
<annevk>
I suspect this was written when we shared an open office space SimonSapin, git blame can prolly verify
14:27
<SimonSapin>
I have no memory of this ^^'
14:28
<annevk>
Seems it was committed six years ago and 3 years ago I changed curse to blame :p
14:28
<SimonSapin>
haha
14:29
<annevk>
Hmm, PR Preview is not picking up changes
14:29
<SimonSapin>
Yeah March 2014 is when we were in the same office I think
14:31
<andreubotella>
in any case, I'm gonna have to take a good look at every time that read is called just in case
14:51
<subz>
its great to see acitivty in an irc channel ;p
14:51
<subz>
(efnet = ded)
15:04
<andreubotella>
subz: this channel isn't quite dead, but usually there isn't a lot of activity, especially on the weekends and European late nights and mornings
16:51
<annevk>
tobie: if you're around, https://github.com/whatwg/url/pull/518 is not getting updated by PR Preview and I've noticed this in several PRs now; we have switched to GitHub Actions but that's not something that PR Preview should be concerned with, right?