00:22
<TabAtkins>
Hixie_: <iframe seamless> imports the stylesheets from the surrounding document, but selectors still don't match across the iframe boundaries, right?
00:23
<kennyluck>
I hope someone can answer some fundamental questions about the flex layout that I still haven't figured out...
00:23
<TabAtkins>
Yo.
00:23
<kennyluck>
What's the point of having 'flex-basis'?
00:24
<kennyluck>
When it usually just means 'width' and 'height'?
00:24
<kennyluck>
s/and/or/
00:24
<TabAtkins>
It abstracts width/height into the flex axis, so you don't have to worry about which property to use in the common case.
00:24
<TabAtkins>
It also lets you cascade width/height and flexibility separately if you wish.
00:27
<kennyluck>
TabAtkins, hmm… ok, thanks. What about this, suppose I want to set the flex basis of an element to, say, 100px, am I more encouraged to do 'flex: 1 100px' than 'flex: 1auto; width: 100px'?
00:27
<TabAtkins>
Either one works. If you don't specifcially need the cascading ability, the former is simpler, so might as well use that.
00:28
<kennyluck>
TabAtkins, is there an good use case of casding width and flex-basis separately?
00:29
<TabAtkins>
Same as cascading anything separately.
00:29
<kennyluck>
Not I don't believe in it. Just want to know.
00:29
<TabAtkins>
It's one of those fundamental abilities that is useful sometimes. Dont' have any specific examples off the top of my head.
01:37
<Hixie_>
TabAtkins: nothing will ever match * > :root, right
06:05
<annevk>
So I'm thinking about URL conformance, does it even make sense to have a valid URL concept without caring about the scheme?
06:07
<annevk>
Otherwise you get this thing where "data:test" is "valid" but actually it is not and should be flagged
06:08
<annevk>
And you could even have "data:te st" which is in "error", but comes out of parsing as "data:te%20st" which is "valid" but actually it is not and should be flagged
06:11
<annevk>
What seems kind of consistent is that you have a "scheme", a data part, and a "fragment"
06:11
<annevk>
with the data part being dependent upon the "scheme"
06:30
<annevk>
btw, if you type in "data:test" in Opera and hit enter, it hangs a little
06:31
<annevk>
zcorpan: is there an open bug on removing media from <source>?
06:31
<zcorpan>
annevk: i thought there was but couldn't find it from a 1-minute search
06:36
<annevk>
zcorpan: https://www.w3.org/Bugs/Public/show_bug.cgi?id=19619 (filed a new one)
07:01
<annevk>
Hixie_: the default styles for <pre><code> yield in too much orange: http://encoding.spec.whatwg.org/#api
07:01
<annevk>
Hixie_: even for the Dutch
07:01
<zcorpan>
all: default; seems scary
07:20
<annevk>
Chrome's debugger seems to have the ability to modify a script, but how do I run the script after I made the modifications?
07:21
<annevk>
In particular I'm trying to figure out why dfn.js fails for http://url.spec.whatwg.org/
07:21
jgraham
thought annevk had his text editor set up to orange-on-orange anyway
07:21
<annevk>
maybe the easiest is for me to simply copy dfn.js and do the thing locally
07:22
<jgraham>
Undefined variable getCookie?
07:23
<jgraham>
(which means that the init function is never called afaict)
07:25
<jgraham>
Oh still doesn't seem to work if I "fix" that
07:26
<annevk>
the problem is a reference to "constructor"
07:27
<annevk>
most other specs I write call that bit "constructors"
07:31
<annevk>
jgraham: fwiw, the getCookie thing also still fails, but doesn't cause total breakage
07:31
<annevk>
I'll just name it "Constructors" for now; arguably it's several anyway because of the optional argument
07:41
<zcorpan>
TabAtkins: you realize you made yourself look like a dick on twitter over the "authors" thing?
07:47
<hsivonen>
so many holes in XML enforcement
07:47
<hsivonen>
bogus charsets work as in HTML instead of causing the YSoD
07:48
<hsivonen>
I wonder what kind of breakage would ensue if I made this tough compliant.
07:48
<hsivonen>
s/tough/stuff/
07:49
<annevk>
hsivonen: we can also change the respective encodings to emit a FFFD instead of a decoder error
07:49
<hsivonen>
I mean bogus charset names
07:50
<hsivonen>
I don't have an opinion on what we should do on either invalid data or bogus names. For now, I try not to fix too many bugs at the same time to get better regression windows.
07:51
<hsivonen>
This old parser code is annoying to look at. When I look at it to fix one bug, I see three more.
07:52
<hsivonen>
I should get around to rewriting all this.
07:53
<zcorpan>
hsivonen: seems chrome shows YSoD. (not opera) http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1854
07:53
<zcorpan>
haven't tested http content-type
07:54
<hsivonen>
zcorpan: nice to see Chrome is compliant
07:55
<zcorpan>
(chrome also shows ysod for x-user-defined in the xml decl)
07:57
<hsivonen>
Where did Leif put his XML BOM tests?…
07:57
<zcorpan>
no ysod for http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1855
08:51
<jgraham>
Speaking of people coming across badly, some of the rhetoric in the <maincontent> thread really needs to be toned down
08:54
<jgraham>
And speaking of twitter, is there an equivalent to the parable about bind men and the elephant to describe the situation where people are hampered in their understanding not by an incomplete set of input data, but by insufficent communication bandwidth?
08:55
<jgraham>
*blind
09:17
<krijn>
Made a backup of all the static logs on http://krijn.html5.org/irc-logs/, in case my server goes down again
09:18
<krijn>
2012 isn't there yet
09:24
<Stevef__>
jgraham: re <maincontent> if I need to tone down please feel free to point out where
09:25
<jgraham>
Stevef__: I wasn't really refering to you :)
09:26
<jgraham>
Stevef__: You might like to fix the title case in your use case document
09:26
<annevk>
Stevef__: did you ever reply to hsivonen?
09:26
<annevk>
Stevef__: I agree with him that it needs a one-word name
09:27
<Stevef__>
jgraham: that makes a change :-) have been trying best to be good, I was afraid my respone to Hixie last night might have been a bit OT as I had been to a wine tasting at a vineyard in carcassonne
09:28
<zcorpan>
aren't you supposed to spit it out after tasting?
09:28
<jgraham>
Stevef__: Well if there was something, I might have skipped over it :)
09:28
<Stevef__>
annevk: re name, right I responded to maciej over on html wg list http://lists.w3.org/Archives/Public/public-html/2012Oct/0112.html and henri also tweeted at me about it
09:29
<Stevef__>
annevk: have no problem with chnaging it, just leaving it for a bit for more feedback
09:30
<annevk>
just wondering as you replied to every other email in the WHATWG thread
09:30
<annevk>
I'm fine with letting people bikeshed on, I employ similar tactics
09:31
<Stevef__>
annevk: as i had replied to ian yang on list about the name and relied to henri offlist didn't think it needed a repsonse, the more substantive stuff about parsing UA stylesheet i captured in a bug and ccd him
09:32
<annevk>
sure, as I said, just wondering :)
09:32
<annevk>
sounds like you're on top of it
09:34
<Stevef__>
am trying to be...
09:37
<zcorpan>
Stevef__: do you have a dataset of top 10,000 pages with urls now, btw?
09:39
<Stevef__>
zcorpan: I have a data set generated late last month with each file in a folder that uses the URL as a name, and also each file has a comment in it with the URL
09:39
<zcorpan>
Stevef__: sounds nice. is it available online?
09:40
<Stevef__>
zcorpan: will make available when i get back home am in France at the moment, will ping you when it available
09:40
<zcorpan>
cool thanks
09:41
<annevk>
new datasets?
09:42
<annevk>
sweet
09:42
<Stevef__>
same URL list that i did back in march
09:44
<Stevef__>
gotta travel up to toulouse now to catch a big bird home catch you all later
10:33
<hsivonen>
does the W3C test suite support setting the content-type header now?
10:35
<jgraham>
Well sure, if you make a .htaccess file
10:36
<hsivonen>
ok
10:36
<hsivonen>
the mochitest mechanism of having a foo.bar^headers^ file is quite nice
10:37
<jgraham>
Yeah
10:38
<jgraham>
One could port that to apache if people thought that it was a significant improvement over .htaccess files I guess
10:38
<jgraham>
In general lack of standardisation of the server-side component of testing is a big problem
10:39
<hsivonen>
does anyone have CSS BOM precedence tests yet?
10:39
<jgraham>
That is Opera + Mozilla + WebKit + IE (presumably) all have different setups
10:39
<jgraham>
And making one test that can run in all environments can be tricky
10:40
jgraham
goes back to removing Opera-specific server names from some tests
10:52
<hsivonen>
annevk: FYI, http://idpf.org/epub/30/spec/epub30-publications.html#tbl-core-media-types has some non-IANA font MIME types
10:52
<odinho>
jgraham: You knight in shining armour ;-)
10:53
<jgraham>
Saying something about a queen?
10:54
<hsivonen>
application/epub+zip is unregistered, too
10:55
<hsivonen>
looks like the IDPF has given up on IANA
10:57
<jgraham>
Like everyone else then?
11:10
<hsivonen>
does JS process \u escapes before or after tokenization?
11:10
<hsivonen>
can \u escapes be used in indentifiers?
11:11
<jgraham>
Yes
11:11
<hsivonen>
thanks
11:11
<jgraham>
Which is less evil? A 32Mb file in version control or a PHP script to output 32Mb of data?
11:12
<odinho>
hsivonen: And before you could var v\u0061r = hello; and it would use "var" as a variable name. But not anymore :D
11:13
<odinho>
jgraham: Hm, -- if the version control does gzip, or handles sparse files, the 32mb of data could be compressed to almost nothing.
11:13
<odinho>
jgraham: Although I'd probably go with PHP script. Because we have lots of those already.
11:13
<jgraham>
odinho: You I guess 32Mb of highly compressible text might not be too bad. I think git at least compresses
11:14
<jgraham>
I don't want to use PHP if I don't have to if it a problem for WebKit/Mozilla
11:14
<odinho>
jgraham: But if they want to run CORS/XHR and other tests that need a server component, -- they have to support it anyway.
11:15
<hsivonen>
hmm. Is U+0E4F banned as the first character of a JS identifier?
11:15
<hsivonen>
oh. well. I’ll try not to overdo this test
11:15
<odinho>
So I think/hope/pray (no, not the last one) that they will get it soon.
11:16
<jgraham>
odinho: Well they have a server component
11:16
<jgraham>
It just doesn't support PHP
11:16
<odinho>
I would guess they're interested to fix that.
11:17
<jgraham>
hsivonen: http://es5.github.com/#x7.6
11:17
<jgraham>
odinho: Well no one has said to me "yeah, PHP, that sounds like a good idea, we'll get right on it"
11:17
<zcorpan>
hsivonen: http://dvcs.w3.org/hg/web-ecmascript/file/e0a9564ea062/identifiers/index.html
11:18
<jgraham>
Dunno what webkit does, but Mozilla have some custom javascript server that they can control from within the test
11:18
<odinho>
jgraham: They should. They should run my tests.
11:18
<jgraham>
odinho: Do they show bugs in Mozilla/WebKit?
11:18
<odinho>
Yeah, some.
11:18
<odinho>
Ofc.
11:18
<odinho>
It's the web, man.
11:18
<jgraham>
You should tell sicking that
11:19
<hsivonen>
thanks. I’m slightly annoyed about the spec trying to use Unicode classes instead of treating runs of code points as opaque strings
11:19
<hsivonen>
but not a real problem
11:19
<hsivonen>
I was just trying to make a variable name that matches the UTF-8 BOM decoded as Windows-874
11:20
<smaug____>
odinho: FYI, on Mozilla's httpd.js server one can run .sjs scripts. Something like http://mxr.mozilla.org/mozilla-central/source/browser/base/content/test/authenticate.sjs
11:23
<smaug____>
IIRC for websockets we use pywebsocket server
11:23
<odinho>
smaug____: I've looked a bit at it, but that only works for mozilla, so it won't do putting that on w3c-test.org
11:24
<smaug____>
right
11:24
<jgraham>
Yeah, obviously reusing an XPCOM-based server wholesale isn't going to fly
11:24
<odinho>
Although if we had a common server side format that'd be so much nicer.
11:24
<smaug____>
does w3c-test.org support only php ?
11:24
<odinho>
I don't care if it's PHP, Python or server side javascript.
11:24
<jgraham>
Well I think we have pywebsocket and jetty for web sockets tests
11:24
<odinho>
(As long as it's not Perl)
11:24
<jgraham>
But the problem isn't really PHP-vs-foo
11:25
<jgraham>
It's "how do we get everyone running the tests in their own test infrastructure"
11:25
<odinho>
Yes. That's the "common" part.
11:25
<smaug____>
--odinho
11:25
<jgraham>
Which means that it has to be a system that works for a number of setups
11:25
<odinho>
smaug____: Waaa :'(
11:26
<smaug____>
(Perl is way nicer than Python :) )
11:26
<jgraham>
(smaug____ is obviosuly crqazy)
11:26
<jgraham>
In particular it has to work for people that want to distribute all tests to each slave
11:27
<jgraham>
And I guess they might not want to have to get apache + PHP running on each individual salve?
11:27
<jgraham>
*slave
11:27
<jgraham>
(I don't really know the rationale for the current Mozilla design, so I can't tell what would work for you guys)
11:27
<smaug____>
I'd assume python based server side thing might be the easiest to sell to Mozilla
11:28
<jgraham>
smaug____: Any idea who at Mozilla I should talk to about this?
11:29
<odinho>
I like Python too. I'd be willing to rewrite all my server side php things to some python server side resource.
11:30
<jgraham>
Yeah, there isn't enough stuff on w3c-test.org that migration is a serious problem at the moment
11:30
<jgraham>
But we need to find a solution that works for everyone asap
11:30
<odinho>
Agreed! :D
11:30
<smaug____>
jgraham: probably ted
11:31
<jgraham>
I don't know if I know who that is :) Is that an email address?
11:31
<odinho>
https etc will be a bit strange though.
11:31
<odinho>
And maybe the test system should have some common.js as well where settings like expected domains and ports etc can be set.
11:32
<jgraham>
Well if you run your own server you can control things like that
11:33
<jgraham>
I mean if there is one common setup that everyone uses, we can go with convention over configuration
11:35
<smaug____>
jgraham: use bugzilla as phonebook
11:35
<smaug____>
type :ted to the cc field
11:35
<jgraham>
Hah
11:35
<annevk>
hsivonen: at some point I'd like to fix MIME type parsing and registration
11:36
<jgraham>
Does anyone that works on WebKit still hang out here?
11:37
<annevk>
jgraham: there's several, e.g. arv, abarth, othermaciej, beverloo, ...
11:37
<jgraham>
Yeah, but I never see them :)
11:38
<jgraham>
I guess WebKit isn't even the right level
11:38
<jgraham>
Might need someone from Chromium and someone from Safari
11:38
<jgraham>
(they have seperate test systems, right?)
11:39
<smaug____>
well, webkit related tests are in webkit's tree
11:40
<smaug____>
but doesn't Safari and Chromium use separate network layer, so they have different bugs there
11:40
<smaug____>
s/separate/different/
11:41
<smaug____>
bah, now my English is getting horrible
11:42
<zcorpan>
smaug____: must be the Perl
11:48
<annevk>
smaug____: yeah, Safari uses Mac OS X's network layer
11:48
<MikeSmith>
smaug____, jgraham : we can add support python on w3c-test.org if there's a real need
11:49
<annevk>
marcosc: even though <source media> "works" it doesn't actually dynamically adjust or anything
11:49
<annevk>
marcosc: it's hardly useful for anything
11:52
<marcosc>
annevk: yes, it's not "responsive"
11:52
<marcosc>
Why was it added?
11:53
marcosc
was actually quite surprised that it was there.
11:54
<odinho>
lol, tobie is expressing interest for almost anything on TPAC wiki. I wanted to do the same, but am currently restraining it a bit :P
11:55
<marcosc>
odinho: if you really want to sign up for the Web Marketing one, no one is stopping you :)
11:55
<odinho>
images are not supposed to be dynamically adjusted either.
11:55
<odinho>
marcosc: Too embarrasing. :S
11:55
<zcorpan>
put in a fake tag entry to see how many are interested
11:55
<marcosc>
heh
11:56
<odinho>
zcorpan: == TAG chitchat == People who have expressed interest: ...
11:57
<zcorpan>
or longdesc! gotta resolve longdesc!
11:57
<marcosc>
heh :)
11:57
<marcosc>
how about resolving longdesc with httpRange-14 ?
11:57
<annevk>
longdesc is back again?
11:57
<hsivonen>
IE9 is weird. If a JS or CSS file starts with a UTF-8 BOM and HTTP says it’s not UTF-8, IE9 skips the BOM and then decodes the file according to the HTTP-level charset.
11:59
<zcorpan>
annevk: does it ever leave?
11:59
<zcorpan>
longdesc stays for long
11:59
<jgraham>
You are saying it shoudl have been named longdiscuss?
12:00
<annevk>
hsivonen: o_O
12:00
<jgraham>
"a href pointing to a longer discussion of the image's contents"
12:00
<annevk>
hsivonen: I hope I'm not going to spec that
12:00
<marcosc>
heh
12:02
<annevk>
This responsive image thing is kinda similar; people all up in arms about a single attribute
12:02
<hsivonen>
annevk: I hope you are not
12:02
<hsivonen>
IE10 (Preview) behaves the same
12:05
<hsivonen>
also for HTML
12:06
<annevk>
I'm pretty sure that means they changed behavior
12:06
<hsivonen>
from 8 you mean?
12:07
<annevk>
Or maybe we did not check the HTTP override closely enough? Hmm
12:07
<hsivonen>
from 9 even
12:08
<hsivonen>
IE9 is different for HTML on one hand and JS and CSS on the other
12:09
<hsivonen>
writing well-researched email to www-style is so much slower than just changing the code...
12:43
<hsivonen>
finally got the email sent: http://lists.w3.org/Archives/Public/www-style/2012Oct/0516.html
13:18
<zcorpan>
MikeSmith: http://dvcs.w3.org/hg/webapps/rev/93b89bd30489 gives 500
13:20
<Ms2ger>
https://dvcs.w3.org/hg/webapps/rev/93b89bd30489 doesn't, fwiw
13:21
<zcorpan>
oh
14:23
Ms2ger
looks for someone from Opera
14:23
<Ms2ger>
jgraham?
14:23
jgraham
looks like someone from Opera
14:24
<Ms2ger>
jgraham, bz wants to add something to your microdata test: https://bugzilla.mozilla.org/attachment.cgi?id=673223&action=diff#a/dom/imptests/html/tests/submission/Opera/microdata/test_001.html_sec1
14:27
<jgraham>
Ms2ger: Sounds good to me
14:27
<Ms2ger>
Thanks
14:27
<jgraham>
I am not quite the right person to really review it, but I don't object to it at least
14:27
<jgraham>
Is the order well defined?
14:28
<Ms2ger>
I think I managed to convince myself the spec agrees with that order :)
14:28
<jgraham>
Ms2ger: Are you going to push that back to the W3C?
14:28
<Ms2ger>
Yes
14:29
<jgraham>
Awesome, thanks
14:29
<Ms2ger>
Np
15:00
<SimonSapin>
Is there a way to test the computed value (not used value) of a CSS property?
15:01
<Ms2ger>
jgraham, fwiw, the Mozilla people most likely to know about test servers hang out on irc.mozilla.org #ateam
15:02
<jgraham>
Ms2ger: Thanks
15:02
<Ms2ger>
Np
15:03
<jgraham>
I have written a slightly incoherent email, but am waiting to see if I can work out who is responsible for this stuff at Google and Apple
15:03
<jgraham>
Or however the infrastructure is set up
15:20
<annevk>
SimonSapin: getComputedStyle works often
15:20
<annevk>
SimonSapin: but not all the time
15:21
<annevk>
omg someone murdered my CSSOM work and replaced it with respec-style shit
15:21
<SimonSapin>
annevk: I want to test vw estc
15:21
<SimonSapin>
annevk: I want to test vw etc. in implementations
15:22
<SimonSapin>
apparently the computed value is supposed to resolve vw and be absolute
15:22
<annevk>
SimonSapin: see http://dev.w3.org/csswg/cssom/#resolved-value for which properties it returns the computed value
15:22
<SimonSapin>
but in paged media the viewport size is potentially different across pages on the same document
15:23
<annevk>
(or should return, anyway)
15:42
<dglazkov>
good morning, Whatwg!
16:05
<gsnedders>
We have multiple specs defining the URL object? Yay!
16:09
<annevk>
gsnedders: we do?
16:09
<gsnedders>
File API.
16:10
<gsnedders>
Supplemental interface, but confused me when I was looking for createObjectURL in the URL spec.
16:12
<annevk>
oh multiple like that
16:18
<abarth>
jgraham: we're around, just in different time zones
16:22
<odinho>
abarth: Hmm. If a tree falls in the forest, but noone hears ... etc. :P
16:58
<annevk>
ooh, jsbell, didn't realize that's how ArrayBufferView worked
16:59
<annevk>
I wish the Typed Array spec had a shorthand so could just talk about the bytes from the ArrayBufferView
17:00
<jsbell>
heh. The reason I got mired in this in the first place was writing an JS library to encode/decode to a binary format. This was before Typed Arrays were supported anywhere so I started off writing a TA shim. So... intimately aware of the details. :)
17:00
<annevk>
heh, man of many shims
17:30
<JonathanNeal>
What are we shimming now? Forcing CSS to recognize unsupported entries like old IE did?
17:30
<TabAtkins>
annevk: It's your fault for abandoning us!
17:30
<TabAtkins>
SimonSapin: getComputedStyle should work for all non-2.1 properties, and generally all 2.1 properties not directly involved in layout.
17:33
<TabAtkins>
zcorpan: Yeah, I know, but I was pissed, shrug. Annoys me when people forget just how large the author community is, and thus take "I think this is easy to misuse" as a personal attack against themselves.
17:33
<TabAtkins>
And/or forget how many hostile authors there are.
19:11
<Hixie>
Glenn Adams doesn't hang out on IRC right?
19:12
<TabAtkins>
I've seen him on W3C server, under glenn.
19:12
<TabAtkins>
But he's not there now.
19:14
<Hixie>
sigh
19:14
<Hixie>
why did anne have to give up on CSSOM
19:14
<TabAtkins>
I know. I'd take it over, but I'm too busy with other things. :/
19:14
<Hixie>
it's already bit-rotting, losing MUST statements and stuff
19:16
<Ms2ger>
"glazou", I believe
19:22
<astearns>
am I reading correctly that I cannot set up a MutationObserver to observe changes in CSS properties?
19:22
<TabAtkins>
Correct.
19:22
<TabAtkins>
MutationObservers observe DOM mutations.
19:22
<TabAtkins>
Though you can observe changes in 'style' attributes.
19:25
<astearns>
is there a principle behind this restriction, or is it just future work to define a CSSMutationObserver?
19:27
<TabAtkins>
DOM observers are easier, in general, than a generic JS object observer.
19:27
<TabAtkins>
However, the latter is planned for the future.
19:29
<astearns>
OK, thanks
20:01
Ms2ger
whacks dglazkov
20:05
<Hixie>
now what
20:06
<dglazkov>
yay
20:07
<Ms2ger>
dglazkov, https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#shadow-root-object
20:07
<Ms2ger>
You need to add ? for nullable types
20:07
<Ms2ger>
and get rid of 'in' and 'raises'
20:08
<dglazkov>
Ms2ger: sure thing, thanks! can you file a bug so I don't forget? there's a nice line at the right top corner
20:08
<dglazkov>
line->link
20:18
<dglazkov>
<3
20:25
<dglazkov>
Ms2ger: are you going to be at the TPAC in Lyon?
20:25
<Ms2ger>
Perhaps
20:26
<astearns>
we should all dress up as Ms2ger on Halloween
20:28
<jgraham>
You mean we each dress up as a rack server and then lie on top of each other?
20:28
<dglazkov>
Ms2ger: well -- I am not going :P
20:29
<Ms2ger>
jgraham, kinky
20:34
<jgraham>
dglazkov: So who will be filling your role as the supernaturally cheery one?
20:57
<dglazkov>
jgraham: slightlyoff, of course!
21:01
<TabAtkins>
That... seems like a perversion of nature.
21:30
<smaug____>
what... Ms2ger said "perhaps"
21:30
<smaug____>
will we see him/her/it
21:32
<jgraham>
I think perhaps is a mysterious-sounding synonym for "no"
21:32
<jgraham>
At least in this case
21:33
<Hixie>
i might be at tpac
21:33
<Hixie>
if there was a wormhole that suddenly opened below my desk and dropped by there against my will
21:33
<Hixie>
:-P
21:36
jgraham
thinks there are a variety of substantially more likely scenarios that would lead to Hixie being at TPAC
21:37
<Philip`>
Declare that TPAC will occur wherever Hixie is, so that he will inevitably be attending it
21:38
<jgraham>
For example
21:44
<Hixie>
now you're just scaring me
21:44
<Hixie>
it's not halloween yet!
21:49
<hober>
halloween falls on the plenary day this year
21:49
<hober>
clearly we should all go as httpRange-14
22:08
<zewt>
Hixie: eh fyi, https://www.w3.org/Bugs/Public/show_bug.cgi?id=18610 doesn't feel like you read the text at all
22:14
<Hixie>
how so?
22:14
<Hixie>
the comment says "i don't want to wait for gc". my point is, just wait for gc.
22:18
<zewt>
if that was good enough, then we wouldn't need Blob.close, either
22:19
<zewt>
anyway, answering "i want to be able to do something" with "sure, just don't do it" doesn't feel like much of an answer :)
22:19
<Hixie>
I don't think we do, but that's not my responsibility
22:20
<Hixie>
if you want detailed answers, mail the list. :-) but i don't really see what answer i would give that's more detailed, it doesn't really give a use case, so "don't do that" is pretty much the only valid answer
23:06
<Hixie>
ok. 48 bugs ahead of schedule, 49 e-mails ahead of schedule. Just right for the weekend.