00:29
<dglazkov>
TabAtkins: are there things like that in JS?
00:29
<TabAtkins>
Not in real JS, no.
00:30
<TabAtkins>
It's something magical that only pops out of IDL.
00:30
<TabAtkins>
(And which imo should be avoided as much as possible in favor of constructible things.)
00:40
<Wilto>
oh what the crap is this
00:40
<Wilto>
http://axis.yahoo.com/
00:40
<Wilto>
—Hah! Wrong window. Hi.
00:40
<Wilto>
Question stands.
04:30
<dglazkov>
TabAtkins: IDL sucks then. It must be terminated.
05:52
<annevk>
abarth: the allowseamless stuff should probably include some advice about how to prevent being embedded by the wrong third party
06:51
<[tm]>
crockford left Yahoo?
06:53
<[tm]>
ah, paypal
06:53
<tantek>
yeah - http://techcrunch.com/2012/05/13/paypal-gets-its-own-share-of-the-yahoo-diaspora-hires-java-icon-douglas-crockford/
06:54
<tantek>
ironic since the recently deposed Yahoo CEO came from paypal
06:54
<tantek>
the one that lied on his resume
06:54
<tantek>
about having a CS degree
06:56
<tantek>
http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2012/05/13/CMKC1OHF1B.DTL - scroll down to "Resume irregularity"
06:56
<tantek>
love this part: "Thompson sent employees a memo apologizing for the impact that the disclosure of his true credentials had on Yahoo, without apologizing for the error itself."
06:57
<tantek>
apologizing for how it looked, rather than apologizing for lying.
07:06
<annevk>
o_O
08:25
<annevk>
ideas for http://wiki.whatwg.org/wiki/Howto_spec
08:25
<annevk>
merge Content and Patterns
08:26
<annevk>
add more patterns: callbacks, class=domintro, cancelable events
08:27
<jgraham>
It is very about:blank. You are likely to be eaten by a load.
08:29
<annevk>
jgraham: I don't get it :(
08:30
<jgraham>
annevk: Oh don't mind me, I'm just experiencing the joy of about:blank today
08:30
<jgraham>
My comment was apropos nothing else in particular
08:32
<jgraham>
(I think I was thinking of "blank" as an alternative to "dark")
08:44
<annevk>
man
08:44
<annevk>
about:blank sure causes a lot of pain
09:01
<jgraham>
with that in mind
09:01
<jgraham>
hsivonen: yt?
09:08
<annevk>
so WebKit's location.origin is still not defined...
09:08
<annevk>
meh
09:09
<othermaciej>
was it ever officially proposed?
09:10
<othermaciej>
if not, I can complain to the person who added it to the code
09:11
<annevk>
pretty sure abarth proposed it
09:12
<annevk>
the way to clean this up is probably by defining the URL specification properly and then have Location and HTMLAnchorElement use it
09:12
<annevk>
I think [tm] already did some work in that direction
09:12
<othermaciej>
is there anything about it currently that would prevent it from being used as a supplemental interface for Location and HTMLAnchorElement?
09:13
<hsivonen>
jgraham: ?
09:13
<annevk>
othermaciej: yeah, the attributes are defined directly on the URL interface
09:14
<annevk>
othermaciej: we should probably have a [NoInterfaceObject] interface URLAttributes thingie
09:15
<othermaciej>
annevk: would that make a difference to the ability of Location to reuse it? (I might not sufficiently understand the Web IDL issues)
09:16
<jgraham>
hsivonen: So, I am looking at about:blank. Please feel sorry for me :) Also gecko seems to have some odd behaviour if you create an iframe, insert it, and then set the src
09:16
<jgraham>
Let me put a TC somewhere
09:16
<othermaciej>
in fact I am still super confused about the difference between sequence<Foo> and Foo[] and why both exist
09:16
<annevk>
othermaciej: interface URL has a bunch of other stuff (such as a constructor) that would not make sense elsewhere
09:17
<annevk>
actually, maybe it's just that constructor...
09:17
<annevk>
see http://dvcs.w3.org/hg/url/raw-file/tip/Overview.html#url
09:17
<hsivonen>
jgraham: Please don't try to make Opera behave like current Gecko behaves
09:17
<hsivonen>
jgraham: unfortunately, I've been blocked from making progress on changing Gecko yet again
09:18
<hsivonen>
jgraham: but the plan still is to change it
09:18
<jgraham>
hsivonen: I'm not trying to :)
09:18
<jgraham>
I'm trying to understand what behaviour is actually web compatible
09:18
<hsivonen>
webben: The deps of http://bugzilla.validator.nu/show_bug.cgi?id=923 now track Maven stuff
09:19
<jgraham>
(the spec is not)
09:19
<hsivonen>
webben: I have almost no clue about Maven and depend on people who want Maven support to contribute pom.xml patches
09:19
<jgraham>
I am told that it is relatively easy to change Opera to make it Webkit-like
09:19
<hsivonen>
jgraham: firing onload synchronously?
09:19
<hsivonen>
events that fire sync with parse are evil
09:20
<hsivonen>
I still want to make the events for about:blank to fire async
09:20
<jgraham>
Why?
09:20
<hsivonen>
jgraham: they can run scripts, so they require putting Gecko in a state where it's safe to run scripts
09:20
<hsivonen>
which add both code and perf overhead
09:21
<hsivonen>
also interesting document.write() call opportunities
09:21
<jgraham>
http://hoppipolla.co.uk/tests/about_blank/002.html
09:22
<jgraham>
In Opera that currently claims to be 2 async events, but apparently it is sure that the events will run before any other script
09:23
<jgraham>
In webkit it is one sync/one async
09:23
<jgraham>
In gecko there is only one event
09:28
<othermaciej>
annevk: I just read the spec and complained about the parameter stuff
09:28
<othermaciej>
annevk: anyway - are constructors inherited? I think they are not, so it doesn't matter
09:28
<othermaciej>
annevk: only issue would be whether prototype-hacking the URL interface object would affect HTMLAnchorElement
09:31
<annevk>
othermaciej: what you want is implementing them and defining them in a single place, but the effect should be that they appear to be on HTMLAnchorElement, Location, and URL independently I think
09:31
<annevk>
I don't really care how we go about that, I guess heycam|away can figure that out :)
09:32
<jgraham>
hsivonen: So, what behaviour are you proposing, and how sure are you that it's web compatible?
09:32
<annevk>
it might be that "implements" does exactly that, but I don't know what happens to Constructors
09:32
<Ms2ger>
That's 'implements', AIUI
09:34
<othermaciej>
annevk: I think it might just work for Location and HTMLAnchorElement to both inherit from URL
09:34
<Ms2ger>
No
09:34
<Ms2ger>
There is no multiple inheritance in IDL
09:35
<othermaciej>
ok, whatever the alternative to multiple inheritance is to add a mixin (is there such a thing?)
09:35
<Ms2ger>
implements copies "constants, attributes or operations"
09:35
<Ms2ger>
So, implements should be fine
09:35
<othermaciej>
Location could just inherit, since it has no base class
09:35
<othermaciej>
I think HTMLAnchorElement could use "implements"
09:36
<Ms2ger>
It would be silly to make them different, IMO
09:37
<othermaciej>
Location could use "implements" too despite not having any other base class
09:37
<othermaciej>
I do not know if there is any other comparable case in the HTML DOM
09:37
<othermaciej>
where an element and a non-element share an interface in common
09:39
<annevk>
HTMLElement and Document for a few members
09:39
<annevk>
but they're just duplicates
09:39
<annevk>
duplicated*
09:40
<Stevef>
othermaciej: hi, what's the status on the <hgroup> issue?
09:40
<othermaciej>
Stevef: I do not know offhand
09:40
<othermaciej>
do you remember the issue number?
09:41
<othermaciej>
there were draft reviews of all the proposals in progress, I do not recall if they have been posted yet
09:41
<othermaciej>
if not, that is the next step
09:42
<Stevef>
othermaciej: http://www.w3.org/html/wg/tracker/issues/164
09:43
<Stevef>
othermaciej: haven't been posted yet, paulc soad he was going to post them about 2 weeks ago
09:43
<othermaciej>
ok, I'll check in with him
09:43
<Stevef>
othermaciej: thanks
09:45
<Stevef>
can anybody tell me what ted oconnors nick is?
09:45
<Ms2ger>
hober,
09:46
<Stevef>
Ms2ger:thanks
09:46
<Ms2ger>
Np
09:47
<Stevef>
hober: any response to this http://lists.w3.org/Archives/Public/public-html/2012May/0008.html ?
09:58
<webben>
hsivonen: I'm looking into the Maven issue btw. How do you build and test htmlparser yourself? I want to verify my pom.xml doesn't break your workflow?
11:06
<hsivonen>
webben: I use a plain Eclipse project setup with its intregated incremental builder
11:06
<hsivonen>
webben: pom.xml isn't part of my workflow at all except for making release bundles for the Maven Central Repository
11:07
<hsivonen>
webben: hence, I don't grok pom.xml
11:09
<zcorpan>
http://forums.whatwg.org/bb3/viewtopic.php?f=10&t=5000#p7899 anyone have suggestions about what to do about this?
11:12
<ashemedai>
MathML in Opera Next gets better and better, I have to say
11:15
<jgraham>
ashemedai: Interesting. Examples of things that improved?
11:18
<ashemedai>
jgraham: http://www.in-nomine.org/~asmodai/3d.html
11:19
<ashemedai>
jgraham: scroll to alpha blending
11:19
<ashemedai>
The entire layout of that part is just tight now, as it should
11:19
<ashemedai>
of course, the other ones still can use some work :)
11:20
<Ms2ger>
Heh, that looks bad on my opera-next
11:20
<jgraham>
Yeah, maybe I am missing some fonts
11:20
<jgraham>
But I see [r] instead of [r,g,b]
11:20
<Ms2ger>
^
11:20
<Ms2ger>
Fortunately, Gecko is there when you need a good MathML implementation ;)
11:22
<ashemedai>
oh wait
11:22
<ashemedai>
Good point jgraham
11:22
<ashemedai>
Totally missed that
11:25
<ashemedai>
Ms2ger: And you are right, just still have this pipedream of seeing Chrome and Opera implement more of MathML
11:26
<zcorpan>
publish more mathml content so it becomes a sitecompat issue :-)
11:26
<Ms2ger>
Acid4 ;)
11:26
<jgraham>
Convince Google to make google.com depend on MathML :p
11:26
<annevk>
ashemedai: I'm afraid that as long as we use CSS and CSS cannot describe all of MathML displaying Math in Opera will be bad :(
11:27
<jgraham>
Ms2ger: Well given acid 3 that would probably give you stubs for MathML
11:28
<Ms2ger>
Acid4: The entire MathML test suite? :)
11:28
<ashemedai>
mmm, opera next updater gives me a cannot validate file when it tries to grab the update file, at least manual update worked
11:28
<zcorpan>
each pixel is a test
11:28
<ashemedai>
annevk: Yea, but I'm happy with the intermediate work already
11:28
<Ms2ger>
zcorpan, ... and they animate ;)
11:28
<ashemedai>
annevk: I should just use Mathjax in the meantime
11:29
<annevk>
ashemedai: nah, please publish MathML
11:30
<Ms2ger>
Does annevankesteren.nl have any?
11:30
<annevk>
ashemedai: and write about the problems you encounter
11:31
<ashemedai>
annevk: I'll be adding more formulae to that page in the weekend.
11:31
<annevk>
Ms2ger: I suck at math
11:31
<ashemedai>
annevk: as in blog?
11:31
<annevk>
ashemedai: for instance
11:31
<ashemedai>
Can do that :)
11:31
<annevk>
you can also create a wiki page on the WHATWG wiki
11:31
<annevk>
we try to track/document shortcomings of all web technology
11:32
<annevk>
so whenever someone gets a chance to improve it, they know where to start
11:32
<Ms2ger>
annevk, I'm sorry to hear that :)
11:32
<annevk>
Ms2ger: the people who wanted me to define matrix-aware layout APIs were too
11:33
<Ms2ger>
Meh, that's not real math
11:33
<ashemedai>
annevk: Ah, sure, I can do the MathML page on Whatwg wiki
11:34
<ashemedai>
So who do I bother for an account? :P
11:34
<annevk>
ashemedai: you message me an email address
11:34
<annevk>
ashemedai: oh and give me a desired username
11:37
<ashemedai>
Thanks!
11:39
<ashemedai>
annevk: Is there a specific subsection where status/shortcomings are discussed?
11:39
<ashemedai>
Where I hook a new page under
11:39
<annevk>
[[Category:Proposals]] maybe
11:39
<annevk>
hmm
11:40
<Ms2ger>
[[Category:ToBeAssimilated]]
11:40
<annevk>
oh or maybe http://wiki.whatwg.org/wiki/Category:Spec_coordination
11:40
<ashemedai>
Ms2ger: :P
11:40
<annevk>
Spec coordination is probably good
11:42
<ashemedai>
annevk: ok, done. Got the page up, linked under Spec coordination
11:43
<annevk>
"Spec coordination is what keeps #whatwg busy at night."
11:43
<annevk>
heh
11:43
<annevk>
oh I wrote that
11:43
<ashemedai>
lol
11:44
<jgraham>
Well at least you can laugh at yourself
11:45
<hsivonen>
ashemedai: convince Wikipedia to go all-in with MathML without MathJax fallbacks
11:45
<annevk>
yeah Wikipedia really ought to switch
11:46
<ashemedai>
hsivonen: I can try asking some of my Wikipedia-Unicode contacts about that
11:46
<ashemedai>
Think that would be incentive for the browser makers to step up the game?
11:47
<hsivonen>
ashemedai: If Wikipedia went all-in with Presentation MathML, yeah.
11:47
<hsivonen>
ashemedai: (if they did Content MathML, they'd be too far out there)
11:48
<annevk>
is it even agreed we should keep Content MathML?
11:48
<hsivonen>
annevk: no
11:48
<hsivonen>
annevk: we decided to make Gecko not corrupt Content MathML alternatives in clipboard operations, though
11:49
<annevk>
mkay
11:49
<hsivonen>
annevk: so we're trying to be nice about it
11:49
<annevk>
I guess the MathML wiki page should at some point define the subset we're interested in
11:49
<hsivonen>
annevk: but no plans to really support it, AFAIK
11:49
<annevk>
if the Math WG is not going to do that
11:50
<hsivonen>
annevk: are there parts of Presentation MathML that we're *not* interested in?
11:50
<hsivonen>
annevk: I thought the subset was "Presentation MathML"
11:50
<annevk>
what is <annotation-xml> part of?
11:51
<zcorpan>
lala land?
11:51
<gsnedders>
We've pretty much said we're only really interested in http://www.w3.org/TR/mathml-for-css/
11:51
<hsivonen>
annevk: it's an integration point on the edge of Presentation MathML
11:51
<jgraham>
hsivonen: So re: about:blank it seems like we will go for something WebKit-like unless we are persuaded otherwise (e.g. by a gecko implementation that is web compatible and doesn't have synchronous events or task queue mangling)
11:51
<hsivonen>
annevk: you walk off the cliff when you walk into that subtree
11:51
<jgraham>
Or by finding out that "webkit like" is actually hard to implement in detail
11:51
<annevk>
hsivonen: right so maybe that should be "disallowed"
11:51
<gsnedders>
i.e., only really interested in the subset of MathML that can be described by CSS.
11:51
<hsivonen>
jgraham: :-(
11:51
<gsnedders>
Of course as CSS grows that may expand.
11:52
<hsivonen>
annevk: depends on how you view use cases for alternative semantic content for copying and pasting into symbolic algebra software
11:52
<jgraham>
hsivonen: Yeah, sorry :( But it is hard to argue against something that I'm told is - at a high level - simple in our implementation and has known web compat properties
11:52
<hsivonen>
jgraham: I understand
11:53
<hsivonen>
jgraham: I fail for what I want being continuously vaporware
12:24
<ashemedai>
So feel free to let me know what you think such a page on MathML needs - http://wiki.whatwg.org/wiki/MathML
12:24
<ashemedai>
I'll add some implementation notes/details as soon as I get home
12:25
<annevk>
ashemedai: feel free to phrase it more direct
12:26
<ashemedai>
annevk: Phrase what more direct?
12:26
<annevk>
ashemedai: like "Content MathML should not be used and is not going to be implemented by browsers."
12:27
<annevk>
though maybe mention the copy-and-paste exception hsivonen was talking about
12:27
<ashemedai>
Ah
12:28
<annevk>
if we communicate our intentions clearly, there's less room for surprise
12:28
<ashemedai>
Gotcha
12:28
<annevk>
(and more room for debate, people might disagree with our stance)
13:05
annevk
is making modest progress with http://wiki.whatwg.org/wiki/Howto_spec
13:06
<annevk>
defined a bunch of event patterns
13:07
<annevk>
and callbacks
13:11
<Ms2ger>
Anyone have a link for the previous readyState string/short discussion?
13:19
<annevk>
you're lazy
13:19
<annevk>
took me a minute: http://lists.w3.org/Archives/Public/public-script-coord/2012JanMar/thread.html#msg166
13:20
<annevk>
but it's really my fault for responding here :)
13:32
<matjas>
http://lachy.id.au/dev/markup/tests/html5/charref/ lists 1449 named character references, while http://whatwg.org/html/named-character-references.html lists 2232
13:32
<matjas>
would there be any interest in an updated test case for this?
13:32
<matjas>
i was thinking of making one that automates the testing through JS
13:33
<Philip`>
matjas: That test case has 1449ish lines, but lists multiple named character references on a single line
13:33
<Philip`>
<tr><td>&#x00026;<td>&amp; &amp &AMP;<td>U+00026 AMPERSAND
13:33
<Philip`>
etc
13:33
<matjas>
right
13:34
<Philip`>
which might make up some of the difference
13:34
<Philip`>
(or all of it)
13:35
<matjas>
not all of it; there are only 3581 occurences of & in the source
13:35
<matjas>
3581 / 2 = 1790,5 < 2232
13:36
<matjas>
anyhow, just wanted to know if it hasn’t been done already, or if lachlan had an update planned
13:37
<Philip`>
Hmm, looks like it excludes at least the multi-codepoint references (&acE; etc)
13:38
<matjas>
zcorpan: without checking the spec i’d guess A
13:41
<zcorpan>
matjas: http://i.imgur.com/Emi0l.gif
13:41
<Philip`>
There's http://code.google.com/p/html5lib/source/browse/testdata/tokenizer/namedEntities.test which would hopefully be up to date, but I don't know whether there's a way to run those tests inside a browser (rather than a standalone parser)
13:42
<Ms2ger>
C
13:42
<matjas>
Philip`: okay, I’ll just give it a whirl then — can’t hurt, right?
13:42
<zcorpan>
Ms2ger: http://i.imgur.com/Emi0l.gif
13:42
<Ms2ger>
Nice
13:43
<Philip`>
matjas: More tests never hurt :-)
13:45
<jgraham>
http://test.w3.org/html/tests/submission/Opera/html5lib/tests/test_tokenizer_namedEntities.html perhaps?
13:46
<matjas>
jgraham: woah @ source
13:47
<jgraham>
You can't decode uri components in your head?
13:47
<jgraham>
:)
13:47
<odinho>
Ms2ger: Seems test-runner doesn't run in IE10? I just wanted to check something, but seems it never really starts :-) Is it known, or an authoring fault from my side on making the testrunner.htm file?
13:48
<jgraham>
matjas: It was supposed to be a very general purpose way of converting the html5lib tests that didn't optimise for readability
13:49
<odinho>
Ms2ger: fsck, it was (my :P) authoring error as I had a hunch it might be.
13:51
<Ms2ger>
odinho, does it work in IE10, then? I never tried :)
13:52
<odinho>
Ms2ger: Well, I'll see shortly, I need to stop reading IRC backlog first :P I'm easily distracted it seems.
13:53
<odinho>
Ms2ger: Aaaand, it works! :-)
13:53
<Ms2ger>
\o/
14:12
<jgraham>
It would be nice if Bryan Sullivan's name wasn't always written in loudcase
14:14
<odinho>
Hehe.
14:20
<zcorpan>
nobody guessed the right answer for this quiz (other than by eliminating the wrong answers), i think that's a first
14:38
<matjas>
Hixie: why does whatwg.org/html/named-character-references.html#entity-DotDot have \u25CC\u20DC in the glyph cell rather than just \u20DC?
14:41
<zcorpan>
file a bug
14:42
<tkadlec>
e
14:42
<Philip`>
matjas: I expect it's a placeholder so that the combining character is sensibly visible
14:42
<matjas>
zcorpan: it doesn’t seem like a bug/typo, as other cells have it too… i just don’t see why — it doesn’t make it clearer
14:43
<matjas>
Philip`: i think the extra circle just makes it harder to see the combining char
14:43
<matjas>
guess it’s just me then
14:43
<Philip`>
If you didn't have any character in front of it then it'd appear too far to the left, which would also look unclear
14:44
<Philip`>
http://www.fileformat.info/info/unicode/char/25cc/index.htm has a comment relating to combining character indications
14:45
<Philip`>
(I presume that comment is originally from the Unicode standard itself)
15:12
<matjas>
other mismatches between code points + glyphs on that page: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17170#c1
15:16
<matjas>
^ writing those tests pays off already :)
15:47
<matjas>
test results: WebKit currently fails on 1 named character reference (&AElig doesn’t match Æ), the WebKit in latest stable Safari has 94 errors, Presto and Gecko pass all tests
15:49
<jgraham>
matjas: Nice, but you should test one of the many parts of the spec that *doesn't* already have tests. Then you should submit the tests to the W3C :)
15:50
<Ms2ger>
matjas, or review the submitted tests, if you like that :)
15:51
<jgraham>
s/that/torture/
15:52
<Ms2ger>
shh
15:52
<jgraham>
Uh right
15:52
<jgraham>
Testcase review is really fun!
15:52
<jgraham>
You should do it!
15:53
<Ms2ger>
Hah
15:53
<matjas>
thanks, i’d rather write my own :')
15:53
<jgraham>
Problem is, if people start reviewing TCs, they will quit before they get to writing them
15:53
<jgraham>
And I would rather have people writing TCs
15:54
<jgraham>
Even though that means more reviewing...
16:00
<odinho>
Funny, Firefox does 1 test better than IE10 in MS' idb testsuite. But they both fail the same number (the diff is not-run).
16:00
<odinho>
But both more or less lies at 84% pass.
16:01
odinho
wonders when WebKit will start updating their idb implementation...
16:01
<annevk>
matjas: the &lang; thing is a problem in the publishing pipeline
16:01
<annevk>
matjas: there's a bug on it somewhere, we haven't quite located the source
16:02
<matjas>
annevk: hmm, can’t you just use numeric character references instead of the raw characters, or are those unreliable as well?
16:02
<annevk>
matjas: you mean instead of named entities?
16:02
<matjas>
no, i mean for the “glyph” cell
16:03
<annevk>
matjas: I think numeric character references are used, but the publishing pipeline fucks it up
16:03
<matjas>
annevk: oh, i see
16:04
<dglazkov>
good morning, WhatwG!
16:05
<odinho>
good evening dglazkov :-)
16:06
<annevk>
dglazkov: still trouble spelling names I see :p
16:06
<dglazkov>
annevk: I am mixing it up.
16:07
<tantek>
good morning dglazkov
16:08
tantek
is debating whether to join the HTMLWG telcon this morning.
16:08
<annevk>
dglazkov: GoOd
16:08
<tantek>
perhaps I should take a straw poll
16:08
<annevk>
tantek: lol
16:08
<dglazkov>
tantek: yes, but only if you do it ironically
16:08
<annevk>
tantek: I can tell you how it goes: http://annevankesteren.nl/2010/12/html-wg-teleconference
16:09
<annevk>
tantek: maybe you can write down your experience as well so we can compare notes and see how things have progressed
16:09
<tantek>
ok, I leave it to #whatwg - please express +1/-1/0
16:09
<TabAtkins>
-1
16:09
<odinho>
+1 (plus notes)
16:09
<annevk>
+1 if you write it down
16:09
<annevk>
otherwise waste of time
16:21
<tantek>
annevk - your post is similar to most of my past experiences on the telcon
16:22
<tantek>
however, when I've had an issue (as in an Issue in tracker) to discuss, and have specifically brought up questions, typically I've had very productive discussions with the chairs.
16:23
<tantek>
so I think the telcons are mostly what you make of them. if just lurking, it's perhaps not that useful. if you have specific business to raise/discuss with the chairs, it can be useful. and anyone can do that during the "any other business" part of the telcon.
16:26
<annevk>
not sure why you'd dial in for that, but then I'm not sure why I ever dialed into teleconferences anyway
16:28
<tantek>
annevk - mostly I've dialed in to help move along the various <time> and <data> element change proposals that I made to officially make the changes happen that I discussed/debated/designed with Hixie (and somewhat in this channel) ages ago - after we got rough consensus at the TPAC HTMLWG f2f last year.
16:29
<annevk>
the <time> stuff was handled in such a fucked up way
16:29
<annevk>
W3C HTML was not updated for months
16:33
<Ms2ger>
Mm, we support rest parameters now
16:34
<annevk>
Ms2ger: meaning?
16:34
<tantek>
annevk - W3C HTML5 still lacks <data> :(
16:34
<Ms2ger>
function foo(...rest) {}
16:36
<othermaciej>
tantek: it was decided to restore it but it probably won't happen now til there are stable draft editors in place
16:38
<annevk>
tantek: not the only thing http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#how-do-the-whatwg-and-w3c-specifications-differ?
16:38
<annevk>
Ms2ger: is that the automatic array extraction?
16:39
<annevk>
Ms2ger: maybe it's time we update DOMTokenList and friends then
16:39
<Ms2ger>
Wfm
16:41
<annevk>
maybe add a note to the bug?
16:41
<annevk>
I'm gonna play with Howto spec a while longer I think
16:42
<annevk>
and then maybe review a bunch of API specs and point Howto spec out
16:43
<tantek>
othermaciej - is there a list somewhere of such pending edits?
16:44
<tantek>
(where a decision was made to make an edit, but the edit itself has not been made)
16:44
<othermaciej>
tantek: I think most pending decisions have an open bug with WGDecision keyword, but this case may be an exception since it was a CFC not directly related to a bug
16:46
tantek
is having some trouble following HTMLWG process intricacies.
16:54
<TabAtkins>
I'd be glad to see Content MathML dropped, since it contains the only two tagname conflicts in the language. Presentation MathML was careful (or lucky?) not to collide with SVG or HTML in any way.
16:55
<Ms2ger>
Careful
16:55
<TabAtkins>
Good to know.
17:03
<tantek>
interesting, an actual IETF draft to define rel="profile" - http://tools.ietf.org/html/draft-wilde-profile-link-01
17:24
<dglazkov>
in custom elements spec, I am very tempted to be just describe how things happen from JS perspective (i.e. prototype chain, objects in it, etc.). However, WebIDL/DOM4 and most other specs tend to specify things in terms of interfaces and generic inheritance concepts. Should do the former and not worry about consistency with existing specs, or should I do the latter and try to fit the concept of cu
17:24
<dglazkov>
stomizable DOM interfaces into the WebIDL world?
17:24
<Ms2ger>
Sounds like you're doing something wrong
17:25
<dglazkov>
Ms2ger: yes, but what? :)
17:25
<Ms2ger>
Well, I don't know what you're trying to accomplish
17:27
<dglazkov>
trying to capture http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html#custom-element-section as a spec.
17:28
<dglazkov>
specifically, describing the process of building a custom DOM element with a prototype chain, which includes a DOM object and an arbitrary JS object.
17:29
<Ms2ger>
I don't think I want to lat you do that, dave
17:29
<dglazkov>
Ms2ger: it's too late for that, R2D2
17:30
<dglazkov>
actually, http://www.w3.org/TR/WebIDL/#dfn-interface I think is workable
17:32
<dglazkov>
it's just such a weird transpiler operation, having to speak in WebIDL when really everyone knows it's JS.
17:32
<dglazkov>
can we just rewrite all specs to be in JS? :)
17:33
<Ms2ger>
It isn't
17:33
<Ms2ger>
It's C++
17:40
<dglazkov>
Ms2ger: that's just an implementation detail. C++ tries darn well to pretend it's not there. And Microsoft peeps are leading the charge to make it even less visible.
17:41
<dglazkov>
in IE10 that is
17:52
<annevk>
dglazkov: is there agreement that we want to do such a thing?
17:56
<annevk>
Ms2ger: stumbled upon http://lists.w3.org/Archives/Public/spec-prod/2012AprJun/0075.html
17:57
<Ms2ger>
Heh
18:00
<scott_gonzalez>
smaug____ (or any other Mozilla devs): Do you know why scrollable elements are in the tab order in Firefox but no other browser?
18:00
<scott_gonzalez>
Is it an accessibility concern?
18:00
<smaug____>
yes
18:01
<smaug____>
scott_gonzalez: https://bugzilla.mozilla.org/show_bug.cgi?id=755766#c11
18:02
<scott_gonzalez>
Target audience of sighted keyboard users?
18:02
<smaug____>
(that bug is invalid)
18:47
<rniwa>
AryehGregor: yt?
19:31
<gsnedders>
"Ecma International now hosts a normative HTML copy of Ecma-262, Edition 5.1 The ECMAScript Language Specification."
19:33
<Ms2ger>
It's not actually normative
19:36
cbright6062
tries to read over the recent posts here but gets a headache and decides to not bother.
19:40
<cbright6062>
I'd also love to see the day where things didn't seem to get so overcomplicated with everything. Lol.
22:51
<alecflett>
hey - is anyone around who can clarify something for me in the DOM4 spec?
22:52
<alecflett>
specifically what looks like a spec bug in the section about DOMException
22:55
<gsnedders>
Just ask.
22:56
<alecflett>
well the problem I have is that there's no specifically called-out field for the string-based exception type in DOMException
22:57
<alecflett>
so if a caller wants to check the exception type using the newer string-based mechanism, there's no way to do it
22:57
<alecflett>
i.e. rather than if (ex.code == DOMException.IndexSizeError) ….,
22:57
<alecflett>
there's no equivalent for the string "IndexSizeError"
22:57
<alecflett>
ie.
22:57
<alecflett>
if (ex.<???> == "IndexSizeError") {…}
22:58
<alecflett>
ex.name? (consistent with DOMError) or ex.type (alluded to in the spec but not called out in the IDL)
23:02
<heycam>
alecflett, it's .name
23:02
<heycam>
alecflett, it's in Web IDL that it's defined that exception objects get a name property
23:03
<alecflett>
ahh.. .thanks for the clarification
23:03
<alecflett>
might be nice to have some non-normative reference to that somewhere in the DOM4 spec as I spent a good deal of time looking for it!