00:31
<openstandards>
evening all
02:45
<micheil>
is <meta http-equiv="X-UA-Compatible" content="IE=edge" /> valid html5?
02:49
<Anti-X>
why wouldn't it be?
02:49
<MikeSmith>
micheil: no, it's not valid
02:49
<micheil>
okay
02:50
<micheil>
I wasn't sure, I'd just seen it in several places, including ALA
02:50
<MikeSmith>
the value of the http-equiv attribute is constrained to being an enumerated list
02:50
<Anti-X>
really?
02:50
<MikeSmith>
Anti-X: yeah
02:50
<MikeSmith>
that's one thing that's changed in HTML5
02:51
<MikeSmith>
micheil: yeah, some individual people at ALA came out in support of it
02:51
<Anti-X>
i didn't think values of meta attributes would ever matter
02:51
<micheil>
okay, but it's not actually part of the strict standards
02:51
<Anti-X>
for validity purposes
02:51
<MikeSmith>
oh whoops
02:51
<MikeSmith>
I meant WASP
02:53
<MikeSmith>
it matters because we want to help authors be aware that only certain values have an effect, and only certain values have agreed-upon semantics
02:54
<MikeSmith>
e.g., some people think they can set HTTP headers on the client side somehow by using the http-equiv attribute
02:55
<MikeSmith>
or they think at least that browsers will have behavioral responses to whatever values are set there
02:55
<micheil>
right, which isn't correct, yes?
02:59
<MikeSmith>
right
03:00
<MikeSmith>
http://dev.w3.org/html5/markup/meta.html#meta gives an overview
03:01
<MikeSmith>
if you click on the circled i links, that will take you to the corresponding info in the actual HTML5 spec
03:02
<MikeSmith>
micheil: on a different subject, do you happen to now how often the v8 subdir in the node source repo is updated
03:03
<micheil>
umm..
03:03
<MikeSmith>
if there's some update policy
03:03
<micheil>
when ever v8 is usually
03:03
<MikeSmith>
OK
03:03
<MikeSmith>
well, v8 has two branches
03:03
<MikeSmith>
trunk and "bleeding edge"
03:04
<MikeSmith>
changes were pushed from bleeding-edge to trunk yesterday
03:04
<MikeSmith>
so I guess I should just check to see if they made it into the node repo yet
03:04
<MikeSmith>
v8 trunk version is now at 2.4.3
03:20
<paul_irish>
micheil: for both ie=edge and chromeframe, headers can be sent that do the same thing (and get around the validation problem)
03:20
<paul_irish>
but.. yeah the validator bitches about it. ohwell.
03:21
<paul_irish>
one of the more prominent cases where best practices conflict with conformance.
03:21
<hober>
MikeSmith: I've made a lot of progress on the elisp tokenizer lately
03:22
<MikeSmith>
super
03:22
<hober>
hoping to get it to an experimentally-useful state in the next couple of weeks
03:22
<hober>
I think 80% of desirable major mode features can be tackled with just a tokenizer backend
03:22
<hober>
the remaining 20% will require the tree builder
05:52
<wirepair>
not sure who here updates the whatwg wiki but some of the images are broken on: http://wiki.whatwg.org/wiki/index.php?title=Rationale
07:26
<annevk>
great, so now public-html gets spammed with NotInW3CSpecYet
07:26
<annevk>
funny
07:27
<annevk>
hsivonen, are you following the thread on www-dom regarding exposing the keyboard locale?
07:29
<annevk>
hsivonen, given your bugs on reducing the uniqueness of users
07:52
<annevk>
http://www.phoboslab.org/biolab/ -- yay, old school type games in JavaScript :)
07:54
<wirepair>
wow that is neat.
07:56
<annevk>
http://blogs.msdn.com/b/ie/archive/2010/09/13/web-standards-from-working-draft-to-recommendation.aspx -- no mention of XMLHttpRequest
07:56
<annevk>
typical
07:59
<annevk>
oh god
07:59
<annevk>
Microsoft promotes unknown elements with this tagline
07:59
<annevk>
"This allows you to semantically describe the content of your page without losing any of the power you have with normal elements, using the same code as you would in other browsers."
07:59
<annevk>
fail
08:04
<hsivonen>
annevk: where's the quote from?
08:06
<annevk>
IE blog
08:06
<annevk>
http://blogs.msdn.com/b/ie/archive/2010/09/13/interoperable-html-parsing-in-ie9.aspx
08:07
<hsivonen>
annevk: 386 time!
08:09
<annevk>
I guess -- though I already pointed this out in 2005: http://annevankesteren.nl/2005/05/generic-xml
08:33
<jgraham>
386 time?
08:34
<annevk>
correcting people on the interwebs
08:34
<annevk>
see last two blog posts I made
08:34
<jgraham>
Oh
08:34
<jgraham>
xkcd :)
08:34
<annevk>
:)
08:35
<annevk>
http://twitter.com/foolip/status/24457028326 notices it too
08:38
<jgraham>
That is the biggest WTF, but I also have to wonder why they copied the webkit AAA rather than the HTML5 one
08:38
<jgraham>
In fact if they were rewriting the parser, why not just go for the HTML5 one from the start
08:39
<annevk>
euh yeah, dunno
08:43
<jgraham>
Oh, I see abarth already asked that :)
08:43
<phrearch>
hi
08:43
<abarth>
yeah, that blog post makes no sense
08:43
<phrearch>
i wonder whether websockets can be used for file uploads
08:48
<jgraham>
phrearch: Well yes, it's just getting access to the file that is the problem
08:49
<phrearch>
jgraham: reading up on it, it seemed everyone is using a post-to-iframe hack
08:49
<phrearch>
found something about new file functionality in http://soakedandsoaped.com/articles/read/firefox-3-native-ajax-file-upload
08:50
<phrearch>
webkit doesnt seem to support this though :(
08:50
<phrearch>
like getting the file as binary in js
08:51
<phrearch>
and then send it over the wire using whatever technique is available
08:51
<jgraham>
Yeah, not really sure what the state of support of the FileAPI is
08:51
<jgraham>
Websockets in particular currently only supports text uploads but one can always e.g. base64 encode stuff (in exchange for larger file size)
08:52
<phrearch>
yea that would be an idea
08:52
<Peter`>
Ericsson added binary data support for WebSockets for their Device experiments (https://labs.ericsson.com/blog/beyond-html5-conversational-voice-and-video-implemented-webkit-gtk)
08:52
<jgraham>
Binary will be supported in the future once we have a proper binary array type standard
08:52
<phrearch>
checking if getAsBinary is supported in later versions of chrome
08:53
<phrearch>
ow cool!
08:53
<annevk>
jgraham, thanks for "WTF" -- http://annevankesteren.nl/2010/09/generic-elements
08:53
<phrearch>
webcam support in html5 :)
08:54
<phrearch>
would be interesting to see a voice solution with js-only :)
08:56
<jgraham>
annevk: drop ", to be perfectly clear", it reads badly (imho) and it should probably be "will have the semantic meaning"
08:58
<phrearch>
i wonder why binary support is still not in websockets
08:58
<phrearch>
err in the specs
08:59
<annevk>
jgraham, thanks! fixed
08:59
<annevk>
phrearch, it is in some specs
09:00
<phrearch>
annevk: hope it gains some momentum
09:01
<annevk>
it has
09:02
<annevk>
will prolly take another year or so for it to reach stability
09:03
<phrearch>
cant wait :)
09:11
<phrearch>
hm, xhr2 seems to have an upload thingy
09:12
<hsivonen>
annevk: 'it' being Web Sockets?
09:13
<annevk>
octet APIs
09:14
<annevk>
is it octet or binary? I always wonder what the proper term here is...
09:14
<annevk>
or maybe byte?
09:15
<hsivonen>
byte unless you want to use IETF-speak
09:19
<annevk>
so the hard parser limits being discussed are only for the invalid cases right?
09:19
<annevk>
or did I miss something?
09:21
<hsivonen>
annevk: I suggested on limitation that'd apply to deep nesting of currently conforming formatting elements, too
09:21
<hsivonen>
s/on/one/
09:22
<annevk>
oh, that seems less nice
09:22
<hsivonen>
annevk: but that could easily be addressed by making insanely nesting <i> non-conforming
09:22
<hsivonen>
like <i> nested ten deep
09:22
<annevk>
new Web DOM Core snapshot: http://lists.w3.org/Archives/Public/www-archive/2010Sep/att-0015/Overview.html
09:27
<zcorpan_>
MikeSmith: NotInW3CSpecYet implies that it's going to be?
09:28
<zcorpan_>
MikeSmith: isn't the component "other hixie drafts" the same thing?
09:31
<zcorpan_>
is http://www.w3.org/Bugs/Public/show_bug.cgi?id=10586 the start of element creep in websrt? (i can imagine mathml in subtitles)
09:32
<annevk>
heh, didn't even notice the implication of "Yet"
09:34
<nessy>
I wished there was proper names on those bug submissions, not just contributor⊙.
09:34
<hsivonen>
zcorpan_: innerHTML parsing in SRT FTW
09:35
<zcorpan_>
hsivonen: yeah it's possible that we end up with that in the end
09:36
<hsivonen>
zcorpan_: it would be nice if Hixie gave in and we didn't have to walk the path of speccing and prototyping something else first
09:37
<zcorpan_>
http://www.businessinsider.com/disney-hates-on-html5-2010-9 what do they mean with 'no room for ads'?
09:38
<nessy>
probably ads in video, I would think
09:38
<hsivonen>
zcorpan_: I think they are also confusing "copyright protection" with TPM
09:38
<zcorpan_>
yeah, but surely that's possible with <video>
09:39
<jgraham>
MathML in subtitles would be awesome
09:39
<jgraham>
I mean insane
09:39
<jgraham>
But the awesome kind of insane
09:39
<nessy>
insanely awesome :)
09:39
<hsivonen>
jgraham: subtitled math lectures
09:40
<jgraham>
hsivonen: Yes, I see the sue case
09:40
<jgraham>
*use
09:40
<jgraham>
(bad typo)
09:40
<hsivonen>
I'd rather support MathML than karaoke
09:40
<jgraham>
But it seems like it would be hard to keep up
09:40
<hsivonen>
from the technical req POV
09:41
<jgraham>
Captions are typically ephemeral
09:41
<jgraham>
but equations need to stay up a long time to digest and copy
09:41
<annevk>
so SRT with HTML fragments?
09:42
<annevk>
as cues
09:42
<zcorpan_>
jgraham: nothing prevents cues staying up a long time
09:42
<jgraham>
(if I were implementing virtual maths lectures, I would probably try toi implement a virtual blackboard that rendered away from the video and retained all its contents)
09:43
<jgraham>
zcorpan_: No, but after the first blackboard-full of equations you can't see the video any more
09:43
<zcorpan_>
lol
09:44
<hsivonen>
annevk: yes. (I've been like a broken record about this)
09:47
<nessy>
hsivonen: don't stop that record!
09:47
<nessy>
though I am not so worried about it any more, since cues can have innerHTML as "metadata", I guess
09:49
<jgraham>
On an entirely different topic, is anyone else bothered by the "no excuses" pitch on the topic of bugspam? It seems to be about aportioning blame rather than achieving desirable goals (e.g. "everyone should have the information they need to participate in discussions relevant to them")
09:51
<zcorpan_>
aren't PERs usually announced on w3.org?
09:52
<hsivonen>
jgraham: I am, but I kinda sympathize given the circumstances
09:53
<hsivonen>
but then, I tend to follow bugmail, I still missed Hixie "simplifying" my U+0000 handling suggestion and I missed Hixie making <figure> close <p>
09:53
<hsivonen>
in a timely fashion, that it
09:53
<hsivonen>
*that is
09:53
<annevk>
zcorpan_, yeah
09:53
<hsivonen>
I found out once the corresponding test cases had made it to html5lib
09:53
<annevk>
zcorpan_, ij⊙wo can prolly help out (there's a dedicated address for this that I forgot)
09:54
<zcorpan_>
ok
09:58
<zcorpan_>
hsivonen: hasn't <figure> closed <p> since forever?
09:58
<hsivonen>
zcorpan_: nope
09:58
<zcorpan_>
i thought just <figcaption> changed
09:58
<hsivonen>
zcorpan_: then I have missed the change since forever
09:59
<zcorpan_>
<figure> closes <p> in my copy of minefield
09:59
<hsivonen>
ok. I'm confused, then
10:00
<hsivonen>
I still think that <figure> closing <p> is Bad.
10:05
<annevk>
Ms2ger, zcorpan_, clone throws for DocumentType, but that does not seem to work well if you want to clone e.g. Document
10:05
<annevk>
Ms2ger, zcorpan_, I guess it should not throw at all?
10:06
<Ms2ger>
I guess
10:06
<zcorpan_>
can you clone a document?
10:06
<annevk>
I think you can in most impl
10:09
<zcorpan_>
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/629 http://software.hixie.ch/utilities/js/live-dom-viewer/saved/630
10:09
<zcorpan_>
opera throws for both, firefox clones both, webkit clones the doctype but returns null for document
10:17
<annevk>
hmm
10:19
zcorpan_
wonders what's up with '386'
10:20
<Philip`>
jgraham: For a virtual maths lecture, why not just write some prose notes containing all the equations and suchlike (using LaTeX or HTML+MathML or whatever), and distribute that in parallel with the video?
10:20
<Philip`>
That seems simpler than a virtual blackboard and probably better usability
10:22
<annevk>
zcorpan_, xkcd
10:22
<jgraham>
Philip`: Also a good idea, but loses the synchronisation
10:22
<jgraham>
You could e.g. make the handout avaliable at the end of the lecture
10:30
<annevk>
Philip`, that would be too pragmatic
10:30
<MikeSmith>
ara! I just now discovered that Colloquy puts little indicators in my scrollbar to mark the point where somebody nick-pinged me
10:30
<MikeSmith>
sweet
10:31
<MikeSmith>
zcorpan_: about NotInW3CSpecYet, see the description: "This bug is for a feature that is has been adopted into the W3C version of HTML5 and may never be, and that is not under the HTML WG decision policy and may never be."
10:31
<MikeSmith>
oops
10:31
<MikeSmith>
missed a "NOT"
10:32
MikeSmith
fixes it
10:35
<annevk>
https://bugs.webkit.org/show_bug.cgi?id=45645 lol
10:41
<MikeSmith>
I would like to ask a favor from everybody here who has some time today to do a little review
10:42
<MikeSmith>
which is, please review the following
10:42
<MikeSmith>
http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Checklist
10:42
<MikeSmith>
and comment on it if you find anything that you think should be changed in it
10:43
<MikeSmith>
anything removed, anything that needs to be added, anything altered/clarified
10:45
<MikeSmith>
about the topic areas, there are links that lead back to a more detailed description
10:45
<MikeSmith>
e.g., for the "DV" requirements, see http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements#Described_video
10:47
<MikeSmith>
nessy and others have spent a lot of time working together on hammering out the details of that checklist
10:47
<MikeSmith>
so it would be a professional courtesy at the very least to actually take time to read and respond to it
10:48
<MikeSmith>
it seems to me to be a pretty good document overall
10:49
<annevk>
while it seems like a good end goal, I'm not sure we want to meet those requirements all at once
10:50
<annevk>
that would just take forever and not help accessibility meanwhile
10:50
<MikeSmith>
annevk: would probably be an acceptable (meta)comment to make
10:51
<MikeSmith>
comment being, in a message to public-html
10:51
<annevk>
it's been said before
10:51
<MikeSmith>
I can also post a heads-up to the whatwg list about this I guess, and invite further comments there
10:51
<MikeSmith>
annevk: ah, OK
10:52
<MikeSmith>
annevk: another thing is, we would not want to be in the position later of having those requirements presented back to us as a fait accompli
10:53
<MikeSmith>
and being told that, You had the opportunity to comment on detail on those, and to ask for changes to them, and you didn't take it.
10:53
<annevk>
hah, good luck if they try playing it like that
10:54
<MikeSmith>
well, I'm not saying that anybody who's actually involved in creating those would do that
10:54
<MikeSmith>
because they would not
10:55
<MikeSmith>
I guess I'm just thinking about other possible polemicists who might choose to join the fray
10:55
<annevk>
some of the requirements seem kind of wrong btw
10:55
<MikeSmith>
so ignore that, thought, actually
10:55
<annevk>
"specify a character encoding" must?!
10:56
<annevk>
for i18n no less
10:56
<MikeSmith>
annevk: that indeed does seem not necessary to be a must
10:56
<annevk>
guess they missed how UTF-8 obsoleted that need
10:57
<jgraham>
I would prefer that as a MUST NOT, all things considered :)
10:59
<annevk>
i think it would help if they prioritized things
10:59
<annevk>
everything may be a must, but some are more important than others
11:01
<MikeSmith>
annevk, jgraham - I started adding comments on the Talk page there - http://www.w3.org/WAI/PF/HTML/wiki/Talk:Media_Accessibility_Checklist
11:03
<MikeSmith>
david_carlisle: hey
11:04
<annevk>
ta MikeSmith
11:04
<MikeSmith>
np
11:04
<MikeSmith>
thanks for the comments
11:04
<MikeSmith>
I just used what you said verbatim :)
11:04
<jgraham>
Yes, some things seem to depend on stuff that we are a way away from supporting
11:05
<jgraham>
Like an api for stero
11:05
<jgraham>
*stereo
11:05
<annevk>
stereo is in there?
11:06
<annevk>
i thought syncing audio with video was a complex one already
11:06
<annevk>
or syncing video with video
11:06
<jgraham>
annevk: There was something about being able to pan the audio
11:06
<david_carlisle>
hsivonen: "I'd rather support MathML than karaoke" Thanks for this support:-) (wouldn't subtitles without maths in them be boring?)
11:21
<Ms2ger>
jarib, http://aryeh.name/tests/reflection.html might be a good place to start for an index
12:17
<jarib>
Ms2ger: interesting
12:20
<jarib>
Ms2ger: if we could figure out how the index should be organized, i'd be happy to start doing the boring work :)
12:21
<jarib>
hmm, can't figure out the clone URL for that repo
12:22
<jarib>
AryehGregor: ^^
12:36
<annevk>
Ms2ger, so what features of Anolis are we using that pimp my spec does not have?
12:37
<Ms2ger>
xspecxref.py and refs.py
12:37
<annevk>
cross-spec xref?
12:37
<Ms2ger>
Yes
12:37
<annevk>
oh, references
12:37
<annevk>
right
12:38
<annevk>
hmm
12:39
<annevk>
i guess either I have to get this to run locally or just lose those features for now
12:39
<annevk>
until jgraham catches up :)
12:39
<annevk>
having cross-spec xref and references would be neat -- though not sure how they work with a web interface
12:39
<Ms2ger>
Pubrules will probably want more detailed references, though
12:40
<annevk>
no
12:40
<annevk>
see e.g. XMLHttpRequest
12:41
<Ms2ger>
Works for me, then
12:41
<annevk>
yeah, it just doesn't for me :/
12:41
<Ms2ger>
Heh
12:54
<Ms2ger>
I think it shouldn't be too hard to get the json files somewhere on the server where anolis can find them
12:54
<annevk>
and how do we update them then?
12:55
<Ms2ger>
Bug jgraham? ;)
12:55
<annevk>
yeah, I guess we can provide patches
12:56
<Ms2ger>
They shouldn't change too often
13:03
<annevk>
zcorpan_, new thread next time?
13:04
<zcorpan_>
yeah, sorry
13:11
<nessy>
MikeSmith: ping?
13:15
<MikeSmith>
nessy: hej
13:15
<nessy>
hey, I am surprised you sent a link to the Checklist to the WHATWG - how come?
13:16
<MikeSmith>
because I want to get wider feedback on that doc
13:16
<nessy>
I would have understood a link to the requirements list, which is in good shape - but the checklist is so much still in raw format, I'm not sure input is helpful at this stage...
13:16
<MikeSmith>
we have so far gotten almost zero feedback on it
13:17
<MikeSmith>
we have not gotten much feedback on the requirements either
13:17
<MikeSmith>
and we need to have a sense of urgency about that
13:17
<MikeSmith>
we do not have infinite amounts of time to get implementors to wait for us
13:19
<nessy>
ok, I can see where you're coming from
13:19
<nessy>
I'm just wondering if feedback to the checklist can be useful at this stage
13:19
<nessy>
we've had some edits earlier this week, which I had to remove again because they were solution-specific rather than general technology area
13:21
<jgraham>
nessy: What is the value proposition in not getting feedback?
13:21
<nessy>
it's in an intermediate state - all the feedback at this stage can be only on the requirements realistically, which has its own page
13:22
<nessy>
the whole page will be re-organised by technology still to become actual checklists
13:23
<nessy>
getting feedback on the requirements would be awesome though
13:23
<jgraham>
nessy: It sounds like feedback now is a great idea
13:24
<nessy>
it's not feedback then, but rather input
13:24
<jgraham>
No point in doing a big refactoring of things people don't like
13:24
<jgraham>
Is there a difference?
13:25
<nessy>
what refactoring? there is no refactoring - it's about making checklists that make sense from a technology POV rather than a disability POV
13:26
<nessy>
also, one obvious critique right now is on the priorities - none of which have been discussed or consciously set yet
13:27
<annevk>
well, there are no priorities
13:28
<nessy>
yup, that's another thing that is on the todo for this page still - it's on the agenda
13:28
<nessy>
but anyway - I'm sure the "feedback" will be good input into the process, so go ahead :)
13:40
<zcorpan_>
hsivonen, abarth: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10630
13:41
<hsivonen>
zcorpan_: does that one have known site impact?
13:42
<zcorpan_>
hsivonen: no, not afaik
13:43
<zcorpan_>
we had an old bug about <div><frameset> (with url still working), but that's ok with the current spec
13:46
<annevk>
http://econsultancy.com/uk/blog/6573-why-it-s-time-to-pay-attention-to-html5 -- lol
13:46
<annevk>
"According to numerous sources, the balls were indeed in HTML5, specifically CSS3, part of the standard."
13:47
<zcorpan_>
hsivonen: iirc Refresh works as a real header at least in some browsers
13:47
<hsivonen>
zcorpan_: for which values of some?
13:47
<zcorpan_>
don't remember
13:47
<zcorpan_>
possibly all
13:52
<hsivonen>
annevk: maybe my suggestion for limiting the active formatting element growth could be modified not to affect conforming content
13:53
<hsivonen>
by not removing the formatting elements from the stack when removing them from the list
13:53
<zcorpan_>
or removing only elements that are obsolete :)
13:54
<hsivonen>
zcorpan_: curbing <font> growth is certainly the most important motivation here, but letting e.g. <i> grow insanely for DoS wouldn't be nice
13:55
<zcorpan_>
it wasn't a serious suggestion :)
13:56
<zcorpan_>
with your proposal it's still easy to cause a DoS, just have different attributes on each element
13:56
<zcorpan_>
<font 1><font 2> etc
13:56
<hsivonen>
zcorpan_: good point
13:57
<hsivonen>
I wonder if setting n to 0 and thus removing all duplicates from the list would break the Web
14:03
<hsivonen>
hmm. not removing from stack would required corresponding changes to the AAA
14:04
<hsivonen>
since currently the AAA can't close an element that's not on the list
14:06
<hsivonen>
too bad that simply banning duplicates would break the fancy pages that do nested emphasis and de-italicize the inner one
14:07
<hsivonen>
we could allow two duplicates...
14:07
<hsivonen>
actually, I like that more than picking a permitted length since the marker
15:03
<jgraham>
hsivonen: Like is relative here, right :)
15:04
<jgraham>
I mean the whole thing is a really nasty hack
15:24
zcorpan_
does s/Standards/Acid tests/ on the chrome wiki page
15:34
<hsivonen>
jgraham: I just sent email to public-html. I experimented some more and came up with something that I think works
15:40
<jgraham>
hsivonen: Interesting, but scary
15:40
<jgraham>
Especially for you I would have thought
15:41
<jgraham>
Like I would be tempted to keep the current algorithm for now and experiement with the new one in a more beta release
15:41
<Philip`>
"With this scheme, it's still possible to DoS the HTML5 parser" - does that mean browsers would have to add a second scheme to prevent DoS attacks?
15:42
<Philip`>
in which case wouldn't it be better to start by designing the second scheme, and then only the first scheme as an optimisation if the second one is still poor on some real-world content?
15:42
<hsivonen>
Philip`: it depends. if you look carefully (and you don't need to be that careful), there are already other ways to DoS browsers
15:42
<hsivonen>
it's trivial to crash Gecko remotely, for example
15:43
<Philip`>
Shouldn't the goal be to minimise those cases?
15:43
<hsivonen>
Philip`: we've managed for 12 years without malicious DoS prevention in the parser
15:43
<jgraham>
Arguably a hang is worse than a non-exploitable crash
15:43
<hsivonen>
only prevention for DoS-by-incompetence
15:43
<hsivonen>
Philip`: probably, yeah
15:44
<jgraham>
Since it can suck system resources
15:44
<Philip`>
Having lots of security vulnerabilities sounds like a poor excuse for intentionally not fixing security vulnerabilities
15:45
<Philip`>
Also it's a problem for any other tools that use HTML5 parsers
15:45
<hsivonen>
part of the problem is that DoS countermeasures shouldn't treat the HTML5 spec or bank sites as attacks
15:45
<Philip`>
Not much good trying to argue everyone should replace their XML toolchain parsers with HTML5 parsers if it introduces new DoS attacks that their XML parsers were protected from
15:46
<hsivonen>
Philip`: you are assuming too much
15:46
<hsivonen>
Philip`: it's way easier to crash Gecko via the XML code path
15:46
<hsivonen>
anyway
15:46
<Philip`>
Other applications care more about security
15:47
<hsivonen>
Philip`: here's a concrete problem: you can make the parser exhaust memory by feeding it aa multi-gigabyte attribute value (gzipped so that it explodes on the client)
15:47
<hsivonen>
Philip`: however, for every length limit you might come up with, there's a site somewhere out there that has a non-attack use for an insanely long attribute value that exceeds your limit
15:49
<hsivonen>
Philip`: anyway, I welcome you to design DoS-by-malice prevention for formatting elements
15:52
<jgraham>
I have heard that SVG content with multi-megabyte attributes is not unheard of
15:52
Philip`
should probably try to gather data about how the algorithm runs on some set of pages, rather than guessing what restrictions would be safe
15:52
<Philip`>
but that sounds like it'll take effort :-(
15:53
<hsivonen>
Philip`: I was hoping I could bait you to run an instrumented parser over the dotbot data
15:53
<Philip`>
If I had an instrumented parser .jar that was compatible with the old version I'm using, I could probably run it easily
15:53
<hsivonen>
fwiw, I put an attribute value length limit in Gecko, broke a bank site, and took it out
15:54
<hsivonen>
Philip`: how would you like the parser to output its self-diagnostics?
15:55
<hsivonen>
e.g. the number of iterations in the AAA outer loop or number of iterations in the AAA inner loop?
15:55
<Philip`>
Oh, maybe it's not an old version, it's htmlparser-1.2.1.jar
15:55
<hsivonen>
or the number of duplicate formatting elements on the list?
15:55
<hsivonen>
Philip`: that's *old*
15:55
<Philip`>
It's the latest one on http://about.validator.nu/htmlparser/ :-)
15:56
Philip`
incorrectly assumes "current" and "old" are mutually exclusive
15:58
<Philip`>
hsivonen: Hmm, I have no idea what output data would be helpful for this purpose
15:59
Philip`
has largely forgotten how the algorithm works
15:59
<hsivonen>
I think the helpful output data would be stuff like x% of pages require n iterations or fewer
15:59
<hsivonen>
so presumably at some point x is near hundred while n is low
16:00
<hsivonen>
and then at some point n skyrockets for diminishing returns in x
16:01
<hsivonen>
there are actually three distinct Ns worth measuring: AAA outer loop iterations per entry to the loop
16:01
<hsivonen>
AAA inner loop iterations per entry to the loop
16:02
<hsivonen>
duplicate items after the last marker
16:04
<Philip`>
If the parser can output those numbers somehow, so I can associate them with the URL that's being parsed, then it sounds like that should be sufficient and the output can be processed to get tables of pages vs Ns
16:04
<hsivonen>
Philip`: what's your preferred output mechanism?
16:05
<Philip`>
Um
16:05
<Philip`>
Don't know
16:06
<Philip`>
Currently my code mostly just uses ContentHandler (sometimes LexicalHandler) to collect output
16:06
<Philip`>
It'd probably be ugly to squeeze some Ns into that interface but maybe it'd be easier than alternatives
16:06
<hsivonen>
Philip`: how about I make a one-off handler interface for this? StatHandler or something?
16:07
<Philip`>
I guess that could work too
16:07
<hsivonen>
ok. I'll try to get that done tomorrow-ish. gotta go get some dinner now
16:08
<Philip`>
Alternatively, could just dump it to stdout and I could disable multithreading
16:50
<annevk>
Ms2ger, gsnedders, hmm no zcorpan..., I was thinking of maybe drafting out the Attr proposal from Jonas in the draft
16:50
<annevk>
and maybe even make some of the other suggested changes
16:50
<Ms2ger>
Go for it
16:51
<annevk>
initially I wanted to safe myself editing cycles, but maybe it is worth having a concrete proposal in the draft so people can see all the implications
17:03
<annevk>
heh abort the abort() algorithm
17:03
<annevk>
but I guess that might be needed, indeed
17:09
<hsivonen>
"Allow the author to use a codec which is optimised for voice only, rather than requiring the same codec as the original soundtrack. " categorized as a "must"
17:09
<hsivonen>
there goes the credibility of "must" in those reqs
17:10
<jgraham>
Because it touches on codecs?
17:11
<hsivonen>
jgraham: it makes codec choice into an accessibility requirement on the must level, which seems completely bogus
17:11
<hsivonen>
"Provide a means to prevent descriptions from carrying over from one program or channel when the user switches to a different program or channel. "
17:11
<hsivonen>
channel???
17:12
<hsivonen>
are these copied from a TV-oriented set of reqs?
17:12
<jgraham>
Yeah, that makes no sense
17:12
<annevk>
maybe nessy was right and we should not look at them yet
17:12
<jgraham>
Depends if it is useful to point out that it makes no sense
17:13
<jgraham>
Seems that it should be
17:16
<hsivonen>
relocating within the audion field meas setting the stereo balance?
17:16
<hsivonen>
or doing something more fancy with a surround system?
17:16
<jgraham>
I guess at least stereo
17:16
<jgraham>
But I am just as clueless as you really
17:20
<annevk>
I doubt anything beyond captions will have traction anytime soon
17:20
<annevk>
And even that is not close until we settle structured text vs all-of-HTML
18:26
<annevk>
ooh, TTML became a Proposed Recommendation
18:27
<annevk>
can't wait to (not?) avoid all those discussions
18:35
<TabAtkins>
I wonder what the implementations of it were?
18:36
<jgraham>
gsnedders: Did you put the code for the outliner somewhere? I thought you wanted me to host it?
19:04
<annevk>
so all ECMAScript errors are TypeError?
19:04
<annevk>
jgraham: ?
19:04
<annevk>
it seems so weird
19:45
<annevk>
Ms2ger, congrats on joining the HTML WG
19:46
<MikeSmith>
yay Ms2ger
19:47
<paul_irish>
"Ms-Two-ger -" haha. excellent. :)
19:50
<annevk>
I guess they banned numbers :)
19:58
<MikeSmith>
yeah, I had the same problem … they made me write my name out as Seven-Oh-Nine Seven-Five-Five Six-E-L-Three, Computer File Nine-Three
20:20
<annevk>
http://twitter.com/TVRaman/status/24493208893 :/
20:37
<Ms2ger>
annevk, did you notice "It is not possible to have a type Node?, since interface types already allow the null value."?
20:40
<annevk>
nooo :/
20:41
<annevk>
I wonder what heycam thinks
20:47
<jgraham>
annevk: No?
20:48
<jgraham>
annevk: Why do you think all ECMAScript errors are TypeError?
20:48
<jgraham>
(lots of interesting ones are, but not all)
21:01
<gsnedders>
jgraham: Uh, yeah.
21:01
<gsnedders>
jgraham: It's on my /. :P
21:01
<jgraham>
You have a slashdot?
21:02
<gsnedders>
Smartass.
21:03
TabAtkins
isn't sure how that's "being a smartass", since it's what gsnedders actually said.
21:03
gsnedders
sighs
21:03
<gsnedders>
This channel is full of geeks.
21:04
TabAtkins
is still confused. ;_;
21:06
<TabAtkins>
Oh, I get it now. It's on your /, followed by a period. Damn you, slashdot.
21:07
<Philip`>
He has a slashcomma?
21:07
<TabAtkins>
Yup. Typo on gsnedders' part.
21:08
<jgraham>
http://www.krakenbenchmark.com/ -- somewhere in the basement of a Mozilla office the old toaster that they appear to be hosting this on just caught fire
21:12
gsnedders
is hiding from flatmates playing drinking game
21:12
<gsnedders>
*games
21:12
<TabAtkins>
Dude. There is this word. It is called "No". (Or "No thank you", if you want to be polite.)
21:13
<aho>
http://www.w3.org/TR/2010/PR-ttaf1-dfxp-20100914/ <- meh. me likes websrt a lot better
21:13
TabAtkins
has a bunch of alcoholic friends, and successfully uses this phrase all the time.
21:14
<gsnedders>
TabAtkins: I could do that… again. I'm somewhat tired of doing that every day though.
21:14
<TabAtkins>
gsnedders: Shrug. A lot of people are alcoholics in college. You'll just have to deal.
21:14
<gsnedders>
TabAtkins: Hey, why do you think I was so apprehensive about this?
21:14
<gsnedders>
:)
21:15
<TabAtkins>
gsnedders: But hiding means they wont' think of you when they're doing *non* drinking-related things, or things where drinking is onlyl an incidental part.
21:15
<gsnedders>
TabAtkins: The flatmates that are doing it, well, I don't expect to particuarly spend much time with them anyway
21:16
<gsnedders>
TabAtkins: And not joining occasionally isn't really going to cause that
21:16
<TabAtkins>
gsnedders: Whatever floats your boat. I found in college that I had a lot of fun hanging out with people even if their standard idea of fun is getting blasted until they puke.
21:16
<TabAtkins>
(I didn't hang with them while they were out binge-drinking, is all.)
21:17
<gsnedders>
TabAtkins: My flatmates aren't really people I have much in common with at all, though. Maybe two of the eleven others in the flat I might actually become friends with.
21:17
<TabAtkins>
Ah. I had the benefit of my roommate being one of my best friends from high school.
21:18
<jgraham>
There is a certian tension between wanting to hang out with people enough that you make friends, and avoiding the people that you don't get on with
21:19
<TabAtkins>
Excellent phrased, jgraham. I find that it's often useful to me to swing in the direction of "more hangouts", but I've also trained myself to be very extroverted.
21:37
<aho>
jgraham, that kraken thing looks pretty dead to me :>
21:55
<erlehmann>
jgraham, can you explain that tension? i see none of it, i just avoid people i don't like.
21:56
<TabAtkins>
erlehmann: There's a difference between "people you don't like" and "people you don't immediately get along with, but might be fun to hang out with once you get to know them".
21:59
<erlehmann>
TabAtkins, for most people, I am of the latter kind, hehe
22:04
<variable>
http://pastebin.com/9DP7dLBe
22:04
<variable>
is that correct ?
22:06
<variable>
that is a reply to someone on the -help mailing list
22:16
<jgraham>
erlehmann: The problem is that in a situation where most people are in the pool of unknowns, it is hard to avoid all the people you don't like without avoiding many people you don't know but potentially would like
22:17
<variable>
jgraham, I find that the people I want to avoid tend to hang together
22:17
<variable>
and the people I want to get to know usually seperate from them
22:17
<variable>
at somepoint
22:17
<jgraham>
variable: Yeah, eventually by the time the whole system has stabilised
22:17
<TabAtkins>
That said, the benefits and downsides change somewhat based on how intro/extroverted you are. If you've trained yourself in politely disengaging and avoiding people you find you hate, it's a lot easier to experiment with groups.
22:18
<jgraham>
But by that point you can already be classed as an outsider even by people that you would get on with if you met them
22:19
<variable>
jgraham, any advice for dealing with that then? I'm at the start of the the whole "finding people I like" period now ;-)
22:19
<variable>
also --> could someone verify that this is correct http://pastebin.com/9DP7dLBe
22:20
<jgraham>
variable: Not really. I think my university experience was rather atypical
22:20
<TabAtkins>
variable: Push yourself into social situations as much as possible. Consciously focus on learning from it, so that the uncomfortable/painful situations you'll find yourself in actually serve a purpose in training you to deal with or avoid them in the future.
22:20
<jgraham>
since the social setup at Cambridge is somewhat unique
22:20
TabAtkins
supports approaching social interaction analytically until you've trained up a knack for it.
22:21
<jgraham>
(well it varies a bit per college and so on, and I guess Oxford might be similar)
22:21
<jgraham>
And also I can be painfully shy and very bad at doing what TabAtkins just suggested
22:22
<variable>
TabAtkins, I'll try doing that. Unfortunately my social abilites are a bit low at the moment
22:22
<gsnedders>
My biggest problem is just shyness and talking to people in the first case; if I have someone I know around I can use them to introduce me which I'm fine with
22:22
<jgraham>
+therefore
22:22
<variable>
I'm not shy - but I tend to say/do stupid things - either that or I think the smallest mistake I make is humongous and everyone notices
22:22
<TabAtkins>
jgraham: The painful shyness is (usually) a symptom of insufficient experience in the first place. It's an unfortunate fact that you have to be painful uncomfortable in order to overcome being painfully uncomfortable.
22:23
<TabAtkins>
gsnedders: Yeah, I still have that problem sometimes. I'm trying to learn to fix it using the techniques here: http://lesswrong.com/lw/2co/how_to_always_have_interesting_conversations/
22:24
<jgraham>
TabAtkins: I don't think that is quite the case. I mean I don't seem to have ended up a social outcast or anything
22:24
<TabAtkins>
I know that this works in general, because when I find someone who happens to trigger a box in my unconsciously-designed map I can have great convos.
22:24
<gsnedders>
jgraham: What, with all your friends running away from you? :P
22:25
<TabAtkins>
jgraham: I can only really speak from my own experience. I was *ridiculously* shy and withdrawn in grade school, but consciously changed myself into an extrovert.
22:25
<TabAtkins>
variable: Yeah, that paste looks accurate.
22:25
<variable>
"One of the things that makes Michael Vassar an interesting person to be around is that he has an opinion about everything" - people tell me thats a BAD thing
22:26
<TabAtkins>
Having an opinion is a good thing. Having a strong opinion that you push on people, or that you offer up unasked for, is not.
22:26
<jgraham>
I am assuming that isn't being used to mean "is opinionated"
22:26
<TabAtkins>
Having an opinion that you can express in conversation that moves into the topic area is great.
22:26
<jgraham>
I assume it means something like "is prepared to offer interesting thoughts on"
22:27
<TabAtkins>
Yeah, that's right.
22:29
<variable>
TabAtkins, and flow content would be elements that affect the flow of the document ? is there a better way to phrase that?
22:29
variable
finishes the article
22:29
romeo_
can't imagine TabAtkins as "shy and withdrawn"
22:29
<TabAtkins>
Flow content is sorta just "everything else", right? Or everything that isn't one of the "non-rendering" things.
22:29
<TabAtkins>
romeo_: Have you met me somewhere?
22:29
<romeo_>
no
22:29
<romeo_>
only here
22:30
<TabAtkins>
Ah. Was wondering if you'd seen me give a talk or something. ^_^
22:30
gsnedders
can imagine TabAtkins not being the most outgoing person
22:31
<TabAtkins>
But yeah, I'm a substantially different person socially than I was a decade ago, mostly because of conscious effort to change myself.
22:31
<TabAtkins>
gsnedders: You met me personally, though, where I went out of my way to introduce myself and then took you out for ice cream.
22:32
<variable>
TabAtkins, part of the problem is that I find most chit-chat type topics (weather, most jobs, blah) boring
22:32
<jgraham>
variable: I assume that the idea is to work out ways to flow to topics that you find interesting from ones you find boring
22:32
<jgraham>
And hope there is mutual interest I guess
22:32
<TabAtkins>
variable: Two ways to combat that. (1) Train yourself to think the opposite, or at least be able to project the image of interest. It goes a long way. (2) Using conversation maps or similar techniques, learn how to quickly transition a conversation from the boring chit-chat to more interesting subjects.
22:33
<TabAtkins>
One good thing is to learn how to ask personal questions of the person who's being boring. People are a lot more interesting when they're talking about themselves, I find.
22:35
<gsnedders>
TabAtkins: There again, it was in a context where everyone already knew everyone to some levle
22:35
<jgraham>
And you could always discuss marin collapsing if you ran out of other topics ;)
22:36
<jgraham>
*margin
22:36
<TabAtkins>
gsnedders: It honestly wouldn't have mattered much to me. Remember that when I first introduced myself to you guys it was kind of awkward. That's just how it goes sometimes; I just hung out for a bit and then politely excused myself so I could try again later. I successfully talked with you guys later in the bar.
22:38
<variable>
I don't mind forced social situations much
22:38
<variable>
(like my roommate was random and we like each other)
22:38
<variable>
but I find it hard to meet *new* people also
22:38
<gsnedders>
TabAtkins: I would have been a lot more awkward in the first case otherwise
22:39
<jgraham>
TabAtkins: I don't really remember that but it is quite distressing to dissect old social situations
22:39
gsnedders
can't remember the specifics either
22:40
<TabAtkins>
gsnedders: Otherwise what? If I didn't already know you somewhat? If that was the case, I could have at least gone into the suite of job-related questions. I already know what you do, though.
22:40
<variable>
if I go over social situations I always thing I screwed up badly
22:41
<gsnedders>
TabAtkins: I basically wouldn't know what to say, at all
22:42
<jgraham>
Anyway, there was some original point to this
22:42
<TabAtkins>
variable: Nothing wrong with that, as long as you're analyzing it for places where you could have done better!
22:42
<jgraham>
Which I think was that you want to be sociable enough that you meet people you like
22:42
<jgraham>
But not so socialble that you do things that make you unhappy
22:43
<jgraham>
TabAtkins: I'm not sure I agree with that, necessarily. People generally can't manage clean emotional detachment
22:43
<variable>
jgraham, s/generally//
22:43
<jgraham>
So going over stuff in your head doesn't lead to good analysis
22:44
<variable>
I used to think I could - but over time I learned no one could
22:44
<TabAtkins>
jgraham: In reference to what? Emotionally detaching themselves from the memories of their interaction, so they can study it analytically?
22:45
<gsnedders>
It's so easy to just get dragged down into over-analyizing everything
22:46
variable
has to leave now
22:46
<variable>
thanks TabAtkins
22:46
<jgraham>
TabAtkins: For example
22:46
<TabAtkins>
True. You have to teach yourself how to not do that, as well. ^_^ There's a whole lot of generally just learning to recognize and account for emotional imprints in your actions and memories.
22:47
<jgraham>
Also, in the specific case of gsnedders, he has a tendency to over-think things at the best of times, which I'm not sure is always good :)
22:47
<TabAtkins>
He needs a social coach!
22:47
<gsnedders>
jgraham: It's definitely not good. :)
22:48
<gsnedders>
jgraham: I'm a lot better about that than I used to be, though.
22:48
<hober>
TabAtkins: isn't that what #whatwg is?
22:48
<TabAtkins>
(Also, he needs to read lesswrong.com, which has several posts about social interaction in terms of geeky near-aspies.)
22:48
<hober>
lesswrong++
22:52
<jgraham>
Isn't getting social skills advice from IRC practically the definition of irony?
22:53
<jgraham>
I just need to work out how to draw venn diagrams to illustrate it
22:53
<aho>
inkscape :>
22:54
<jgraham>
aho: On IRC?
22:54
<jgraham>
I meant ascii art
22:55
<aho>
ah
22:55
<jgraham>
:)
22:56
<gsnedders>
And then for the past year I've got mocked a fair bit for my behaviour with two of my best friends…
22:56
gsnedders
glares at jgraham (in part)
22:57
<aho>
krakenbenchmark works again, by the way
22:57
<aho>
looks like they moved it over to another server
22:57
jgraham
has no idea what gsnedders is glaring at
22:58
<aho>
http://blog.mozilla.com/rob-sayre/2010/09/14/release-the-kraken/
22:58
<aho>
some blurp over there