00:01
<JosephSilber>
ff respects the percentage height, while chrome does not
00:03
<TabAtkins>
Ah, this is due to a disagreement over whether "stretched" things are definite or not when the container is definite in the cross axis.
00:08
<zewt>
(oh yeah, the other big killer for chrome, the broken address bar autocompletion)
00:09
<TabAtkins>
JosephSilber: Firefox is correct - this was updated in the spec a while ago, and WK/Blink havent' updated yet: http://dev.w3.org/csswg/css-flexbox/#algo-stretch
00:11
<JosephSilber>
Is min-content considered a definite size?
00:12
<TabAtkins>
Nope.
00:13
<TabAtkins>
Just read the definition: http://dev.w3.org/csswg/css-sizing/#definite
00:13
<JosephSilber>
I thought so, but then why does it work? I guess it's considered an intrinsic height, but not a definite.
00:14
<TabAtkins>
I don't understand the question. Why does what work?
00:28
<Hixie>
zewt: oh ok
00:28
<Hixie>
zewt: weird
00:30
<zewt>
i guess
00:30
<zewt>
works well for me anyway :)
00:32
<Hixie>
i run out of room for my tabs going horizontally, nevermind vertically :-)
00:40
<zewt>
well the whole point is i can fit several times as many tabs vertically than horizontally
05:54
<Domenic_>
I want to start a conversation about adding GZIP and/or .zip file APIs to the web platform. What mailing list would people recommend? I'm thinking public-webapps?
05:54
<Domenic_>
Or whatwg@whatwg, perhaps.
06:08
<hendry>
Domenic_: talk to marcosc about zip files :-)
06:17
<Hixie>
Domenic_: anne was working on a zip: scheme or something for a bit
06:21
<Domenic_>
Hixie: yeah, but from what I remember he gave up on it.
07:19
<zcorpan>
Hixie: that svg paragraph, iirc it was added after people asking whether <svg xmlns:lol="wat"><lol:metadata such="wow"/> was valid in html
11:03
<zcorpan>
jgraham: Ms2ger: what do i need to do to run http://web-platform.test:8000/html/dom/interfaces.html ?
11:03
<Ms2ger>
Oh, right
11:04
<Ms2ger>
git submodules are broken
11:04
<Ms2ger>
Go into wpt/resources and git submodule update, or something
11:06
<jgraham>
Yeah, in theory git submodule update --recursive should work
11:07
<jgraham>
But it doesn't seem to for some reason
11:11
<MikeSmith>
I don't have a problem getting wpt/resources to update
11:11
<MikeSmith>
it updates fine for me with git submodule update --recursive
11:11
<MikeSmith>
the problem I run into is for wpt/tools
11:12
<MikeSmith>
which I deal with by doing "mv ./tools tools-old; git submodule init; git submodule update"
11:12
<MikeSmith>
or something like that
11:14
<MikeSmith>
hmm or at least dirtiness for wpt/resources goes away after submodule update --recursive
11:15
<MikeSmith>
but I guess that doesn't mean it's necessarily pulling the latest from the resources repo
11:15
<MikeSmith>
question mark
11:18
<jgraham>
MikeSmith: It's resources/idlharness that's the problem (that might not be the right name)
11:18
<MikeSmith>
ah ok
11:19
MikeSmith
shuts up and tries pulling to see what happens
11:20
<Ms2ger>
MikeSmith, if you just follow the readme, you get an empty wpt/resources/webidl2
11:20
<MikeSmith>
oh, initially you mean?
11:21
<MikeSmith>
the very first time?
11:21
<MikeSmith>
so yeah I guess I remember having needed to do that
11:21
<zcorpan>
well... http://web-platform.test:8000/resources/WebIDLParser.js is still 404 for me
11:22
<webben>
I'm looking for prior art on how an application (a server in my case) should handle query strings like http://example.com?%atfoobar
11:22
<Ms2ger>
zcorpan, is webidl2 non-empty?
11:22
<webben>
note the "t" which makes %at not represent a percent-encoded code point
11:22
<zcorpan>
Ms2ger: it's empty
11:23
<webben>
as far as i can tell the url parsing algo at https://dvcs.w3.org/hg/url/raw-file/tip/Overview.html#parsing just would return me "http://example.com?%atfoobar"; again
11:24
<Ms2ger>
Don't look at that
11:24
<Ms2ger>
The spec is at url.spec.whatwg.org
11:24
<webben>
I'm wondering if it's "correct" ("safe"?) error handling to treat such it equivalently to http://example.com?%25atfoobar
11:24
<webben>
Ms2ger: oooh. ty
11:24
<Ms2ger>
zcorpan, okay, I don't remember what the incantation is to get it updated
11:26
<webben>
hmm
11:26
<MikeSmith>
yeah I just tried a fresh resources/ submodule update from there and I get an empty webidl2 dir
11:26
<webben>
so looking at that, it's the same result, "http://example.com?%atfoobar";, except it's a non-fatal parse error
11:27
<MikeSmith>
if I cd into resources/ and do git pull it fails because it's a detached branch
11:28
<webben>
so I guess from the perspective of a server it's not unreasonable to correct to http://example.com?%25atfoobar (?)
11:29
<webben>
oh actually
11:29
<webben>
maybe that's what the spec is saying to do
11:30
<webben>
mmm ... ok only in the case of the fragment not the query
11:30
<zcorpan>
webben: what do you mean from the perspective of a server? what are you trying to do?
11:32
<webben>
Third-parties are generating query strings like ?a=quux&foo=bar&somethingelse=%atfoobar to my server. I'd like to capture these URLs, pull out data from the query strings, and generally process the request.
11:33
<webben>
My server happens to be delegating parsing the query string to some Jetty code, which emits from its depths an InvalidArgumentException when it tries to percent-decode %at
11:33
<webben>
I'm just wondering what the least incorrect error handling could be
11:34
<webben>
(and whether jetty's behavior could be improved for that matter)
11:34
<webben>
(this deep exception is thrown from a call like httpRequest.getRequestParams() )
11:35
<MikeSmith>
zcorpan: it appears you have to cd to resources/ and then do a git init && git submodule update within there too and then the webidl2 directory will get populated. I don't know if that's that only way or the right way, but it does actually work at least. (And so I guess the --recursive flag to git submodule udpate doesn't really mean what it claims to mean)a
11:35
<webben>
so I'm wondering whether, for example, we should try to "correct" the url to http://example.com?a=quux&foo=bar&somethingelse=%25atfoobar before delegating to jetty
11:37
<zcorpan>
MikeSmith: not git submodule init ?
11:37
<webben>
zcorpan: Does this make any sense as a problem statement, at least?
11:37
<zcorpan>
webben: yes
11:38
<zcorpan>
webben: so either jetty could implement the url spec and not throw an exception
11:39
<zcorpan>
webben: or you could regexp fixup the url before handing it to jetty
11:40
<webben>
i wonder if jetty behavior were to change, how they should best signal a parse error without throwing an exception.
11:41
<MikeSmith>
zcorpan: yeah sorry I meant git submodule init (I should have just pasted it instead of retyping)
11:49
<jgraham>
MikeSmith: If the readme is wrong, maybe you could fix it?
12:01
<zcorpan>
ok now the tests run
12:01
<zcorpan>
i failed to recover from git init though
12:03
<jgraham>
Shouldn
12:03
<jgraham>
't git init on an existing repo be a noop
12:03
<jgraham>
?
12:04
<jgraham>
I guess it might not interact well with submodules, but if so that seems like a bug
12:06
<zcorpan>
it wasn't a noop for me when i ran it in resources/
12:21
<MikeSmith>
zcorpan: sorry :(
12:21
<MikeSmith>
jgraham: yeah I will update the readme
15:25
<Ms2ger>
Are he blink UseCounter results public?
15:26
<Ms2ger>
*the
15:54
<mathiasbynens>
Ms2ger: there’s http://www.chromestatus.com/metrics/css/animated but other than that, I don’t think so
15:54
<mathiasbynens>
i meant http://www.chromestatus.com/metrics/css/popularity
15:54
<Ms2ger>
I found some 0% claims in another thread, which made me happy :)
16:03
<SimonSapin>
annevk-cloud, hsivonen: Do you agree that CSS’s "environment encoding" is a legacy thing and we don’t want new formats or linking mechanisms to define it?
16:33
<gsnedders>
SimonSapin: Do we not just want it to be UTF-8 in any new case?
16:34
<SimonSapin>
gsnedders: That’s the idea. If not provided, the next fallback is UTF-8
16:34
<gsnedders>
SimonSapin: Well surely it doesn't matter if they define it or not, given the environment encoding will be UTF-8 :)
16:35
<SimonSapin>
Well :)
16:35
<SimonSapin>
This includes not having a charset attribute, for example
17:07
<dglazkov>
good morning, Whatwg!
17:15
<Ms2ger>
My dear dglazkov!
18:48
<jgraham>
MikeSmith: So git submodule update --init --recursive does what you might think that git submodule update --recursive would do
18:56
<Hixie>
foolip: wtf is MSE?
18:58
<jgraham>
Hixie: Media Source Extensions
18:59
<Ms2ger>
Is that ROT13(DRM)?
18:59
<Hixie>
what are those?
18:59
<jgraham>
https://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html
18:59
<jgraham>
No, this is for adaptive streaming using javascript
19:00
<Hixie>
(aw, another non-rfc-2119 spec)
19:01
<Hixie>
looks like a cool idea, i guess
19:01
<Hixie>
though seems like more effort than just having the browsers do it
19:01
<Hixie>
but ok
19:01
<Hixie>
any idea why they try to change TextTrack?
19:11
<annevk>
Hixie: to add SourceBuffer?
19:11
<annevk>
but I guess you could tell as much
19:11
annevk
goes back to doing useful stuff
19:28
<Hixie>
annevk: i mean, why do they make kind and language mutable
19:29
<Hixie>
falken: did the patch on https://www.w3.org/Bugs/Public/show_bug.cgi?id=20418 fix all our problems?
19:30
<Ms2ger>
Hixie, fyi, updates in https://www.w3.org/Bugs/Public/show_bug.cgi?id=22118
19:30
<Hixie>
thanks
19:30
<Ms2ger>
Also, we might be able to drop document.all()
19:31
<Hixie>
yeah i saw that
19:31
<Hixie>
that's great!
19:35
<Hixie>
Ms2ger: more comments in that bug :-)
19:35
<Ms2ger>
\o/
19:35
<Hixie>
anyone want to make a call on https://www.w3.org/Bugs/Public/show_bug.cgi?id=24312 regarding what exactly i should spec?
19:35
<Hixie>
(<img> reloading when adopting)
19:36
<Ms2ger>
Aaaand I'm out :)
19:37
<annevk>
Hixie: hmm weird, I suppose language can change over time, dunno about kind
19:37
<Hixie>
languages of subtitles changing over time seems wildly crazy to me
19:37
<Hixie>
i'll be back later. gonna go get food.
19:50
<annevk>
SimonSapin: new formats or linking mechanisms should enforce utf-8 for themselves and subresources
19:51
<SimonSapin>
annevk: that’s different still. But I guess they can always do UTF-8 decoding themselves and parse the result like they would <style>
19:52
<annevk>
SimonSapin: yeah, you want some kind of override flag like the HTML parser has
19:52
<annevk>
SimonSapin: for these contexts
19:53
<SimonSapin>
annevk: I mean, parsing from code points is an existing hook, so CSS Syntax does not need to add a "UTF-8 only" hook for parsing from bytes
20:14
<Hixie>
annevk: does https://www.w3.org/Bugs/Public/show_bug.cgi?id=19505 look right? (the final proposal)
20:28
<annevk>
Hixie: yeah I think so
20:28
<annevk>
SimonSapin: you don't really want to have to decode / parse in some other spec when all you need is parse
20:29
<annevk>
SimonSapin: especially since it might lead implementers astray from doing the right thing
20:32
<Hixie>
annevk-cloud: k, i'm putting it in
21:54
<aleray>
hi, how can I prettyprint with html5lib python? I'm using lxml but this code does not output pretty html: http://dpaste.com/1589423/
21:55
<aleray>
not sure if I should serialize using lxml or if I should rather use the html5lib serializer
22:27
<TabAtkins>
I'd like an answer to that, too - I haven't investigated pretty-printing yet, but Bikeshed's output is *really* ugly. ^_^