04:43
<GPHemsley>
What exactly does this mean? "Table column 13 established by element col has no cells beginning in it."
04:59
<MikeSmith>
GPHemsley: it means the table is malformed because the col element makes the table algorithm expect there to be a cell in a certain place but the later table markup does not actually produce the expected cell
05:00
<GPHemsley>
the only thing I can think of is that there is a colspan="2" but never two column separately
05:07
<MikeSmith>
GPHemsley: if you have a test case I'd be glad to take a look also
05:08
<MikeSmith>
it could actually be a bug in the v.nu table-integrity-checking code
05:11
<GPHemsley>
MikeSmith: This is what I'm working on ATM: http://gphemsley.org/linguistics/en/trace_table.php
05:11
<GPHemsley>
and it's broken as it currently stands
05:11
<GPHemsley>
(=invalid)
05:13
<MikeSmith>
weird
05:13
<MikeSmith>
it has 13 columns, right?
05:13
<MikeSmith>
unless I'm counting wrong
05:13
<GPHemsley>
right now, all of the cells in the beta/V(PASS) column are colspan="2"
05:13
<MikeSmith>
or unless it counts the first as zer
05:14
<MikeSmith>
ok
05:14
<GPHemsley>
and the 13th column would be the second column in that span
05:14
<GPHemsley>
AFAICT
05:14
<GPHemsley>
which, indeed, does not currently exist anywhere
05:14
<MikeSmith>
ah, yeah, I see what you're saying
05:15
<MikeSmith>
so you have no col element at all, I see
05:15
<MikeSmith>
oh, sorry
05:15
<MikeSmith>
I see now
05:15
<MikeSmith>
colgroup/col
05:15
<GPHemsley>
yeah
05:15
<GPHemsley>
it's mention in a <col> and in @colspan, but no <td> or <th>
05:16
<GPHemsley>
IOW, it's only mentioned implicitly, not explicitly
05:25
<MikeSmith>
what happens if you just delete the colgroups and cols?
05:26
<MikeSmith>
it seems like it doesn't have any effect on the rendering at least
05:28
<GPHemsley>
hmm... incidentally, it considers it an error if you don't have the same amount of cols/colgroups as your table
05:28
<GPHemsley>
(I at first only commented out the one colgroup)
05:29
<GPHemsley>
MikeSmith: It still complains, it appears
05:29
<GPHemsley>
"Table column 13 established by element th has no cells beginning in it."
05:37
<MikeSmith>
GPHemsley: maybe I'm being daft, but I can't understand why you have a colspan=2 on the column at all
05:37
<GPHemsley>
because it's a WIP :)
05:37
<MikeSmith>
it's a normal column, right?
05:38
<GPHemsley>
I plan on adding more rows to the table ;)
05:38
<MikeSmith>
ah
05:38
<GPHemsley>
and some of them will have two-column entries under that header
05:40
<GPHemsley>
so, what's the verdict?
05:40
<GPHemsley>
is it a bug?
05:40
<MikeSmith>
not a bug
05:41
<MikeSmith>
if you change all your <td colspan="2">&empty;</td> for that column
05:41
<MikeSmith>
in the body of the table
05:41
<MikeSmith>
change those to <td>&empty;</td><td>&empty;</td>
05:41
<MikeSmith>
it validates
05:41
<GPHemsley>
right, as I would expect
05:42
<MikeSmith>
yeah, so what it is telling you is that you have set up an unneeded colspan=2 column all the way down
05:42
<MikeSmith>
I guess
05:42
<GPHemsley>
yeah, makes sense
05:42
<GPHemsley>
although it's a little weird that it's an error, IMO
05:42
<GPHemsley>
(rather than a warning)
05:42
<GPHemsley>
but IDK what the spec says to do
05:43
<MikeSmith>
yeah, me neither
05:43
<MikeSmith>
but I suspect that if Henri has the code reporting it as an error, it's because the spec says it's an error
05:43
<GPHemsley>
:)
05:44
<MikeSmith>
now, whether the spec should define it as an error or not is arguable, I guess
05:45
GPHemsley
pokes hsivonen and Hixie
05:49
<MikeSmith>
<BoazSender> @paul_irish will be sorely missed: http://twitpic.com/1sn5pn
05:49
<MikeSmith>
beautiful
05:49
<MikeSmith>
I guess that image is the work of f1lt3r
05:50
<f1lt3r>
haha
05:50
<f1lt3r>
you guessed right
05:50
<paul_irish>
very nice work, al. :)
05:50
<paul_irish>
<3z
05:50
<f1lt3r>
haha
05:50
<f1lt3r>
what you doin in here?
05:51
<f1lt3r>
yeah i thought you'd get a kick out of it
05:51
<paul_irish>
i'm sweeping my old apt. about to leave it for the last time. and you know.. hanging out on IRC
05:51
<f1lt3r>
crazy times!
05:52
<boaz>
I definitely laughed!
05:52
<f1lt3r>
hey what the wg are you doing in here too?!
05:52
f1lt3r
checks to see if his grandma is in here too
05:54
GPHemsley
wonders why <col style> still isn't supported in Firefox...
06:16
<hsivonen>
krijnh: the <!-- in style thing is fixed on trunk
06:57
<Hixie>
so anyone know what's going on with the issues that went to poll last month?
06:57
<Hixie>
sorry, earlier this month, not last month
07:46
<hsivonen>
Hixie: nothing visible going on as far as I can tell
09:14
hsivonen
fails to see the multitouch-relevance of http://www.w3.org/Bugs/Public/show_bug.cgi?id=9822
09:15
<aho>
huh?
09:15
<aho>
what's that bug report even supposed to mean?
09:26
<jgraham>
Hixie: Welcome back :)
09:33
<boblet>
MikeSmithX: here’s a report of the Fukuoka HTML5 event in Gigazine, in case you missed it: http://gigazine.net/index.php?/news/comments/20100529_html5/
09:33
<boblet>
your dearly departed mustache makes an appearance, may it rest in peace
09:35
hsivonen
encourages security-minded folks to think about http://www.w3.org/Bugs/Public/show_bug.cgi?id=9659#c2
09:36
<hsivonen>
I'm a bit disappointed that no one from Microsoft shared any insight on http://www.w3.org/Bugs/Public/show_bug.cgi?id=9767 even though I advertised it on public-html
09:38
<hsivonen>
shepazu: any news on the load event from the SVG WG?
09:39
<hsivonen>
shepazu: should I send email amending my change request to request that the load event be dropped from non-<svg> elements altogether?
09:51
<MikeSmithX>
boblet: thanks
09:52
<MikeSmithX>
I got Shimokawa-san's mail about that but hadn't looked yet
09:52
<boblet>
aah ok
09:52
<MikeSmithX>
seems like a very good writeup
09:52
<boblet>
seems like everyone enjoyed it, which was good
09:52
<boblet>
yeah
09:53
<boblet>
bbl
11:13
<jgraham>
hsivonen: I assume you failing the html5lib tests like <!DOCTYPE html><p><b><i><u></p> <p>X is deliberate? Do you have a bug for the spec change you anticipate?
11:26
<hsivonen>
jgraham: the test that fail due to space character interaction of space characters with formatting elements are known
11:27
<hsivonen>
*tests
11:27
<hsivonen>
jgraham: and deferring fixing is deliberate
11:28
<jgraham>
hsivonen: You consider it a bug in the spec or in gecko?
11:28
<hsivonen>
jgraham: whether the failure itself should be considered deliberate isn't quite so clear to me, but I tend to think that it'd bad to make "in body" sensitive to spaceness
11:28
<hsivonen>
jgraham: I consider it a bug in Gecko, but more careful thinking might persuade me to consider it a bug in the spec
11:29
<hsivonen>
I think how forcefully I will consider it a spec bug will depend on performance metrics that I don't have at this time
11:30
<jgraham>
hsivonen: OK, thanks. Maybe we should have a list on a wiki page or something of possible issues? I seem to recall that there were some other things that you considered bugs in the spec?
11:31
<hsivonen>
jgraham: the other spec bugs are on file
11:31
<jgraham>
hsivonen: Is there a list somewhere?
11:32
<hsivonen>
jgraham: except I think Hixie avoided fixing one bug I had filed before and I should take the time to repursue
11:32
<hsivonen>
(that was about freezing src, async and defer)
11:33
<hsivonen>
jgraham: you get a list if you search for bugs reported by hsivonen⊙if in the W3C bugzilla
11:36
<hsivonen>
the src, async defer thing is only detectable if you document.write a script start tag, then use the DOM to modify the element and then write the end tag
11:41
<hsivonen>
jgraham: but yeah, we should probably have a wiki page
11:42
<hsivonen>
jgraham: any ideas for the title? "Possible bugs in the HTML5 parsing algorithm according to hsivonen"? :-)
11:43
<jgraham>
hsivonen: http://wiki.whatwg.org/wiki/ParserIssues
11:43
<hsivonen>
jgraham: ok
11:43
<jgraham>
Does that list seem complete
11:43
<jgraham>
?
11:44
<hsivonen>
jgraham: I'm adding the missing bits
11:45
<jgraham>
hsivonen: Thanks
11:52
<hsivonen>
jgraham: updated
11:56
<jgraham>
great
12:05
<boblet>
anyone know what’s up with HTML5 + ARIA? Wasn’t there a combo spec? I found Mike’s H:TML (ARIA edition) but it’s Sept 2009, so I’m guessing not being updated…
12:09
<hsivonen>
boblet: http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#annotations-for-assistive-technology-products-%28aria%29
12:10
<hsivonen>
boblet: so ARIA still lives in its own specs and HTML5 references those
12:11
<boblet>
hsivonen: aah, naruhodo. Yeah I’d found that, but obviously needed to read the first sentence more thoroughly
12:11
<boblet>
AT is a rather sad state of affairs. Luckily NVDA is eating their lunch so they’ll be forced to evolve or die
12:13
<boblet>
couldn’t believe the attitude of Window-Eyes devs; ‘spec not finished so not worth our time til then’ O_o
12:13
<boblet>
doesn’t help that they have major bugs with new elements + landmark roles either
12:14
<hsivonen>
boblet: "spec" being ARIA or HTML5?
12:14
<boblet>
hsivonen: HTML5
12:15
<boblet>
oh, is ARIA not doe either? har! well I guess that reasoning means they don’t really need to support anything then
12:15
<boblet>
s/doe/done/
12:15
<hsivonen>
boblet: ARIA is at WD
12:18
<boblet>
“Not only is HTML5 still in draft, there are parts of ARIA that are sill not completely set in stone. This is another reason why providing some sort of release time frame is difficult; the technologies are a moving target” http://www.mail-archive.com/gw-info⊙gc/msg10851.html
12:19
<boblet>
so they appear to be waiting, although not until 2022 it seems
12:22
<hsivonen>
boblet: I guess they haven't gotten the memo about the interdependency of spec maturity and implementations
12:24
<MikeSmith>
hsivonen: I did some hacking to the v.nu datatype code today in an attempt to improve error-reporting for IRIs a bit
12:24
<hsivonen>
MikeSmith: cool
12:24
<MikeSmith>
current results: http://www.w3.org/html/check?doc=http%3A%2F%2Fbugzilla.validator.nu%2Fattachment.cgi%3Fid%3D177
12:25
<MikeSmith>
compare to current source: http://validator.nu/?doc=http%3A%2F%2Fbugzilla.validator.nu%2Fattachment.cgi%3Fid%3D177
12:25
<MikeSmith>
trying to make the messages a little more user friendly
12:26
<MikeSmith>
e.g., instead of "DNS_LABEL_DASH_START_OR_END in HOST", "Host component contains a DNS name with a - (dash) character at the beginning or end."
12:26
<MikeSmith>
etc.
12:28
<MikeSmith>
along the way, discovered a couple of other IRI-checking cases that it seems like should be reported as warnings instead of errors
12:28
<hsivonen>
MikeSmith: that's great!
12:29
<MikeSmith>
I think there's probably a few cases I missed
12:29
<MikeSmith>
but anyway, for those cases, it'll just fall back to reporting them the same way as the existing code
12:30
<hsivonen>
ok
12:30
<MikeSmith>
anyway, will send you a patch after I test it some more
12:30
<hsivonen>
ok
12:30
<MikeSmith>
and maybe if I can get zcorpan_ to throw some other test cases at it
12:31
<hsivonen>
about the Jing patch: I need to check what kind of copyright bureaucracy the project requires (if any) before I land the patch
12:31
<MikeSmith>
ah
12:31
<MikeSmith>
ok
12:32
<MikeSmith>
no rush, anyway
12:33
hsivonen
MikeSmith I take it that you are contributing the Jing patch the same way as other V.nu patches, i.e. under the same license as the file being patched and waiving notices?
12:33
<hsivonen>
doh
12:33
<MikeSmith>
heh
12:34
<MikeSmith>
I guess that was supposed to be a DM
12:34
<hsivonen>
yeah
12:34
<MikeSmith>
good thing you didn't reveal any secrets of the inner cabal there
12:34
<MikeSmith>
anyway, yeah, same terms as always
12:34
<annevk>
you guys keeping secrets? ooh
12:34
<hsivonen>
ok
12:37
<Dashiva>
There are no secrets... that you know of
12:37
<MikeSmith>
annevk: all of it is stuff you already signed an NDA on too
12:37
<MikeSmith>
annevk: plus remember the blood-brother ceremony
12:37
<hsivonen>
a new binary release of the V.nu parser is long overdue
12:38
<hsivonen>
but every time I get close to the point of releasing, there's still One More Thing to fix first...
12:38
<MikeSmith>
heh
12:38
<hsivonen>
this time the changes to named character references in attribute values
12:39
<MikeSmith>
hsivonen: because of a spec change?
12:39
<MikeSmith>
recent spec change?
12:39
<hsivonen>
MikeSmith: yeah
12:39
<hsivonen>
MikeSmith: fairly recent
12:39
<hsivonen>
before that, my excuse was </a> and </font> in SVG
12:45
<boblet>
hsivonen: …or the one about how being involved is a good thing :/ oh well, what can you do. With the free NVDA already supporting ARIA and some HTML5 too…
12:50
<MikeSmith>
ah cool, Opera 10.6 gots onhashchange
12:51
<hsivonen>
does it have WebM?
12:51
<gsnedders>
hsivonen: no
12:51
<hsivonen>
:-(
12:54
hsivonen
wonders if Opera has a solid plan for <video> in Mini and Mobile
13:02
<annevk>
http://twitter.com/Klok_Domtoren lol
13:05
<Peter`>
They based that on the London clock account
13:06
<Peter`>
http://twitter.com/big_ben_CLOCK
13:06
<Dashiva>
Localization is important
13:06
<Peter`>
but yeah, the idea is quite.. original
13:06
<svl>
see also http://twitter.com/NotreDameDParis
13:06
<svl>
actually: http://twitter.com/memowe/kirchen-die-twittern
13:07
<annevk>
great
13:17
<Lachy>
Awesome. Now all we need is someone to implement NTP over Twitter. :-)
13:17
<hsivonen>
can't fail
13:17
<Lachy>
... or Twitter Time Protocol
13:23
<Dashiva>
I guess you could get second precision via twitter, which is enough for normal human use
13:35
<Lachy>
I'm not sure you could even get that level of precision any more. It may have been possible when they were sending out tweets in near real time when they had Jabber support.
13:36
<Lachy>
But I don't think it's possible with the current API setup that, AIUI, needs to be done by the client polling twitter for updates at regular intervals.
13:50
<Philip`>
Surely you could just use a timestamp from an HTTP header in the response from the Twitter API, instead of looking in the actual tweet to work out the time
13:50
<Philip`>
or would that be considered an unacceptable layering violation?
13:51
<gsnedders>
Philip`: The server isn't required to return the right value
13:53
<Philip`>
gsnedders: It's even less required to return the right value in the response body
13:54
<jgraham>
Philip`: Presumably the contents of the response body count as application-level semantics
13:54
<jgraham>
It's true that twitter doesn't make any promises
13:54
<jgraham>
So using twitter for time would probably be a bad idea
13:55
<Lachy>
The inefficiency of twitter for this purpose doesn't seem to stop people from trying http://twitter.com/CurrentTime
13:56
<jgraham>
The inefficiency of twitter for any and all communications doesn't stop people trying
14:07
<hsivonen>
I guess now my only excuse for not making a release of the V.nu parser is the 8000 byte limit
14:08
<hsivonen>
so it will be slow unless run with a special VM switch
14:08
<hsivonen>
I wonder if I should make a release anyway or develop a workaround...
14:09
<hsivonen>
I guess I should develop a workaround...
14:17
<hsivonen>
MikeSmith: I redeployed V.nu without your recently landed patches and mine
14:17
<MikeSmith>
ok
14:24
<variable>
hsivonen: what is v.nu ?
14:25
<hsivonen>
variable: validator.nu
15:48
<aliok>
hi everybody
15:49
<annevk>
hi hi
15:49
<aliok>
can anyone direct me a good demo of Html5 <output> element?
15:50
<aliok>
Btw, I am working on my GSoC project Apache MyFaces Html5 Support: http://wiki.apache.org/myfaces/GSoC2010_HTML5
15:51
<annevk>
aliok, http://www.whatwg.org/demos/2008-sept/widgets/demo2.html
15:51
<annevk>
oh oops
15:51
<annevk>
looks like Hixie used a <span> rather than <output>
15:51
<annevk>
anyway, that <span> there should be <output> :)
15:52
<aliok>
yeah, I see :)
15:52
<aliok>
thanks
15:53
<aliok>
but, what about @for @mode and @defaultValue attributes? any example using them? especially @for?
15:55
<annevk>
defaultValue is a DOM attribute
15:55
<annevk>
for allows you to couple it to the input box; can be useful for screen readers
15:55
<annevk>
they prolly do not implement that yet but maybe in the future
15:55
<annevk>
and I've no idea what mode is
15:55
<jgraham>
Philip`: Where did you hide your O'Caml HTML5 parser?
15:55
<annevk>
in other news...
15:56
<annevk>
http://www.w3.org/2010/05/31-svg-minutes.html#item05 -- "<AlexD> Given how long it will take HTML5 to mature (i.e. PREC) then perhaps SVG needs to take some lead in an HTML(4)+SVG integration profile... HTML5 is a bit of vapourware right now really."
15:56
<jgraham>
Good lord, who are these people and which universe do they live in?
15:56
<Philip`>
jgraham: I cunningly hid it on the internet
15:56
<hsivonen>
https://bugzilla.mozilla.org/show_bug.cgi?id=558036 hasn't landed, yet, so @for support can't be demoed in Gecko plus screen reader yet
15:57
<hsivonen>
who is AlexD?
15:57
<aliok>
thanks annevk
15:57
<Philip`>
jgraham: Looks like it's at http://canvex.lazyilluminati.com/svn/tokeniser/
15:58
<annevk>
http://www.w3.org/2000/09/dbwg/details?group=19480&public=1 -- "Alex Danilo"
15:58
<annevk>
aliok, where did you find "mode"?
15:59
<jgraham>
Philip`: Thanks
15:59
<karlushi>
Alex Danilo was? working for Canon
16:09
<annevk>
he's listed as invited expert; I think I met him once, back in the CDF / WICD days...
16:42
gsnedders
gets peckish, looks for food in his flat, and realizes he has almost none. That seems problematic.
16:48
<jgraham>
You could take up a religion that enforces fasting until sunset
16:51
<Lachy>
jgraham, adopting such a religion in this part of the world would be torture during summer.
16:51
<jgraham>
Lachy: I realise :)
16:53
<jgraham>
gsnedders: (alternatively I recommend exchaning money for food)
16:54
<gsnedders>
jgraham: That means walking past work, and that seems too much like reminding me that I'm not a free bird.
16:58
<jgraham>
gsnedders: You have too little route planning imagination
16:58
<gsnedders>
:P
17:22
<jgraham>
I love the fact that even though the STIX fonts have been released, there will be no LaTeX versions for another year
17:24
<Philip`>
Does that mean a real year, or a STIX "year"?
17:26
<jgraham>
I guess it means a STIX year
17:26
<jgraham>
Which could be as much as a decade
17:26
<jgraham>
to those using normal calendars
17:28
<jgraham>
I suppose a consistent viewpoint would be that the STIX people are moving at a highly relatvistic velocity with respect to the rest of us
17:34
Philip`
wonders to what extent the notation of modern mathematics is driven by font availability rather than by more traditional factors like readability
17:35
<Philip`>
(I assume that e.g. Leibniz could write down the integral symbol without having to care whether it was already supported by his typesetting package)
17:35
<Philip`>
(but nowadays it takes far too much effort to make up completely new symbols)
19:57
<GPHemsley>
MikeSmithX: If you're interested, this is now much more complete: http://gphemsley.org/linguistics/en/trace_table.php
20:34
<boaz>
yo!
20:34
<boaz>
whatwg!
20:34
<boaz>
im working on some css3 animations. anyone in here know about matrix syntax for the filter prop in IE?
20:41
<boaz>
MikeSmittXX
20:42
<boaz>
do you know who i would talk to about IE css filter matrix syntax?
20:46
<Philip`>
boaz: You should probably talk to Microsoft people
20:47
<boaz>
Philip :(
20:47
<Philip`>
or use http://msdn.microsoft.com/en-us/library/ms533014(VS.85).aspx
20:47
<boaz>
yah, im on msdn, the matrix syntax seems to not be documented
20:47
<boaz>
er, at least, the syntax for what I want do
20:47
<boaz>
http://msdn.microsoft.com/en-us/library/ms533014(VS.85,loband).aspx
20:48
<boaz>
im looking for something like this: matrix(a, c, b, d, tx, ty)
20:49
<Philip`>
It looks like it's just a list of the specified properties - progid:DXImageTransform.Microsoft.Matrix(m11=1, m12=0, m21=1, m22=0, dx=0, dy=0)
20:54
<boaz>
philip: hmm
23:46
<roc>
where's the HTML5 parser test suite that you can run in a browser?
23:47
<Philip`>
roc: http://gsnedders.html5.org/html5lib-tests/runner.html
23:48
<roc>
great thanks
23:48
<roc>
do you know if it tests SVG-in-HTML?
23:49
<Philip`>
It includes http://gsnedders.html5.org/html5lib-tests/data/tests11.dat
23:49
roc
looks
23:49
<Philip`>
and http://gsnedders.html5.org/html5lib-tests/data/tests10.dat
23:49
<roc>
great thanks
23:49
<Philip`>
which look like SVG tests