01:52
<miketaylr>
hi hasather
07:01
<zcorpan>
jgraham: i dunno... http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4205 looks like the reported outerWidth is sync in chrome/safari/opera (on mac) but not in firefox?
07:02
<zcorpan>
jgraham: does gecko have a bug reported about this?
07:37
<jgraham>
zcorpan: So we were discussing the implementation of this in Servo and it turns out that X11 doesn't allow you to make this sync. It has a mechanism to ask the WM to set a window size, and a mechanism to get events when the window size changes, but no coordination between the two. So if you ask for a size change you may get ignored at the WM level (consider a tiling WM) and never get an event back, or you may get an animated transition and get multi
07:37
<jgraham>
... might get an event related to some other resize that has happened.
07:40
<zcorpan>
jgraham: you could maintain size information separately, and resizeTo could update that information sync and ask the WM to resize. but i don't have an opinion either way how this should work, really.
07:41
<jgraham>
zcorpan: But that information would be wrong if the resize doesn't actually happen at the WM level
07:42
<zcorpan>
yeah, right.
07:44
<zcorpan>
jgraham: what happens in chrome in such a case?
07:46
<jgraham>
zcorpan: Not sure
09:03
<zcorpan>
i'm happy that i now understand enough of git to be able to work through simple mistakes like forgetting to create a local feature branch and committing to master (locally). when i started using git i'd sigh and remove my working copy and do a fresh clone and start over
09:08
<Ms2ger>
Been there...
09:18
<nox>
zcorpan: Git is the only DVCS that should come with a Remote Desktop Assistant.
09:19
<zcorpan>
is there a git plugin that will warn me if there are unstaged changes when doing git commit --amend?
09:22
<Ms2ger>
var ltr = new Array(),
09:22
<Ms2ger>
all = document.querySelectorAll('*');
09:22
<Ms2ger>
for(var i = all.length; i--; ltr.unshift(all[i]));
09:34
<nox>
zcorpan: No, because that's a feature to be able to leave unstaged changes on amend. Maybe you could do a hook though.
09:37
<davve>
zcorpan: or maybe you can use an alias like: "amend = "!sh -c 'git diff --quiet && git commit --amend || echo Your working directory has unstaged changes.'"" in ~/.gitconfig and then use 'git amend'. (Not well tested...)
09:47
<zcorpan>
davve: thanks! seems to do the trick. just need to learn to type git amend :-)
09:57
<zcorpan>
iirc IE6 did something weird with class in particular https://twitter.com/RReverser/status/732527451973267456
10:00
<zcorpan>
hmm no maybe that was style
10:01
<zcorpan>
yep :-)
12:06
<annevk>
tyoshino: yhirano_: if you're around: https://github.com/whatwg/fetch/pull/298
14:19
<annevk>
so <link rel=stylesheet href=... crossorigin> is fairly useless if that fetches further stylesheets that don't get fetched with CORS
14:20
<annevk>
since then only the initial one can be accessed through CSSOM...
14:20
<annevk>
but I guess nobody uses the CSSOM so it's not a problem?
14:35
<tamird>
Hello folks! Can anyone tell me what a BufferSource is? https://fetch.spec.whatwg.org/#bodyinit
14:42
<annevk>
tamird: https://heycam.github.io/webidl/#common-BufferSource
14:44
<tamird>
thanks
14:46
<annevk>
https://blogs.windows.com/msedgedev/2016/05/17/es6-modules-and-beyond/ seems to rather carefully avoid where <script type=module> is defined
14:50
<tamird>
@annevk thanks! is there a reason BufferSource isn't on MDN?
14:51
<annevk>
tamird: I don't know, do they normally document typedefs?
14:51
<tamird>
looks like it? https://developer.mozilla.org/en-US/docs/Web/API/ArrayBufferView
14:55
<annevk>
tamird: yeah, guess BufferSource should be added then
14:56
<tamird>
https://github.com/whatwg/html/issues/1273
14:56
<annevk>
tamird: ah thanks, if you want to write a PR for that, instructions are in the README ;-)
14:57
<tamird>
ha, okay fine
14:58
<tamird>
goodness this is a few hundred megs
14:59
<annevk>
tamird: kitchen sink of the web platform
14:59
<annevk>
tamird: pretty heavy kitchen sink, come to think of it
15:06
<tamird>
@annevk https://github.com/whatwg/html/pull/1274
15:08
<annevk>
tamird: thanks, looking at that though I realized that HTML itself doesn't have a dependency on BufferSource just yet
15:08
<tamird>
where'd you discover that?
15:08
<annevk>
tamird: it probably should in some places, but we haven't made those changes yet
15:08
<annevk>
tamird: searching for "BufferSource", basically
15:09
<tamird>
just in the spec?
15:09
<annevk>
tamird: yup
15:10
<tamird>
afaict it's only useful in one place (websocket definition)
15:13
<tamird>
@annevk well i'm not sure where to go from here
15:14
<annevk>
tamird: yeah, I'm sorry I made you go through the PR process for something that's not needed (yet)
15:15
<tamird>
ah, so basically fetch needs to become standard before buffersource is added?
15:15
<annevk>
tamird: we need to update WebSocket's definition, but that requires some other changes too in the prose and ideally IDL is changed a bit further to make it easier to work with BufferSource-like objects (there's an open bug on that against IDL)
15:15
<annevk>
tamird: Fetch and HTML and IDL are all independent
15:15
<annevk>
tamird: Fetch depends on IDL's BufferSource definition, HTML doesn't (yet)
15:15
<annevk>
tamird: does that make sense?
15:16
<tamird>
almost - what would have to happen for HTML to depend on BufferSource? it may never, right?
15:16
<tamird>
AFAIK the introduction of websockets predates BufferSource, so the language never references it
15:19
<tamird>
@annevk well I updated my PR such that BufferSource is mentioned in the WS API. i suppose I'll just leave it for now
15:31
<nox>
annevk: https://johnmh.me/blog/2016/05/16/github-stupidity.html wtf
15:31
<nox>
(Re: the comments that disappeared.)
15:31
<nox>
Must be the illuminati.
15:32
<nox>
annevk: Oh wow, he is right. mark-otaris really got shadowbanned.
15:32
<Domenic>
https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS is pretty outdated
15:32
<nox>
I hope that's not because of that URL issue, or the GH people are really weird.
15:34
<nox>
Oh, shadowbanned because Tor.
15:34
<nox>
Weird.
15:50
<annevk>
That is shitty
15:58
<nox>
annevk: Yep.
15:58
<nox>
https://twitter.com/nokusu/status/732959239497523200
16:01
<nox>
gsnedders: Glad I don't have to change AAA in h5e. :)
16:01
<gsnedders>
nox: I still need to update html5lib-python to be up-to-date :)
16:02
<nox>
gsnedders: My sincere condolences. :)
16:02
<gsnedders>
nox: still having implemented all the <template> fun!
16:03
<nox>
gsnedders: I implemented <template> before all the slot stuff landed and shadow roots and who knows what else, I can't say I'm in a hurry to work on that again heh.
16:03
<gsnedders>
nox: probably will also find places where we'd applied specific spec patches without updating the rest
16:25
<Domenic>
zcorpan: so only a, audio, del, ins, map, noscript, and video *dont'
16:25
<Domenic>
* close open <p>s?
16:26
<Domenic>
that can't be right
16:26
<Domenic>
wait no that's not what this is about...
16:27
<Domenic>
maybe those are the only elements allowed to contain <p>s that also don't close <p>s
17:33
<tantek>
HTML(5) > (X)HTML
17:46
<gsnedders>
tantek: but what about XHTML5? *hideS*
17:58
<zcorpan>
Domenic: right. the rules for omitting tags only considers conforming DOM trees
18:00
<Domenic>
Oh good, we don't have to remove BroadcastChannel after all... (blink-dev)
18:02
<tantek>
gsnedders: There is no XHTML5. http://tantek.com/2010/302/b1/xhtml-dead-long-live-xml-valid-html5#losing-xmlns
18:06
<Mek>
Domenic: since you apparently care about BroadcastChannel, do you happen to know if firefox wrote any tests for it I could try running against my future implementation?
18:07
<Domenic>
Mek: no, sorry... I mostly just feel constant existential angst about features that are only implemented in one browser, so I was happy that BroadcastChannel is departing from that list.
18:07
<Mek>
makes sense
18:07
<zcorpan>
annevk: the "plan" is to be able to opt-in to CORS on a per-URL basis in CSS with extra syntax to url("" ...stuff here...)
18:11
<annevk>
zcorpan: yeah I know, though unclear how that’ll work yet
18:11
<annevk>
zcorpan: what’s the origin?
18:13
<zcorpan>
annevk: i haven't given it much thought. but it seems like the origin should be that of the document that included the top-level stylesheet
18:16
<annevk>
Think so too, otherwise you could get weird transitive stuff, hmm
18:22
<wanderview>
Mek: looks like we only have mochitests for BroadcastChannel... I think it was implemented before we had good adoption of wpt in the tree
18:24
<Mek>
wanderview: ah, okay, thanks
23:45
<Mek>
hmm, the firefox implementation of BroadcastChannel doesn't seem to entirely match the spec...