06:29
<annevk>
Kinda wish we had removed that wget dependency before I installed it
06:29
<annevk>
Oh well, now the next person won't have to
07:10
<MikeSmith>
yeah
07:14
<cvrebert>
Is it just me, or is drafts.csswg.org unreachable?
12:32
<Ms2ger>
Nice: http://www.computerworld.com/article/2851719/slack-now-lets-employers-tap-workers-private-chats.html
12:55
<ato>
Ms2ger: Isn’t that what we’re switching to? (-:
13:01
<jgraham>
Well to be fair to them, it sounds like it's non-trivial to enable and clear when it is enabled
13:01
<jgraham>
And I hope no one is switching to them!
13:05
<gsnedders>
MikeSmith: why have I left the HTML WG?
13:07
<Ms2ger>
Because it's a cesspit of flamewars and inscrutable Process?
13:10
<MikeSmith>
gsnedders: you only were joined for like one day
13:11
<MikeSmith>
I have no idea why it kicked you
13:11
<MikeSmith>
maybe your affiliation changed?
13:11
<gsnedders>
nothing indicating that?
13:11
<gsnedders>
And /I/ haven't changed anything!
13:11
<MikeSmith>
nothing I can see
13:11
<MikeSmith>
well anyway you're not missing anything
13:12
<MikeSmith>
I don't know why you don't just join webapps wg isntead
13:12
<gsnedders>
I have joined webapps :P
13:12
<MikeSmith>
ah ok
13:13
<wilhelm_>
I'd kick out gsnedders too.
13:32
jgraham
concludes that wilhelm_ is the ghost in the machine
13:40
wilhelm_
changes his business card.
13:49
<annevk>
Hmm
13:49
<annevk>
GitHub can't show the diff for my Fetch PR
13:53
<Domenic>
This should be fun
13:53
<Domenic>
It'll be best to review the HTML diff anyway
13:54
<Domenic>
In the end though this is going to be one of those PRs where you mostly just trust the author. Maybe we'll spot some editorial things.
13:58
<tantek>
annevk: just ship it and have people review the total end result.
13:58
<jgraham>
annevk: Pointer?
14:00
<annevk>
https://github.com/whatwg/html/pull/144
14:00
<annevk>
tantek: idea is currently that changes to the HTML Standard will get some review first
14:03
<jgraham>
That's not even a very big diff
14:03
<jgraham>
All these tools suck :(
14:04
<tantek>
annevk - ok
14:04
<Ms2ger>
There's always https://github.com/whatwg/html/pull/144.diff
14:09
<zcorpan>
wtf github
14:09
<zcorpan>
should we use critic?
14:10
<zcorpan>
i suppose critic is differently annoying in that it gets confused if you --amend
14:11
<Ms2ger>
Maybe reviewable
14:11
<jgraham>
reviewable refuses to display the spec
14:11
<Ms2ger>
But both suck at reviewing single-file diffs
14:11
<annevk>
Domenic: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21674 so many fun cross-origin scripting issues
14:11
<jgraham>
I'm happy to try critic, but the no-force-push thing does seem to upset people
14:11
<jgraham>
I mean I'm happy for you to try critic
14:12
<annevk>
We do use force push
14:14
<jgraham>
But you don't have to, is the point
14:15
<jgraham>
Right up until you want to rebase and have merge conflicts and want them reviewed, or until the review is accepted if you don't have push access yourself
14:15
<annevk>
True
14:17
zcorpan
views the diff in GitUp
14:19
<zcorpan>
annevk: data-noexport="" vs. data-noexport - any reason not to use the latter?
14:20
<annevk>
zcorpan: style consistency
14:20
<annevk>
zcorpan: I would be okay with a PR to change the style throughout though, and drop ="" everywhere
14:20
<zcorpan>
k
14:20
<annevk>
zcorpan: provided wattsi can handle that
14:21
<zcorpan>
i'm sure Hixie implemented that part of the tokenizer correctly :-)
15:01
<annevk>
(Thanks for the feedback on the Fetch PR, will address it tomorrow. Have been working on that for over a week so taking a small break.)
15:23
<JakeA>
TabAtkins: If a flexbox contains wrapped items, is there a way to make the parent box the width as the longest line?
15:23
<JakeA>
Rather than width of the flexbox's container
15:24
<TabAtkins>
width:max-content, though support is spotty currently
15:24
<TabAtkins>
Oh wait
15:24
<TabAtkins>
Never mind, I see what your asking for
15:28
<TabAtkins>
I don't *think* there is. Shrink-wrapping doesn't work; once a float has to wrap, it's full-size regardless.
15:56
<annevk>
Domenic: whoa that Twitter discussion
15:57
<Domenic>
yeah, meh
15:57
<annevk>
Domenic: splitting a response across a Response class and some Error subclass seems mighty weird
15:57
<Domenic>
I think the current design is great.
15:58
<JakeA>
ohh, that discussion took to Twitter did it?
15:59
<JakeA>
TabAtkins: is https://drafts.csswg.org/css-sizing-3/#fit-content-size it?
16:00
<TabAtkins>
No, that's shrink-wrapping
16:05
<annevk>
JakeA: https://twitter.com/trodrigues/status/643705867767054336
16:10
<JakeA>
hm, I replied in the comment
16:10
<JakeA>
s
16:12
<annevk>
ah good
16:24
<JakeA>
fwiw, I'd still like an option to reject on !response.ok
16:25
<JakeA>
But maybe only cache.addAll benefits from that, in which case that option should go there
16:27
<nox>
TabAtkins: With the new CSS specs you are writing, is there anything that allow us to express https://html.spec.whatwg.org/multipage/#magic-border-selector?
16:29
<TabAtkins>
No; we don't yet have anything in Selectors that parses attribute values as anything other than strings.
16:30
<TabAtkins>
We have a pending suggestion, currently punted to level 5, to allow numeric comparisons in the attr selector, so you could write ":matches([border < 0], [border > 0])", or if you only care about positive values, just [border > 0].
16:31
<zcorpan>
TabAtkins: i suppose that wouldn't use html's "rules for parsing non-negative integers"
16:31
<nox>
TabAtkins: Nice.
16:31
<TabAtkins>
zcorpan: Nah, would use CSS's rules for parsing integers.
16:31
<TabAtkins>
Which is probably okay to switch to, compat-wise?
16:31
<nox>
They are different? :o
16:31
<TabAtkins>
Dunno, probably a little.
16:32
<TabAtkins>
Looking over it, CSS's rules are more expansive.
16:33
<zcorpan>
TabAtkins: got a link to css's rules?
16:33
<TabAtkins>
The numeric comparer would almost certainly just parse the attr as a <number>, not an <integer>, and CSS allows scinot.
16:33
<TabAtkins>
I think it's a strict superset.
16:34
<TabAtkins>
zcorpan: https://drafts.csswg.org/css-syntax/#consume-a-number
16:34
<TabAtkins>
zcorpan: Assuming we strip whitespace, which we would.
16:37
<Domenic>
JakeA: and I still think you actually want something more composable than that for cache.addAll, like a general way of guaranteeing atomicity or doing rollbacks or similar, on any condition not just the single built-in one.
16:38
<zcorpan>
TabAtkins: i suppose it would be a bit weird to use css's number parsing here in an html attribute but html's rules elsewhere. but also, it's super-annoying to have different rules in JS/HTML/CSS
16:55
<nox>
:integer(border) < 0? :P
16:57
<JakeA>
TabAtkins: btw, the layout we were looking at was http://jsbin.com/qufiza/edit?html,css,output, where the block of items were centered, but the items were still left aligned
16:57
<nox>
TabAtkins: Couldn't just the numeric comparer keep the type flag as integer in attribute selector context?
16:58
<nox>
Oh wait, some HTML attributes correspond to presentational hints that must be parsed as numbers, I guess?
16:59
<zcorpan>
nox: you wouldn't want integer for all attributes. e.g. <input step=0.5>, <div data-foobar=...>
16:59
<nox>
zcorpan: I see.
17:01
<TabAtkins>
CSS actually matches JS really closely now. Would have to look up the spec to see how exactly, but since we added scinot it got a lot closer.
17:02
<TabAtkins>
And CSS *integers* match HTML exactly, it's just that there's no real call for an "integer only" falling in the numeric comparison selectors.
17:03
<TabAtkins>
s/falling/flag/
17:05
<zcorpan>
TabAtkins: html ignores trailing garbage, which in css makes it a dimension instead of an integer, no?
17:05
<zcorpan>
border="1em"
17:05
<TabAtkins>
There's nothing wrong with a rule like [border >0] { border-width: attr(border px); } except for minor compat
17:05
<TabAtkins>
Oh, didnt know it ignored garbage.
17:05
<TabAtkins>
It would just be invalid in CSS then
17:06
<TabAtkins>
Since yeah, that would parse as a dimension rather than a number.
17:06
<TabAtkins>
(That rule was very annoying to type in a phone keyboard.)
17:07
<TabAtkins>
So assuming that's necessary, CSS won't really be able to help.
17:08
<zcorpan>
i don't know what the compat situation is, but i suppose there's non-zero amount of trailing "px" in html, and it would be bad to break that. maybe we could start supporting number-or-dimension, but personally i'm not so interested in pursuing that
17:09
<TabAtkins>
Yeah. CSS isn't interested in supporting that with syntax either, so not much worth in changing HTML.
17:28
<yhirano_>
wanderview, Domenic, annevk: are you guys going to attend TPAC 2015? I may be there and it would be great if we can talk about streams / fetch.
17:29
<wanderview>
yhirano_: annevk and I will be there... I think Domenic said he would not be there
17:31
<wanderview>
yhirano_: would be great to meet and talk about streams/fetch
17:31
<Domenic>
yhirano_: I will be in Japan around that time for vacation but not for TPAC. I could meet up in Tokyo before/after if desired.
17:34
<yhirano_>
wanderview: thanks, let's talk. maybe in an adhoc meetings slot? (I've never attended TPAC, so please correct me if I'm wrong)
17:36
<wanderview>
yhirano_: I've never been there either... I'm sure we can find time, though... I'll be there Mon to Thu morning
17:39
<yhirano_>
Domenic: yeah, if you could. Maybe we have blink-specific things (e.g. v8 extras) to talk about, too. I'm sorry I couldn't spend enough time for it this quarter.
17:42
<yhirano_>
Domenic: but I will be in MTV /SFO in Nov (for BlinkOn), so feel free to enjoy your vacation.
17:50
<yhirano_>
wanderview: thank you.
17:56
<Domenic>
yhirano_: sounds good! I will also be at BlinkOn. We can figure out a specific plan as the time draws closer.
17:58
<schalkneethling>
still trying to make sense of the crossorigin attribute on the video element :-/ Who would have thought so much discussion can happen around a single attribute ;) One thing I am still unclear of is what credentials are being sent when a user uses either crossorigin=anonymous for local requests or crossorigin=use-credentials for CORS requests? Are these specific HTTP headers that are set or, not set?
18:10
<schalkneethling>
Ah, I believe I have found the details on this https://html.spec.whatwg.org/#concept-media-load-resource
18:10
<schalkneethling>
proceeding to read the details
18:43
<Domenic>
https://twitter.com/domenic/status/643851648461369344
20:50
<JonathanNeal>
Thanks Domenic, just made a pull for the ul typo, hope I got it right https://github.com/whatwg/html/pull/146
20:50
<Domenic>
JonathanNeal: LGTM! :)
20:50
<caitp>
looks right to me
20:50
<Domenic>
Hmm are you in the acks yet?
20:51
<JonathanNeal>
Who me? what are the acks?
20:51
<Domenic>
Acknowledgments, heh.
20:55
<JonathanNeal>
Don’t know about them. Maybe setup a CONTRIBUTING.md doc?
20:55
<JonathanNeal>
I could make a pull request for that too :)
20:56
<JonathanNeal>
I have this rather generic one I’ve assembled, for example: https://github.com/jonathantneal/postcss-partial-import/blob/master/CONTRIBUTING.md
20:57
<Domenic>
JonathanNeal: in the past annevk has preferred keeping things in the readme so people just have to read that. Which makes sense to me. I agree the adding-yourself-to-the-acks should be noted though. Would be happy for you to do a PR for that :)
20:58
<JonathanNeal>
Yea, but CONTRIBUTING.md gets put at the top of every new issues page, look: https://github.com/jonathantneal/postcss-partial-import/issues/new
20:58
<JonathanNeal>
“Please review the guidelines for contributing to this repository.”
20:58
<Domenic>
sure, but nobody actually sees that :P
20:59
<JonathanNeal>
I do :( and it can be a link in the README.md as well, just link you can link to your license from there. Don’t see a LICENSE.md.
20:59
<JonathanNeal>
s/just link/just like
21:00
<Domenic>
license is in the spec along with attributions
21:00
<JonathanNeal>
Would you like additions to the acknowledgements as a separate commit?
21:00
<Domenic>
Sure, that would be great
21:00
<JonathanNeal>
These are also things to put in CONTRIBUTING.md. Then when you want things formatted a certain way you just ask them to modify their commit to follow it. No repeating instructions as much as pointing.
21:01
<Domenic>
We prefer README.md as a location for those instructions.
21:01
<JonathanNeal>
Sure. </sell>
21:05
<Domenic>
JonathanNeal: oh, I'm sorry, I misread. One commit please...
21:06
<Domenic>
I can squash it
22:38
<chimeno>
Good project! I'll try to contribute
22:40
<Domenic>
:)
22:56
<Domenic>
Trying to generate a html diff for annevk's fetch patch is really heating up my CPU
23:48
<JonathanNeal>
TabAtkins: http://jonathantneal.github.io/postcss-nesting/ a live demo of how I think you told me @nest should work, alongside custom selectors and custom properties
23:48
<TabAtkins>
JonathanNeal: @nest requires an & in the selector.