01:29
<Domenic>
TabAtkins: I think you want control group. It is equal to document in all cases except dialogs being open. (And nobody implements that last part, even Chrome :()
01:31
<TabAtkins>
This was informal, so my slightly inaccurate terminology is more understandable. 😀
01:35
<Domenic>
fair!
10:41
<annevk>
So I looked into https://github.com/w3c/html/issues/165 and it seems first of all that JSFiddle is getting in the way since once I take it out of JSFiddle I'm unable to reproduce browser differences
10:46
<annevk>
Actually, I sometimes can
11:00
<annevk>
And solved...
11:10
<zcorpan>
hmm i don't remember <ol reversed> getting implemented! per http://caniuse.com/#search=reversed it seems it was a while ago :-)
11:11
<annevk>
Was news to me too
14:15
<zcorpan>
has anyone replied to Dean, John on help⊙wo (20 March, unsubscribe)?
14:26
<zcorpan>
i haven't looked at this in detail yet but storage proposals are always interesting https://discourse.wicg.io/t/writable-file-api/1433 https://discourse.wicg.io/t/service-worker-content-indexing/1432
15:15
<Ms2ger>
TabAtkins, now I'm curious about the Member-only FUD
15:19
<TabAtkins>
chaals trying to rewrite history about whatwg/w3c and the forking situation
15:40
<MikeSmith>
there is probably some clinical term for the underlying psychological disorder
15:41
<MikeSmith>
that is, when you know are the one who has committed a wrong, and you yourself are doing something that you know in your heart to be dishonest and wrong and unprincipled
15:41
<MikeSmith>
but instead of admitting that, you blame the people you are wronging
15:42
<MikeSmith>
you create a rationalization that justifies to try to justify your behavior
15:42
<MikeSmith>
*you create a rationalization to try to justify your behavior
15:43
<TabAtkins>
Yeah, that's cognitive dissonance, and rationalization.
15:44
<TabAtkins>
People don't like thinking of themselves as bad, so they construct narratives where their actions are justified.
15:44
<TabAtkins>
Everyone does it, it's not a psych disorder.
15:44
<TabAtkins>
Well, *constantly* doing things that are bad, that you then have to justify, that's something wrong.
15:48
<astearns>
psychological projection
16:14
<MikeSmith>
> People don't like thinking of themselves as bad, so they construct narratives where their actions are justified.
16:14
<MikeSmith>
bingo
16:15
<MikeSmith>
astearns: thanks that sounds like what I was trying to think of
16:34
<annevk>
Domenic: I'm going to add a note about that is attribute behavior
16:35
<annevk>
Domenic: seems like a thing folks will ask about
16:35
<Domenic>
annevk: ah OK. There is going to be one in HTML but having one in DOM too is probably good.
16:35
<Domenic>
annevk: I was about to push and squash so perfect timing. I'll leave it to you. I unprotected it for now.
16:35
<annevk>
Domenic: okay
16:35
<annevk>
Domenic: I'll just push it as a fixup and then still leave honors to you
16:36
<Domenic>
ok cool
16:41
<annevk>
Domenic: never mind, just land it as-is
16:41
<Domenic>
annevk: ok, if you say so!
16:42
<annevk>
Domenic: I can't really think of a better note than saying set an attribute has side effects and that is pretty obvious when you follow the link
16:44
<davygrvy>
Hi, I was wondering if I could ask about chromium's WebKit encodings module? Is there a way to put it in a strict mode so named encodings such as iso8859-1 don't become windows-1252, but stay strict to what they are claimed as?
16:47
<annevk>
davygrvy: the person who might know doesn't seem to be around, but I kinda doubt it
16:48
<davygrvy>
tnks
16:48
<annevk>
davygrvy: not sure why they'd ship encodings the web doesn't need
16:48
<davygrvy>
for test/validation purposes
16:50
<jsbell>
irc-logs ends in january :(
16:50
<Domenic>
annevk: how long does it usually take for a merge to make its way to dom.spec.whatwg.org?
16:50
<Domenic>
jsbell: second link works still
16:51
<jsbell>
Dominic: \o/
16:52
<annevk>
Domenic: hmm should be immediate usually
16:52
<Domenic>
not seeing it, hope I didn't break anything...
16:52
<annevk>
Domenic: triggered a manual refresh, should be there now
16:52
<Domenic>
oh, there it goes
16:53
<jsbell>
davygrvy: I'm sorry you didn't like the answers you were given on chromium-discuss, but those are the answers you're going to get.
16:53
<annevk>
Domenic: sometimes there seems to be a little fluke, also with the tweets
16:53
<jsbell>
When specs and reality disagree, reality usually wins.
16:53
<davygrvy>
hi jsbell
16:53
<MikeSmith>
jsbell: also logged to http://logs.glob.uno/?c=freenode%23whatwg
16:53
<davygrvy>
or do it oneself
16:54
<davygrvy>
and not even bothering to to commit a changelog
16:55
<jsbell>
davygrvy: I can answer your questions on #blink
16:56
<jsbell>
(i.e. where to look to make a local build with the behavior you want)
16:57
<davygrvy>
I see most of it.. I thought I was forced to climb the mountain myself
17:10
<jsbell>
davygrvy: you're on your own for the changes, but time permitting I'm happy to answer questions over on #blink
19:07
<jhack>
is there a size limit to fetch’s body? I’m trying to send a base64 string within the body, but my fetch doesn’t seem to be working at all. Not sure whether it’s fetch or something else
19:08
<jhack>
pretty sure it’s something else, but wnated to double check
19:10
<wanderview>
jhack: shouldn't be a size limit... what browser?
19:10
<jhack>
doing this on react-native
19:10
<jhack>
chrome
19:12
<wanderview>
jhack: how are you initializing the body?
19:12
<jhack>
JSON.stringify ?
19:13
<wanderview>
jhack: I mean the Request or fetch() code you are using
19:13
<jhack>
it’s apart of the request obj
19:14
<jhack>
so fetch(..url.., { method, header, body })
19:14
<jhack>
ill put it up on gist
19:14
<wanderview>
thanks
19:15
<jhack>
https://gist.github.com/jhack32/6186ae4612a631e518e505c58d74c56f
19:16
<wanderview>
jhack: and what happens when you run it?
19:16
<jhack>
it doesnt run
19:16
<jhack>
holdon let me update that gist actually
19:16
<wanderview>
does it reject with an error?
19:17
<jhack>
no reject
19:17
<jhack>
or anything
19:17
<jhack>
my console logs inside the fetch doesnt show either
19:17
<jhack>
which was weird
19:17
<jhack>
but if I take out the promise before it, itll run fine
19:18
<wanderview>
the promise before it?
19:18
<jhack>
I updated the gist
19:18
<jhack>
so, it reads the file, converts it into base64, then does the fetch call
19:19
<wanderview>
jhack: I think you need `return fetch(` here: https://gist.github.com/jhack32/6186ae4612a631e518e505c58d74c56f#file-gistfile1-txt-L5
19:19
<wanderview>
you're not returning the promise from the fetch(), right?
19:20
<jhack>
no
19:21
<wanderview>
because if it throws then your inner .catch() just returns its error
19:21
<wanderview>
but its not returned to the outer .catch()
19:22
<jhack>
stil not gettin into fetch
19:23
<wanderview>
is your `this` correct?
19:23
<jhack>
should be, it consolelogs correctly
19:23
<jhack>
So it works on the emulator, but not on a device
19:24
<jhack>
which is what I’m trying to test it on right now
19:24
<wanderview>
hmm... you got me then, sorry
19:24
<jhack>
thanks tho
19:40
<wanderview>
jsbell: fyi, I started the upstream of our SW wpt tests today... hopefully it will get fully upstreamed on to github before our meeting monday https://hg.mozilla.org/integration/mozilla-inbound/rev/26e409f43a2e
19:41
<jsbell>
wanderview: awesome
19:41
<wanderview>
only took me a year to get around to it... :-\
21:11
<jhack>
is there usually a reason why fetch gives the error TypeError: Network request failed
21:11
<jhack>
I’m reading it could be due to the server’s certificate? But i’m trying to run fetch to AWS
21:21
<wanderview>
jhack: is this a cross-origin fetch?
21:21
<jhack>
yes
21:22
<jhack>
how can i log xhr?