| 00:23 | <jamesr_> | well html 5.1 is technically a bigger number than html 5, so it must be better |
| 00:23 | <jamesr_> | by about 2% |
| 00:30 | <Hixie> | you have to wonder why the w3c expect anyone to respect their process when they themselves violate it so brazenly |
| 00:31 | <Hixie> | (and with such a high-profile spec, too) |
| 00:33 | <zewt> | i don't know anything about the contracts, but wouldn't violating process put the patent policy at risk? (and the patent policy is the only reason anyone pretends to care abuot the w3c anymore) |
| 00:34 | <zewt> | (or even about) |
| 00:34 | <TabAtkins> | I keep getting told that the patent policy relies, at least somewhat, on the process being followed, so maybe? |
| 00:34 | <Hixie> | i doubt it, given how widely they violate it |
| 00:34 | <smaug____> | rafaelw__: ping |
| 00:35 | <smaug____> | or anyone from webkit land |
| 00:35 | <smaug____> | https://trac.webkit.org/browser/trunk/Source/WebCore/dom/MutationCallback.idl#L34 |
| 00:35 | <smaug____> | does that mean { handleEvent() {} } is supported as callback |
| 00:36 | <smaug____> | ( bool? why does it return bool ) |
| 00:46 | <smaug____> | the context is https://www.w3.org/Bugs/Public/show_bug.cgi?id=15695 |
| 01:16 | <Yuhong> | On HTML5 CR, already posted this: http://slashdot.org/comments.pl?sid=3322379&cid=42320593 |
| 03:00 | <Hixie> | anyone got a link to the public-html post where the wg chairs said that the web had already proved interoperability with things like the navigate algorithm so it didn't need testing? |
| 03:09 | <zewt> | are you putting together a collection of best hits? |
| 05:18 | <cabanier> | if a message to whatwg bounces because it is too larger, should I resent it or will it go through later? |
| 05:19 | <cabanier> | "Your mail to 'whatwg' with the subject |
| 05:19 | <cabanier> | Re: [whatwg] Canvas-related feedback |
| 05:19 | <cabanier> | Is being held until the list moderator can review it for approval. |
| 05:19 | <cabanier> | The reason it is being held: |
| 05:19 | <cabanier> | Message body is too big: 62553 bytes with a limit of 40 KB" |
| 05:19 | <cabanier> | I guess the mail thread is too large :-) |
| 05:25 | <heycam> | or you should be trimming your quotes! |
| 05:25 | <heycam> | :) |
| 05:26 | <cabanier> | I usually just reply in-line |
| 05:26 | <cabanier> | It was a monster email that hixie sent earlier. It's also not on the archive |
| 05:43 | <cabanier> | I guess I'll wait until tomorrow... |
| 06:58 | <MikeSmith> | Hixie: about https://www.w3.org/Bugs/Public/show_bug.cgi?id=20319 |
| 06:58 | <MikeSmith> | the AAA parsing bug |
| 06:59 | <MikeSmith> | what should the expected DOM for <b><i><a><s><tt><div></b>first</b></div></tt></s></a>second</i> be? |
| 06:59 | <MikeSmith> | or is that actually you're asking in the related whatwg thread? |
| 07:01 | <MikeSmith> | when you asked if anybody had a preference for how it should be fixed |
| 07:03 | <Hixie> | not sure, but for sure the text node that says "first" should come before the text node that says "second" |
| 07:03 | <Hixie> | cabanier: trim your quotes |
| 07:04 | <Hixie> | cabanier: unless you literally replied to everything in the e-mail, but that seems unlikely :-) |
| 07:04 | <cabanier> | Hixie: OK. I will resend it tomorrow |
| 07:05 | <cabanier> | Hixie: no, I didn't reply to everything :-D |
| 07:14 | <MikeSmith> | Hixie: so if for now I hack a current parser to remove the limit on the inner loop and then check to see what DOM that produces, that's probably what we should end up with, right? |
| 07:14 | <MikeSmith> | I mean regardless of the specific way you end up fixing it in the spec |
| 07:15 | <MikeSmith> | I'm writing a test case and just need to know what expected results to put in the test case |
| 07:58 | <zcorpan> | Hixie: r7589: + the top-left corner of this rectangle will be to the right and/or above the (<var |
| 07:58 | <zcorpan> | Hixie: you sure "right and/or above" is correct? |
| 07:59 | <Ms2ger> | No, "and/or" is always wrong :) |
| 07:59 | <zcorpan> | Ms2ger: why? |
| 07:59 | <Ms2ger> | It just means "or" |
| 08:01 | <zcorpan> | http://en.wikipedia.org/wiki/And/or |
| 08:04 | <zcorpan> | ...though i can see that it should be avoided in specs for similar reasons it should be avoided in Wikipedia |
| 08:14 | <MikeSmith> | so, about the adoption-agency spec bug that causes text nodes to be misordered, the limit on the inner loop is the part that states, "If inner loop counter is greater than or equal to three, then go to the next step in the overall algorithm.", right? |
| 08:14 | <MikeSmith> | in http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html#adoptionAgency |
| 08:18 | <MikeSmith> | and the part that corresponds to in the Gecko parser code is http://hg.mozilla.org/mozilla-central/file/2e70b718903a/parser/html/nsHtml5TreeBuilder.cpp#l3405 |
| 09:11 | <zcorpan> | http://www.w3.org/mid/73AC3CEAEF48B3479D4671AE58094B03011B28C6⊙uPC - www-dom is not the right mailing list for this type of question, but what is the right mailing list? |
| 09:11 | <zcorpan> | help⊙wo? |
| 09:16 | <MikeSmith> | zcorpan: wasn't clear to me what source she was citing as far as the 'listed as W3C Standard = "No"' part |
| 09:16 | <MikeSmith> | I assumed MDN |
| 09:16 | <zcorpan> | MikeSmith: w3schools |
| 09:16 | <MikeSmith> | what treebuilder does html5lib use by default? |
| 09:16 | <MikeSmith> | zcorpan: ah |
| 09:17 | <jgraham> | MikeSmith: A built in one that is crappy |
| 09:17 | <MikeSmith> | zcorpan: so help⊙wo would definitely be a good place, I think |
| 09:18 | <MikeSmith> | jgraham: so to put it another way, what file in html5lib/treebuilders do I need to hack if I want to make a treebuilder change? |
| 09:19 | <MikeSmith> | or maybe I should feed it whatever switch to just tell it to use a better one |
| 09:19 | <jgraham> | We obviosuly need help-I-got-scammed-by-w3schools⊙wo |
| 09:19 | <MikeSmith> | then hack on the code for that other one |
| 09:19 | <jgraham> | MikeSmith: What are you trying to achieve? |
| 09:20 | <MikeSmith> | I want to change the code to not have the "If inner loop counter is greater than or equal to three, then go to the next step in the overall algorithm." |
| 09:20 | <MikeSmith> | to ignore that part of the spec |
| 09:20 | <MikeSmith> | so that there's no limit |
| 09:21 | <MikeSmith> | ah simpleTree |
| 09:21 | <zcorpan> | change the limit to +Inf |
| 09:23 | <darobin> | MikeSmith: I don't have the context for your problem, but re picking a different treebuilder, you can html5lib.html5parser.HTMLParser(tree = html5lib.treebuilders.getTreeBuilder('lxml')) |
| 09:23 | <jgraham> | MikeSmith: That's not specific to a treebuilder |
| 09:23 | <jgraham> | That's part of the general implementation |
| 09:23 | <MikeSmith> | darobin: ok |
| 09:24 | <MikeSmith> | jgraham: yeah, I'm seeing that now |
| 09:24 | <MikeSmith> | will explore furthere |
| 09:24 | <zcorpan> | http://code.google.com/p/html5lib/source/browse/python/html5lib/treebuilders/_base.py#110 ? |
| 09:25 | <jgraham> | http://code.google.com/p/html5lib/source/browse/python/html5lib/html5parser.py#1499 |
| 09:25 | <MikeSmith> | didn't look there but I think |
| 09:25 | <MikeSmith> | jgraham: yeah there |
| 09:26 | <jgraham> | zcorpan's line implement's Noah's Ark iirc |
| 09:26 | <zcorpan> | ah |
| 09:26 | <MikeSmith> | ok that did the trick |
| 09:27 | <MikeSmith> | so for the record, without the depth limit, <b><i><a><s><tt><div></b>first</b></div></tt></s></a>second</i> just becomes <b><i><a><s><tt></tt></s></a></i></b><i><a><s><tt><div><b></b>first</div></tt></s></a>second</i> |
| 09:33 | <Stevef_> | darobin: any thoughts on HTML5 CR publication violating W3C process? seen a few comments on it |
| 09:34 | <Ms2ger> | "Eh, process" |
| 09:43 | <darobin> | Stevef_: is *shrug* a thought? |
| 09:44 | <Stevef_> | darobin: sure |
| 09:45 | <darobin> | Stevef_: I've never been a process literalist, when chair I always told my groups that the only parts that truly matter are those that enforce RF |
| 09:46 | <MikeSmith> | .me finds equivalent WebKit parser bits in https://github.com/WebKit/webkit/blob/master/Source/WebCore/html/parser/HTMLTreeBuilder.cpp#L1519 and https://github.com/WebKit/webkit/blob/master/Source/WebCore/html/parser/HTMLTreeBuilder.cpp#L1562 |
| 09:46 | <nimbu> | guize does this have precedence in standards? http://trac.webkit.org/changeset/136744 |
| 09:46 | <nimbu> | MikeSmith: ^ |
| 09:47 | <Stevef_> | darobin: onlt wondered as was unclear whether the concerns are meaningful or process trolling |
| 09:47 | <darobin> | Stevef_: as far as I'm concerned if it doesn't affect RF it's not meaningful |
| 09:47 | <MikeSmith> | nimbu: I read the words but I don't understand what that change is doing. Is it for bad or for good? |
| 09:48 | <darobin> | it might not be trolling, but it's not a very useful position either |
| 09:48 | <nimbu> | MikeSmith: it sez pseudo elements are now in DOM |
| 09:48 | <nimbu> | it makes me worry its bad. |
| 09:48 | <nimbu> | although I have no rational reason for my stress |
| 09:49 | <MikeSmith> | if it's bad for interop then I think it's bad |
| 09:49 | <Stevef_> | darobin: back to real work then... I have some further thoughts on how to resolve alt text impasse will share with the class when I get a chance |
| 09:49 | <nimbu> | MikeSmith: i dont think any other browser does this. |
| 09:49 | <darobin> | Stevef_: exactly! some people complain that CR has bugs, others complain that it's not shipping fast enough — me, I just want to work on stuff |
| 09:50 | <nimbu> | beverloo: beverloo-: plz explain http://trac.webkit.org/changeset/136744 |
| 09:50 | <nimbu> | (on email if I am not online beverloo beverloo- |
| 09:50 | <darobin> | Stevef_: please share as soon as you have a chance! |
| 09:50 | <Stevef_> | btw: thanks for the thumbs up for <main> in your post, appreciated |
| 09:50 | <MikeSmith> | nimbu: it's not clear to me that it gets exposed to Web content or whether it's just an internal implementation design choice. But on the face of it does seem like it would be exposed |
| 09:50 | <darobin> | Stevef_: hey, no need to thank me, it just happens to be what I think |
| 09:51 | <nimbu> | MikeSmith: oic. i hope not. |
| 09:51 | <darobin> | you can thank Bruce for reminding me I'd actually written about the bar for inclusion of semantic elements before :) |
| 09:51 | <Steve^> | Hi, I'm a little confused by the phrasing of "Except where otherwise specified, the alt attribute must be specified and its value must not be empty" |
| 09:51 | <darobin> | Steve^: please meet Stevef_ |
| 09:52 | <darobin> | (and Moo is very cool btw) |
| 09:52 | <Steve^> | It is valid for an alt attribute to be empty? The examples suggest so, but the wording of that sentence immediately makes me feel not |
| 09:52 | <Moo^_^> | darobin: what? |
| 09:52 | <Stevef_> | darobin: i realise that but as we say in in the HTML WG "silence = assent, but positive responses encouraged" or some such :-) |
| 09:52 | <Moo^_^> | thank you |
| 09:52 | <darobin> | Stevef_: hehehe |
| 09:53 | <darobin> | Moo^_^: lol, sorry, I was referring to "~stephen⊙omc" <-- this Moo |
| 09:53 | <jgraham> | nimbu: Without knowing anything about how WebKit works I would bet money that these are "hidden" DOM nodes, so that DOM methods skip over them |
| 09:53 | <darobin> | but hey, I'm pretty damn sure you're very cool too |
| 09:53 | <Stevef_> | Steve^: it is valid for it to be empty alt="" under certain circumstances this explains when in detail: http://dev.w3.org/html5/alt-techniques/#secm3 |
| 09:54 | <Steve^> | Stevef_, but it must always be specified? |
| 09:55 | <jgraham> | nimbu: Yes, look at the diff in Node.cpp |
| 09:55 | <nimbu> | jgraham: ah k. thanks. |
| 09:55 | <nimbu> | jgraham: so this is just an implementation thing. |
| 09:56 | <Stevef_> | Steve^: depends on which spec you prefer W3C HTML5 says it must always be specified unless the image is a child of a figure element with a non empty figcaption, WHATWG HTML says otherwise |
| 09:57 | <MikeSmith> | ok for the AAA bug hacking the WebKit parser to ignore the limit results as expected in the same DOM as I got from hacking html5lib. Still trying to figure out where in the Gecko parser code to touch |
| 09:57 | <jgraham> | nimbu: I am pretty sure it is. But eseidel hangs out here sometimes I think |
| 09:58 | <Stevef_> | Steve^: so you can choose you brand, its a lifestyle choice |
| 10:00 | <nimbu> | jgraham: k thank you! |
| 10:02 | <MikeSmith> | http://hg.mozilla.org/mozilla-central/file/2e70b718903a/parser/html/nsHtml5TreeBuilder.cpp#l3284 |
| 10:02 | <MikeSmith> | that file seems to have an aversion to comments |
| 10:03 | <Ms2ger> | Might be that the code translator removes comments? |
| 10:03 | <MikeSmith> | nimbu: also esprehn is around on #webkit during west-cooast hours |
| 10:03 | <MikeSmith> | or some hours |
| 10:04 | <MikeSmith> | Ms2ger: yeah I had the same thought. Looking at the Java sources now |
| 10:05 | <Ms2ger> | Not much better |
| 10:05 | <Stevef_> | thanks go to hixie for changing Bruce lawsons mind about <main> http://www.brucelawson.co.uk/2012/why-changed-mind-about-main-element/ ;-) |
| 10:08 | <Steve^> | Stevef_, I imagine the solution for the former is to use CSS for decorational images instead? |
| 10:09 | <Stevef_> | Steve^: thats one solution yes |
| 10:10 | <MikeSmith> | Ms2ger: yeah, just looked at http://hg.mozilla.org/projects/htmlparser/file/cdb5527b1855/src/nu/validator/htmlparser/impl/TreeBuilder.java#l4373 |
| 10:10 | <Steve^> | Stevef_, I think in the 10 minutes I was away from my desk I forgot what question I asked.. is the distinction between the two specs the set/not set of the alt attribute, or the empty/filled of the attribute? |
| 10:10 | <MikeSmith> | Ms2ger: Henri's not super fond of comments |
| 10:12 | <Ms2ger> | So it appears |
| 10:12 | <Ms2ger> | darobin, so, any ideas on how to shout down Kris? ;) |
| 10:12 | <jgraham> | "la la la, I can't hear you"? |
| 10:13 | <MikeSmith> | anyway, after hacking in the right place, Gecko parser as expected also producing same result for that unlimited-depth AAA case |
| 10:13 | <darobin> | Ms2ger: well, if we're all agreed on what we want, maybe we can avoid shouting :) |
| 10:14 | <Stevef_> | Steve^: one of the differences between the 2 specs is that WHATWG spec makes it conforming to use the title attribute when no alt or empty alt is present so you can do this <img title="poot">, you can also do this <img alt="" title="poot"> |
| 10:14 | <darobin> | the chair's role is to declare consensus; if everyone but the chair agrees on something then that's the consensus the chair agrees to |
| 10:14 | <darobin> | if that doesn't work, well... we have a problem |
| 10:16 | <jgraham> | Maybe we can threaten to chop up the chair for firewood |
| 10:17 | <MikeSmith> | briar patch |
| 10:20 | <Workshiva> | Is it legit to have <time datetime="something real"></time> to produce metadata without rendering anything? |
| 10:22 | <MikeSmith> | Workshiva: yeah |
| 10:22 | <MikeSmith> | it's valid at least |
| 10:23 | <Workshiva> | It feels icky |
| 10:23 | <MikeSmith> | well I think the whole <time> element is icky and I wish it didn't exist |
| 10:24 | <MikeSmith> | that example is minor ickiness compared to the grand baroque ickiness that element overall achieves |
| 10:27 | <Workshiva> | I don't see any grand baroque ickiness with the element in general, but maybe it requires prolonged exposure |
| 10:29 | <MikeSmith> | heh |
| 10:29 | <MikeSmith> | yeah that could be it |
| 10:42 | <darobin> | that works for pretty much any element, though |
| 10:50 | <annevk_> | MikeSmith: they wouldn't expose it in the DOM |
| 10:50 | <annevk> | MikeSmith: it can be more convenient to implement it that way, that's all |
| 10:53 | <annevk> | darobin: "work on stuff" is kinda vague, but I assume that means copy & paste? ;) |
| 10:53 | <MikeSmith> | annevk: you mean the WebKit change that Divya mentioned? |
| 10:53 | <annevk> | MikeSmith: yeah |
| 10:53 | <MikeSmith> | ah yeah |
| 10:53 | <MikeSmith> | ok |
| 10:54 | <darobin> | annevk: are you kidding? that's way too much work |
| 10:54 | <annevk> | you just create some special node that normal traversal does not go through |
| 10:54 | <darobin> | I write tools that do that automatically |
| 10:54 | <MikeSmith> | annevk: I see |
| 10:55 | <annevk> | I assume that's the way they've done it, haven't actually looked at the patch |
| 10:55 | <MikeSmith> | makes sense |
| 11:02 | <Ms2ger> | darobin, congratulations on your meaningless milestone, btw |
| 11:02 | <darobin> | Ms2ger: I live to please you |
| 11:03 | <Ms2ger> | Oh, in that case... |
| 11:03 | <Ms2ger> | Let's keep tests in hg |
| 11:03 | <darobin> | sadly, you got your quota this year |
| 11:03 | <Ms2ger> | Dammit |
| 11:04 | <annevk> | hard to stop the git train, way more likely to get crushed |
| 11:08 | <Ms2ger> | Mm, a chaotic strange Magi attractor around the North Pole |
| 11:09 | <darobin> | well, if hg is an option we could also just share an NTFS mount somewhere |
| 11:09 | Ms2ger | pats darobin on the back |
| 11:09 | <Ms2ger> | Oh, I was holding a dagger? Sorry about that |
| 11:10 | <darobin> | it tickles |
| 11:10 | <Ms2ger> | You must be used to getting stabbed in the back by git |
| 11:11 | <jgraham> | Now you have lost me |
| 11:11 | <jgraham> | Are you representing git in this parable? |
| 11:12 | <Ms2ger> | Git, like myself, is quite violent to its users, is the point |
| 11:13 | <jgraham> | You have users? |
| 11:13 | <MikeSmith> | and also git is really oblique and hard to understand when it speaks metaphorically, like Ms2ger |
| 11:14 | <annevk> | just download GitHub.app and live in ignorance :) |
| 11:14 | <Ms2ger> | MikeSmith, :) |
| 11:16 | <darobin> | I think I need to make "it’s in the gnostic gospels somewhere" part of my top go-to sentences |
| 11:16 | <Ms2ger> | darobin++ |
| 11:35 | <rizlah> | Why isn't the HTML5 standard released in pdf ? |
| 11:35 | <jgraham> | Because we don't have a sufficiently finely developed sense of irony. |
| 11:38 | <zcorpan> | it was at some point but it was disabled because it took too much resources of the server to generate, or some such |
| 11:38 | <zcorpan> | i recall someone being interested in taking over that part, but dunno if anything came of it |
| 11:39 | <jgraham> | That was never true of the W3C copy though, was it? |
| 11:39 | <rizlah> | But the final has been released, so I guess you only have to generate it once now. |
| 11:40 | <jgraham> | No, that is a misconception from several points of view |
| 11:40 | <jgraham> | What the W3C has released is a CR |
| 11:41 | <jgraham> | Which will continue to get bugfixes over the coming years |
| 11:41 | <jgraham> | What the world uses to develop web browsers is a living standard, which gets (mostly) the same bugfixes plus extra bug fixes, plus new features on a daily basis |
| 11:42 | <rizlah> | I see |
| 11:42 | <jgraham> | The CR copy is almost the worst document to look at |
| 11:42 | <rizlah> | So I should look at the TR? |
| 11:43 | <Ms2ger> | No |
| 11:43 | <Ms2ger> | The LS |
| 11:43 | <jgraham> | You should look at http://html.spec.whatwg.org |
| 11:43 | <jgraham> | Oh |
| 11:43 | <jgraham> | Unless you are a lawyer |
| 11:43 | <jgraham> | In which case please feel free to look at the CR |
| 11:44 | <rizlah> | http://www.whatwg.org/specs/web-apps/current-work/multipage/ |
| 11:44 | <SimonSapin> | I’m getting a 404 on http://html.spec.whatwg.org/images/logo |
| 11:44 | <SimonSapin> | used on http://html.spec.whatwg.org/ |
| 11:44 | <jgraham> | SimonSapin: Me too |
| 11:45 | <jgraham> | I wonder if it moved to resources.whatwg.org or whatever |
| 11:45 | <Ms2ger> | Mm |
| 11:46 | <Ms2ger> | The HTML spec expects to load from http://www.whatwg.org/ |
| 11:46 | <Ms2ger> | And http://www.whatwg.org/images/logo is fine |
| 11:46 | <darobin> | rizlah: that said, if you insist on getting a PDF version, you can normally append ",pdf" to any URL in W3C-space and get the PDF version |
| 11:46 | <darobin> | I say normally because right now it seems broken |
| 11:47 | <darobin> | I'm also not sure how long it would take to process the single page spec, that would be a nice test of Prince |
| 11:48 | jgraham | does find it strange that it is all the same people that object to the W3C process as heavyweight that object when it isn't precisely followed |
| 11:49 | <jgraham> | Although of course presenting cases of the Process not being followed as evidence that the Process needs to change is fine |
| 11:51 | <Ms2ger> | It also seems to be the people who block changes to the Process who are best at ignoring it |
| 11:54 | <annevk> | html.spec is not really ready yet |
| 11:54 | <annevk> | use whatwg.org/html |
| 11:54 | <Ms2ger> | Or fix it, I guess |
| 11:55 | <darobin> | jgraham: I think that was the basis for http://w3cmemes.tumblr.com/post/34823664715/it-seems-that-the-people-who-most-enjoy |
| 11:55 | <annevk> | jgraham: I think the complaint is that the Process is artificially enforced |
| 11:56 | <annevk> | jgraham: It's followed whenever it suits the gatekeepers and ignored whenever it doesn't |
| 11:56 | <annevk> | jgraham: And that's frustrating |
| 11:56 | <Ms2ger> | And perhaps that things that aren't actually in the process are enforced as if they were |
| 11:56 | <jgraham> | annevk: I don't understand. What does it mean for something to be "artificially" enforced? |
| 11:56 | <annevk> | jgraham: maybe I'm using the wrong English word |
| 11:56 | <Ms2ger> | jgraham, inconsistently? |
| 11:56 | <jgraham> | That would make more sense |
| 11:57 | <jgraham> | Anyway, I don't exactly love the Process |
| 11:57 | <darobin> | well, there's a problem with complaining about "inconsistently" |
| 11:57 | <darobin> | I don't either |
| 11:57 | <annevk> | One of the meanings of artificial is "Not genuine" |
| 11:57 | <annevk> | which is kinda what I meant, but maybe it cannot be used in that way |
| 11:57 | <darobin> | you don't want a process that's enforced slavishly anymore than you want to replace judges by robots |
| 11:58 | <darobin> | as chair, I've only ever used process when a) RF was involved, or b) there was a serious problem |
| 11:58 | <darobin> | (almost no b) |
| 11:58 | <jgraham> | But I don't think that kicking up a fuss every time that something happens that would be OK per some ideal process but not OK per the letter of the current Process is a good way to convince people that the Process is broken |
| 11:58 | <darobin> | yeah, it won't convince anyone |
| 11:58 | <jgraham> | It does seem like a good way to get a reputation for being whiny |
| 11:59 | <darobin> | the process could use reform, but a literalist reading won't convince anyone |
| 11:59 | <annevk> | I don't really think anyone is kicking up a fuss |
| 11:59 | <annevk> | At least I haven't seen any |
| 11:59 | <Ms2ger> | Well, an ideal process wouldn't have CR at an arbitrary point |
| 11:59 | <annevk> | Just a couple of irony remarks on IRC |
| 11:59 | <jgraham> | TabAtkins was bitching on twitter, for example |
| 12:00 | <Ms2ger> | Would your ideal process involve labeling something as "final" with a hundred open bugs? |
| 12:00 | <jgraham> | My ideal process wouldn't label things final |
| 12:00 | <jgraham> | So, uh, mu? |
| 12:01 | <annevk> | jgraham: given that Tab is mostly with CSS and CSS indeed follows the Process to the letter, it seems he's entirely justified to me |
| 12:01 | <annevk> | CSS WG loves Process |
| 12:01 | <jgraham> | Well it is true that's a deficiency of the CSS WG |
| 12:01 | Ms2ger | will not comment on the implementability of CSS2.1 |
| 12:02 | <jgraham> | But I think TabAtkins is not the most process-hungry member of that group |
| 12:02 | <SimonSapin> | Ms2ger: why not? |
| 12:02 | <annevk> | SimonSapin: it's a running gag |
| 12:02 | <SimonSapin> | it was painful, but I did implement most of it |
| 12:03 | <Ms2ger> | Would you say the spec is sufficient to implement something that somewhat accurately renders the web? |
| 12:04 | <SimonSapin> | I guess that would require a quirks mode, which I don’t really care about |
| 12:04 | <annevk> | or like, table rendering rules |
| 12:04 | <SimonSapin> | (and which is not specified at all) |
| 12:04 | <Ms2ger> | Quirks mode is well specified |
| 12:04 | <SimonSapin> | oh yeah, tables. These are missing |
| 12:05 | <SimonSapin> | Ms2ger: where? |
| 12:05 | <jgraham> | SimonSapin: (the short answer seems to be "no" then ;) |
| 12:05 | <Ms2ger> | http://quirks.spec.whatwg.org/ has some |
| 12:05 | <SimonSapin> | including for the parts on layout or anything CSS ? |
| 12:05 | <Ms2ger> | DOM, HTML, CSS3-Syntax all define their own quirks |
| 12:06 | <darobin> | we should call all this stuff "quirks" rather than "standards" |
| 12:06 | <darobin> | would make a lot of the world more meaningful |
| 12:06 | <Ms2ger> | DOM - Living Quirk |
| 12:06 | <SimonSapin> | thanks Ms2ger, I didn’t know about http://quirks.spec.whatwg.org |
| 12:06 | <Ms2ger> | Np :) |
| 12:06 | <darobin> | International Quirks Organisation |
| 12:07 | <darobin> | "Yeah you can do that, but it's not quirky" |
| 12:07 | <annevk> | The IQ Organization? |
| 12:07 | <Ms2ger> | Your reasoning is based on aesthetics? |
| 12:07 | <annevk> | oh the puns |
| 12:07 | <darobin> | annevk: fit inrony |
| 12:08 | <darobin> | "that's a very interesting idea, we should quirk it" |
| 12:08 | <darobin> | Ms2ger: reasoning? |
| 12:15 | <Ms2ger> | http://lists.w3.org/Archives/Public/public-whatwg-archive/2010Dec/0141.html |
| 12:16 | <darobin> | heh |
| 12:29 | <annevk> | So a dictionary has an enum. The dictionary is used in a constructor. I don't specify the enum member of the dictionary. What value does it have? |
| 12:30 | <darobin> | annevk: I'm assuming no default value has been specified? |
| 12:30 | <annevk> | right |
| 12:31 | <darobin> | null I would assume |
| 12:32 | <annevk> | enum cannot be null |
| 12:33 | <annevk> | but the issue here was indeed that the spec didn't define the default value for the event interface |
| 12:33 | <annevk> | nobody really knows what they're doing it seems |
| 12:34 | <darobin> | but dictionary values can always be null |
| 12:34 | <darobin> | (IIRC) |
| 12:35 | <darobin> | they're always optional, unless you provide a default |
| 12:35 | <darobin> | that said, maybe it would be undefined |
| 12:35 | <darobin> | WebIDL doesn't have an ES binding section on dictionaries :) |
| 12:35 | <annevk> | no, I think they'd just be missing, not null explicitly |
| 12:35 | <darobin> | yeah |
| 12:36 | <darobin> | but I can't see anywhere in WebIDL that actually says that |
| 12:37 | <Ms2ger> | Yeah, missing |
| 12:38 | <Ms2ger> | "Let present be false if Type(V) is Undefined or Null, or the result of calling the [[HasProperty]] internal method on V with property name key otherwise." |
| 12:38 | <Ms2ger> | And |
| 12:38 | <Ms2ger> | "Let dict be an empty dictionary value of type D; every dictionary member is initially considered to be not present." |
| 12:39 | <Ms2ger> | http://dev.w3.org/2006/webapi/WebIDL/#es-dictionary |
| 12:40 | <darobin> | mmmmm |
| 12:40 | darobin | *facepalm* |
| 12:40 | <darobin> | Cmd-G shows I was grepping for ditcionary in there... |
| 12:41 | <annevk> | specs are written in English darobin |
| 12:42 | <darobin> | yeah, I resent that |
| 12:42 | <darobin> | we should just make one big piece of JS implementing everything |
| 12:42 | <Ms2ger> | Should be written as a list of git commands |
| 12:42 | <darobin> | and then people could port that to their own ancient languages like C++ or Latin |
| 13:04 | <annevk> | ah man, someone reopened that attribute order bug |
| 13:05 | <annevk> | hmm https://github.com/lachlanhunt/dom/branches seems kinda dead again |
| 13:05 | <annevk> | what happened Lachy? |
| 13:06 | <Lachy> | annevk, what happened with what? |
| 13:07 | <Lachy> | it's not dead. I just haven't had any commits there in the last 2 weeks as I've been doing other things. |
| 13:13 | <Lachy> | annevk, right now, my current plan is to back port all the changes I made to selectors API in the DOM spec, back into the current selectors api 2 draft, and then make necessary changes based on Mozilla's recent feedback, so that at least it's documented somewhere. |
| 13:14 | <Lachy> | Then, when you've made your planned changes we talked about before we merge selectors api into dom, it'll be easier to do. |
| 13:59 | <annevk> | those changes have been made a while back |
| 14:08 | <zcorpan> | boblet: "postMessage for server communication" ? http://www.netmagazine.com/features/top-20-html5-sites-2012 |
| 14:10 | <annevk> | HTML helps polishing? Weird stuff |
| 14:11 | <annevk> | Repeat after me: HTML5 HTML5 HTML5 |
| 14:11 | <annevk> | Feel better? |
| 14:11 | <zewt> | but it's html5.1 now!!! |
| 14:12 | <annevk> | what can I say? It worked for me |
| 14:14 | <zcorpan> | cue all html book authors giving out new editions with s/HTML5/HTML5.1/ in the next few weeks |
| 14:15 | <annevk> | matjas: do you know if the Punycode stuff you wrote is used in the wild? I wonder (again, I know) whether to add API surface for it |
| 14:16 | <matjas> | annevk: node uses it internally for anything that involves URLs |
| 14:16 | <matjas> | annevk: and URI.js and some other open-source projects depend on it |
| 14:16 | <annevk> | matjas: yeah that makes sense, going forward the URL parser should handle that for them |
| 14:17 | <matjas> | annevk: but having a native API for the raw Punycode stuff would be immensely useful |
| 14:17 | <zewt> | i wonder who it is that's responsible for the "uri" nonsense in the first place, eg. the idea that we need a new name for what is in reality something no real people make a distinction about |
| 14:17 | <annevk> | Useful for what though? |
| 14:18 | <smaug____> | annevk: any comments to https://www.w3.org/Bugs/Public/show_bug.cgi?id=15695? |
| 14:19 | <annevk> | zewt: Oh, in the beginning we had URLs expanded, with L meaning Locators, then came the idea we could use them as identifiers, and people thought that was such a breakthrough idea it warranted a new name... |
| 14:19 | <smaug____> | or perhaps I'll just change Gecko's behavior to follow the current spec |
| 14:19 | <zcorpan> | zewt: didn't mattur or someone find an email where it was first (?) suggested to rename "url" because there were no versions, or some such? |
| 14:19 | <Ms2ger> | darobin, ping |
| 14:20 | <annevk> | smaug____: Web IDL requires specs to not use interface for callbacks with a single method (unless there's a backcompat reason) |
| 14:20 | <darobin> | Ms2ger: on phone, bbiab |
| 14:20 | <annevk> | smaug____: so I'm inclined to leave it as WONTFIX |
| 14:20 | <smaug____> | but in WebIDL ;) but ok |
| 14:20 | <smaug____> | s/but/bug/ |
| 14:20 | <annevk> | s/bug/bug in smaug____'s mind/ |
| 14:21 | <annevk> | ;) |
| 14:21 | <zewt> | oh god not the objects-as-callbacks thing again :P |
| 14:44 | <annevk> | oops |
| 14:44 | <annevk> | forgot to reply to some ancient Fullscreen feedback |
| 14:44 | <annevk> | my apologies! |
| 14:45 | <annevk> | btw, does Opera do fullscreen? |
| 14:49 | <darobin> | Ms2ger: back, sorry |
| 14:50 | <Ms2ger> | darobin, so, your idlharness update |
| 14:50 | <Ms2ger> | Does it handle callbacks? |
| 14:52 | <darobin> | Ms2ger: the only thing I've done so far is make it run on the new parser |
| 14:52 | <darobin> | so the parser handles them, but it won't generate any tests |
| 14:52 | <darobin> | beyond what's already in |
| 14:52 | <darobin> | adding new test generation is the next step |
| 14:53 | <Ms2ger> | Oh, actually |
| 14:53 | <Ms2ger> | Looks like the exception is in idlharness itself |
| 14:53 | <darobin> | I want to make the Geolocation API's IDL produce useful tests (as something concrete to drive progress), and that uses callbacks |
| 14:53 | <darobin> | Ms2ger: also, dunno what code you're using but mine's squirrelled away into a branch for now |
| 14:54 | <darobin> | as I haven't tried it out anywhere near enough for it to be ready for prime time |
| 14:54 | <darobin> | I just plugged it in and fixed what was needed to get trivial examples to run |
| 15:04 | <annevk> | marcosc: maybe this helps: http://annevankesteren.nl/2012/12/cors-101 |
| 15:04 | annevk | goes to fix typos now |
| 15:43 | <zcorpan> | annevk: opera supports fullscreen, yes. but not the latest spec |
| 15:44 | <zcorpan> | http://www.opera.com/docs/specs/presto2.12/apis/#fullscreen |
| 15:45 | zcorpan | notes that no TR snapshot was necessary to link to a dated spec |
| 15:46 | <zcorpan> | "Implemented in core-integration-points 311 through 319" http://www.opera.com/docs/specs/presto2.11/ |
| 15:47 | <Ms2ger> | All welcome to vote in favour of calling the master branch "master" for the HTML testsuite in #HTMLT over on irc.w3.org |
| 15:57 | <zcorpan> | i thought it was decided to be "unicorn"? |
| 16:04 | Ms2ger | pokes jgraham |
| 16:04 | <odinho> | darobin: trying to send to robineko.com --> Diagnostic-Code: SMTP; 554 5.7.1 <odinho⊙oc>: Sender address rejected: Access denied |
| 16:05 | <marcosc> | annevk: thanks, will pass that on. They've not been able to articulate what the issues are |
| 16:06 | <odinho> | annevk: Oh yeah, that stupid picture. I'll just open it up in Inkscape and change the font to Arial, almost everyone has that one. |
| 16:07 | <Ms2ger> | marcosc, not joining? :) |
| 16:07 | <odinho> | Too hard to deal with all the inline styles in the svg. :] |
| 16:07 | <marcosc> | oh, what! |
| 16:07 | marcosc | catches up |
| 16:07 | <Ms2ger> | HTML testsuite organization! |
| 16:07 | <Ms2ger> | And branch name bikeshedding! |
| 16:08 | <darobin> | odinho: robineko? I shut that address down 6 months ago :) |
| 16:08 | <marcosc> | Ms2ger: I love a good bikeshed! Where you guys talking about this? |
| 16:08 | <darobin> | use berjon.com or w3.org please! |
| 16:09 | <Ms2ger> | marcosc, irc.w3.org #HTMLT |
| 16:09 | <odinho> | darobin: Well, I didn't get the memo :P Or my Opera M2 didn't at least :] |
| 16:09 | <darobin> | I didn't even know that you'd ever sent me mail to that address :) |
| 16:10 | <annevk> | better not mint too many email addresses |
| 16:11 | <darobin> | yeah, a long time ago I thought I might need a separate address for consulting, but people just kept writing to the personal address anyway |
| 16:13 | <annevk> | I filter mailing lists and that leaves hardly any email |
| 16:17 | <annevk> | well well, uri⊙wo and public-iri⊙wo died out |
| 16:31 | <annevk> | dglazkov: in the email you wrote, I guess some of the links are off? |
| 16:31 | <annevk> | dglazkov: it seems a few times you refer to the earlier algorithm in prose, but the link points to the later one... |
| 16:32 | <annevk> | dglazkov: are mouse events the only problematic events here? what about touch? |
| 16:33 | <dglazkov> | good morning, Whatwg! |
| 16:34 | <dglazkov> | annevk: touch event are definitely going to need retargeting, too. |
| 16:36 | <dglazkov> | annevk: I may have copy/pasted links carelessly in the email |
| 16:36 | <dglazkov> | annevk: let me check |
| 16:36 | <annevk> | dglazkov: also, why call it ancestor and not parent? |
| 16:36 | <annevk> | dglazkov: isn't it a parent chain |
| 16:36 | <dglazkov> | annevk: you call it ancestor chain |
| 16:37 | <dglazkov> | oh wait |
| 16:37 | <dglazkov> | it's even path |
| 16:37 | <dglazkov> | event path |
| 16:37 | <annevk> | yeah |
| 16:37 | <annevk> | and it's a chain of parents, which together are called ancestors |
| 16:38 | <annevk> | but okay, I can manage the terminology mismatch I suppose |
| 16:39 | <dglazkov> | I guess then any given item in chain is ancestor in relation to event target |
| 16:39 | <annevk> | dglazkov: the "Repeat while ANCESTOR exists:" is just about finding the next parent right? |
| 16:39 | <dglazkov> | annevk: yep |
| 16:39 | <annevk> | I want the "event path" to be constructed in a functional manner |
| 16:40 | <annevk> | so the dispatch algo asks the event target for its "event parent" and does that recursively to build up the event path |
| 16:40 | <annevk> | and then we make hooks elsewhere in dispatch/invoke for adjusting stuff such as relatedTarget |
| 16:41 | <annevk> | if possible |
| 16:41 | <dglazkov> | aha. One link is off. In item 5 of the list in my mail, it should refer to http://dom.spec.whatwg.org/#dispatching-events |
| 16:43 | <dglazkov> | annevk: interesting on the recursion. Sure, if you can pull it off, sounds great |
| 16:45 | <dglazkov> | annevk: please feel free to run drafts/ideas by me or hayato⊙co |
| 16:45 | <dglazkov> | annevk: I will happily review and help out |
| 16:45 | <annevk> | cool; the main problem is I want this to work for the seamless iframe stuff too, which requires event object cloning |
| 16:48 | <odinho> | annevk: Arialified: http://odinho.html5.org/CORS/cors-diagram-arial.svg |
| 16:53 | <dglazkov> | annevk: event object cloning is a special case of retargeting, I'll need that for shadow dom here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=16509 |
| 16:57 | <annevk> | yeah, you'd need it for isolation |
| 16:59 | <annevk> | dglazkov: btw, wouldn't the relatedtarget only change at boundary points? |
| 16:59 | <dglazkov> | annevk: yes. |
| 16:59 | <annevk> | dglazkov: that is, when you exit a shadow tree (and either enter another one or come back to the real world) |
| 17:00 | <annevk> | so why would you store it for each object in the event path? |
| 17:00 | <dglazkov> | annevk: or come from insertion point back into shadow tree |
| 17:00 | <annevk> | right |
| 17:00 | <dglazkov> | annevk: you don't |
| 17:00 | <dglazkov> | or shouldn't |
| 17:01 | <annevk> | so I think what we should have is to create a stack of objects that's the event path; as well as markers or some such that indicate boundary points |
| 17:01 | <annevk> | the markers can then be used to either adjust the event object or maybe use a clone or some such |
| 17:03 | <dglazkov> | wait, you're talking about target, not relatedtarget |
| 17:03 | <dglazkov> | right? |
| 17:03 | <annevk> | well both I suppose |
| 17:04 | <dglazkov> | you need to store adjusted target for the same reasons you store the event path |
| 17:04 | <dglazkov> | because DOM changes by event listeners could affect the result |
| 17:04 | <annevk> | hmmm |
| 17:20 | <annevk> | actually no |
| 17:20 | <annevk> | dglazkov: well the event path is cached |
| 17:21 | <annevk> | dglazkov: so you're saying we need to cache the targets too in case the tree is manipulated |
| 17:24 | <dglazkov> | annevk: technically, you don't have to cache them, as long as you cached the event path and the boundaries. But it makes the algorithm easier to understand. |
| 17:25 | <MikeSmith> | Fuck we gotta fix the OPTIONS thing on w3c-test odinho |
| 17:25 | <dglazkov> | even if the tree is manipulated, as long as the markers (as you called them) for when the boundary transitions occurred at the time of constructing event path are cached, you can reconstruct the adjusted targets. |
| 17:25 | <MikeSmith> | but i still have no clue |
| 17:27 | <odinho> | MikeSmith: Hehe :-) darobin came a bit closer when he said it was working on a clean (new) Apache though. So the diff between "normal apache" and w3c-one, ought to be a bit smaller than going through everything at least. |
| 17:27 | <MikeSmith> | yeah |
| 17:30 | <MikeSmith> | anyway I'm at a loss. i like fiddling with Apache BS just slightly better than i love writing apps in PHP |
| 17:33 | <odinho> | Haha, me too. I even stopped using Apache, and use nginx nowadays. |
| 17:33 | <odinho> | Anyway, I should leave work, no good standing here all day - it's been super dark for a long time already. |
| 17:34 | <MikeSmith> | yep |
| 17:36 | <MikeSmith> | i find that the mass of Apache "tuning" i ever do is just unwinding all the idiotic things that Apache does by default |
| 17:36 | <Ms2ger> | MikeSmith, where's your console spec gone? |
| 17:37 | <MikeSmith> | odinho: Hai |
| 17:37 | <MikeSmith> | Ms2ger: should still be there wherever it was before |
| 17:38 | <MikeSmith> | I'm nu |
| 17:38 | <Ms2ger> | MikeSmith, where was your console spec before? :) |
| 17:38 | <MikeSmith> | github |
| 17:38 | <MikeSmith> | sideshowbarker |
| 17:38 | <MikeSmith> | i think |
| 17:41 | <MikeSmith> | can get you the URL later |
| 17:41 | <MikeSmith> | right now I'm on my mobile |
| 17:41 | <MikeSmith> | plus, I'm lit |
| 17:42 | <Ms2ger> | Yeah, found it |
| 17:43 | <MikeSmith> | anyway, vp9 |
| 17:44 | <MikeSmith> | clearly the time is right |
| 17:45 | <MikeSmith> | since vp8 has seen such widespread adoption |
| 17:45 | <TabAtkins> | Ms2ger: No, "and/or" carries some useful weight as being unambiguously different from xor. Plain "or" can be interpreted in either way in English. |
| 17:48 | <TabAtkins> | nimbu: (Hopefully you read logs.) Regarding http://trac.webkit.org/changeset/136744, it's not exposed to JS. We're just copying Firefox and making pseudo-elements live in the DOM tree, to make our code sane. |
| 17:55 | <annevk> | dglazkov: right okay |
| 17:56 | <TabAtkins> | annevk: Why isn't an enum nullable? |
| 17:56 | <jwalden> | onload in a top-level window that has iframes in it, with valid srcs for them, should block until the iframes have onload, right? |
| 17:56 | <annevk> | TabAtkins: oh it is |
| 17:56 | <TabAtkins> | annevk: Ah kk. |
| 17:56 | <annevk> | TabAtkins: but we haven't used that ability thus far |
| 17:56 | <TabAtkins> | Ok, then I'll send my response email. |
| 17:57 | <TabAtkins> | It seems weird to me that enums would have a different "no value" behavior than all the other types in WebIDL. |
| 17:58 | <jwalden> | oh, never mind, I are Dumb |
| 17:58 | jwalden | could have sworn window.frameName gave back a window, not the iframe element |
| 17:58 | <annevk> | TabAtkins: typically for strings the no value case is the empty string, not null |
| 17:59 | <Ms2ger> | jwalden, ... it does |
| 17:59 | <TabAtkins> | annevk: Yeah, but it's a weird split. I'd prefer the platform have one behavior there. |
| 18:00 | <jwalden> | Ms2ger: not in this testcase, oddly |
| 18:00 | <annevk> | I don't really think there's a split TabAtkins |
| 18:00 | <Hixie> | MikeSmith: well the DOM you get when you don't have the depth limiter is definitely the ideal result, but I think it's reasonable to assume that if we need the depth limiter, we won't end up with that exact result. |
| 18:00 | <annevk> | TabAtkins: e.g. for numbers they typically default to 0 or Infinity or some such, not null |
| 18:00 | <Ms2ger> | jwalden, global scope pollution? |
| 18:00 | <Hixie> | zcorpan: I think the text in r7589 is right; why wouldn't it be? |
| 18:01 | <TabAtkins> | Hmm, not sure about that, but I'd have to look into stuff for evidence. |
| 18:03 | <annevk> | it's also awkward if you need to explicitly null check an attribute |
| 18:03 | <annevk> | much easier if they're all strings, which is why XHR.responseType is just that... |
| 18:03 | <TabAtkins> | The right way is to just test it for falseyness anyway. |
| 18:03 | <TabAtkins> | Can you elaborate why it's awkward? |
| 18:05 | <annevk> | because you need to account for distinct types and cannot assume what you got can be manipulated as a single type |
| 18:05 | <Hixie> | jgraham: the only reason i think the process violation matters is that the process is supposedly the reason the whatwg is bad and the w3c is good |
| 18:05 | <Hixie> | (according to some) |
| 18:06 | <jwalden> | Ms2ger: oh, sigh, <iframe name=foo> and <iframe id=foo> are unalike in this matter |
| 18:06 | <TabAtkins> | annevk: Ah, that's true. null+'' == 'null' |
| 18:07 | <annevk> | jwalden: for global scope pollution the name attribute only works on a select set of elements |
| 18:07 | <annevk> | jwalden: forgot if <iframe> is among them |
| 18:08 | <jwalden> | annevk: window.frameName is distinct from GSP, or at least it is in Gecko |
| 18:08 | <Hixie> | Ms2ger: how do i replace and/or in "When a user agent is to fetch a resource or URL, optionally from an origin origin, optionally using a specific referrer source as an override referrer source, and optionally with a synchronous flag, a manual redirect flag, a force same-origin flag, and/or a block cookies flag, the following steps must be run."? |
| 18:08 | <annevk> | jwalden: sounds about right |
| 18:08 | <Ms2ger> | "or"? :) |
| 18:08 | <jwalden> | window.frameName appears to look only for name=, GSP was looking for id=, and I was using id= and so getting GSP behavior where I expected window.frameName behavior |
| 18:09 | <jwalden> | yeah, that was a hedge :-) |
| 18:09 | <jwalden> | given GSP is stupid |
| 18:09 | <Ms2ger> | But hey, at least it's specced now |
| 18:10 | <jwalden> | aaaagh |
| 18:10 | <jwalden> | stupid webkit, stupidly treating data URLs as different-origin and making life hard for one-off test authors |
| 18:10 | <Ms2ger> | Hixie, tbh, a list |
| 18:10 | <annevk> | hmm |
| 18:10 | <annevk> | so where is window.frameName defined? |
| 18:11 | <Hixie> | Ms2ger: oh, i see, prefix the list with something like "optionally with any of" or something |
| 18:11 | <annevk> | no hits in http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html |
| 18:11 | <annevk> | hmm, jwalden, does that even exist? |
| 18:11 | <jwalden> | annevk: you don't want to search for frameName, that'd only apply if <iframe name="frameName"> |
| 18:12 | jwalden | doesn't know the term to use |
| 18:12 | <Ms2ger> | annevk, getter(DOMString) |
| 18:12 | <annevk> | oh it's window.name |
| 18:12 | <Ms2ger> | Hixie, yeah |
| 18:12 | <annevk> | well window.name exists |
| 18:12 | <annevk> | http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#dom-name |
| 18:13 | <annevk> | the other one is http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#dom-window-nameditem |
| 18:13 | <annevk> | jwalden: named property access? |
| 18:13 | <jwalden> | perhaps |
| 18:13 | jwalden | is just trying to write a document.all testcase |
| 18:13 | <jwalden> | STAB ME NOW |
| 18:14 | <annevk> | so yeah, window[name] can never match <iframe name=frame> because <iframe> is not on the whitelist |
| 18:14 | <annevk> | but I guess <a target=frame> will target that |
| 18:14 | <annevk> | good times |
| 18:14 | <jwalden> | ...wait, what? |
| 18:14 | <jwalden> | window.foo should give you <iframe name=foo>'s window |
| 18:15 | <jwalden> | or at least that's what I'm seeing in Gecko, and I thought it was supposed to be how iframe window.* stuff worked |
| 18:15 | <annevk> | never mind, I'm missing something |
| 18:15 | <Hixie> | Ms2ger: "Zero or more As and/or Bs" when trying to say you can do "ABBA" or "AA" or "B" |
| 18:15 | <annevk> | this pollution is not only global scope pollution, it's apparently also fricking weird |
| 18:15 | <jwalden> | :-) |
| 18:16 | <Hixie> | Ms2ger: "Zero or more As and Bs" seems a little less unambiguous. Any suggestions? |
| 18:16 | <annevk> | sometimes returning Window objects, sometimes elements, sometimes a single element |
| 18:17 | <Ms2ger> | annevk, yeah, it's both frames.name and window.name :) |
| 18:17 | <annevk> | Ms2ger: I prefer self, it's more zen |
| 18:17 | <jgraham> | Hixie: I don't think it follows that people think that every part of the Process is good or necessary. That is, I don't think it is logically inconsistent to think that the Process is better than the WHATWG approach and to be happy with violation of some aspects of the Process. |
| 18:17 | <jgraham> | But I guess I should stop talking |
| 18:18 | <jgraham> | Or I might accidentially create a Process discussion |
| 18:18 | Ms2ger | kicks jgraham out of the tree house |
| 18:18 | <annevk> | jgraham: sounds reasonable to me |
| 18:18 | <annevk> | jgraham: I personally like the patent bits, the rest not so much |
| 18:18 | <Hixie> | jgraham: if there are people saying that the process is why i should work at the w3c, but who simultaneously believe that they can ignore the process when it suits them, then how the heck am i supposed to know when i'm to follow the process or not? |
| 18:19 | <Hixie> | jgraham: they released the CR yesterday with _131_ open bugs |
| 18:19 | <Hixie> | jgraham: if "we have to resolve all open feedback before going to CR" isn't one of the things in the process that matters, what is? |
| 18:19 | <Hixie> | jgraham: i'm all in favour of just ignoring the process, or having some well-defined subset that we actually agree should be followed |
| 18:19 | <Hixie> | jgraham: it's this hypocritical double-standard that i have a problem with |
| 18:20 | <Ms2ger> | The part that matters is: "The W3C will put up a press release" |
| 18:20 | <TabAtkins> | Hixie: Use of just "and" seems fine there. |
| 18:20 | <Hixie> | TabAtkins: roger |
| 18:21 | <jgraham> | Well arguably the HTMLWG did have a well-defined subset that will actually be followed |
| 18:22 | <jgraham> | They set release dates |
| 18:22 | <Hixie> | they've never followed _those_ before |
| 18:22 | <jgraham> | and said "on those dates we will transition" |
| 18:22 | <jgraham> | "and screw all other considerations" |
| 18:22 | <jgraham> | Which isn't a bad process, really |
| 18:22 | <Hixie> | if the w3c wants to do transitions on a date-based schedule, then fine. if that's their process, then i disagree with their process on substance. |
| 18:23 | <Hixie> | but they don't claim that that's their process, as they claim to care about spec quality. |
| 18:23 | <jgraham> | I don't really care what they claim to care about |
| 18:23 | <Hixie> | i care insofar as they ask me to work with their process |
| 18:23 | <jgraham> | I care when they get in the way of improving the web |
| 18:24 | <Hixie> | making me follow a process that doesn't put quality first seems to be an example of such |
| 18:24 | <jgraham> | AFAICT releasing the old version of the spec with a new label and known bugs doesn't really affect that |
| 18:24 | <jgraham> | As long as everyone important knows it's an old version |
| 18:24 | <Hixie> | depends on the label, but yeah, i'm all in favour of releasing patent snapshots |
| 18:25 | <Hixie> | but if that's what they want to do, why are they bothering with the intermediate steps? |
| 18:25 | <Hixie> | if they're going to transition regardless, why not just do the transitions that matter? |
| 18:25 | <jgraham> | Because it looks more like the Process |
| 18:25 | <Hixie> | so, bullshit then |
| 18:25 | <Hixie> | that's my point. |
| 18:25 | <jgraham> | Well, I don't think that complaining about it will make the Process more likely to change |
| 18:26 | <Hixie> | agreed |
| 18:26 | <Hixie> | but highlighting the hypocrisy might reduce the number of people who try to argue me into following teh process :-) |
| 18:26 | <jgraham> | Although I think that documenting it and putting forward evidence that the real process is something other than the Process might be convincing when discussions about Process change are happening |
| 18:27 | <jwalden> | dangit Hixie, why do you have to use standards mode for http://software.hixie.ch/ :-( |
| 18:27 | jwalden | finds another page on that domain that doesn't |
| 18:27 | <Hixie> | jwalden: if you need a quirks page i can make one |
| 18:27 | <Hixie> | jwalden: what's up |
| 18:28 | <jwalden> | Hixie: /utilities/js/ did the trick for me |
| 18:28 | <jgraham> | In particular being able to say "actually with sucessful specs X Y and Z we ignored these parts of the Process" is a pretty compelling counterargument when you get the usual conservative voices saying "we can't change anything because (imaginary reason)" |
| 18:28 | <Hixie> | jwalden: /quirks |
| 18:29 | <jwalden> | Hixie: that'll do too, and a little more nicely -- thanks! |
| 18:29 | <Hixie> | jwalden: np |
| 18:29 | <Hixie> | jgraham: HTML has been hugely successful by pretty much every metric and has entirely ignored the process so far, hasn't convinced anyone yet :-) |
| 18:29 | <Hixie> | anyone at w3c i mean |
| 18:29 | <Hixie> | except maybe MikeSmith :-) |
| 18:30 | <jwalden> | (tm) |
| 18:31 | <jgraham> | jwalden: Oh, that MikeSmith! |
| 18:35 | <JonathanNeal> | helloo |
| 18:37 | <jwalden> | is there any way to expand the little fast-commenting widget on whatwg.org/html other than by DOM-hacking? what I want to say is single-paragraphish, a little past single-lineish |
| 18:37 | <Hixie> | yeah |
| 18:37 | <Hixie> | submit the comment |
| 18:37 | <Hixie> | then use the bug form :-) |
| 18:37 | <Hixie> | or whatwg.org/newbug |
| 19:22 | <hober> | what's the url to that 'selected history of when features have been added to the web platform' page? |
| 19:23 | <Ms2ger> | http://platform.html5.org/history/ |
| 19:24 | <hober> | thanks. http://platform.html5.org/ should really link to that. :) |
| 19:26 | <annevk> | Hixie: claiming there are no lines while they have distinct editors is not useful, or you volunteering? |
| 19:26 | <annevk> | are you* |
| 19:26 | <jwalden> | Hixie: I went with /newbug, filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=20436 |
| 19:27 | <Ms2ger> | annevk, he's volunteering you to edit HTML :) |
| 19:27 | <annevk> | Ms2ger: interesting plot twist, but no thanks :) |
| 19:28 | <Ms2ger> | Wasn't the ambient light events feedback supposed to go to another list than public-webapps? |
| 19:28 | <jwalden> | hm, and I mostly missed a Gecko platform meeting |
| 19:38 | <Hixie> | annevk: i think the line between what each of us edits is more or less arbitrary |
| 19:38 | <Hixie> | annevk: e.g. look at CORS vs Fetch vs URL |
| 19:39 | <annevk> | yeah that's a mess now :( |
| 19:39 | <annevk> | well, apart from URL, that's mostly sane |
| 19:39 | <annevk> | (layering wise) |
| 19:39 | <Hixie> | i'd say the line between DOM and HTML is similarly messy :-) |
| 19:39 | <Hixie> | (which is fine) |
| 19:40 | <annevk> | well, my plan for Fetch/CORS is to merge them |
| 19:40 | <annevk> | for DOM I don't know, I guess it could be part of HTML at some point; currently it has no dependencies on HTML which is kinda nice |
| 19:40 | <annevk> | if we add origin that'd no longer be the case |
| 19:40 | <Hixie> | you can add origin by reffing [ORIGIN] |
| 19:41 | <Hixie> | no need to ref HTML |
| 19:41 | <Hixie> | we can always avoid two-way references just by using hooks |
| 19:41 | <Hixie> | but it's an artificial avoidance |
| 19:44 | <annevk> | no that's not the problem |
| 19:44 | <annevk> | the problem is for new Document() I need to get hold of the script's origin or something to copy from |
| 19:44 | <Hixie> | sure but you could in theory just offer a hook |
| 19:44 | <Hixie> | not saying you should |
| 19:48 | <annevk> | I think I'll just define it and have Ms2ger find another way |
| 19:49 | <annevk> | and if he doesn't I suppose I might merge in domparsing |
| 19:49 | <Hixie> | heh |
| 19:49 | <annevk> | mind if I reassign that bug to DOM? |
| 19:50 | <Hixie> | go ahead, just don't close it if there's anything more to do before it's fixed |
| 19:50 | <Hixie> | (not that i would expect you would) |
| 19:50 | <annevk> | I guess I might file a new bug on HTML to "update for DOM origin" or some such |
| 19:51 | <Hixie> | lgtm |
| 19:54 | <annevk> | I don't get https://twitter.com/w3cmemes/status/281121937193828352 |
| 19:54 | <annevk> | Prefixes are not part of the W3C Process |
| 19:55 | <Hixie> | wow, that's a lot of w3cmemes about the process thing |
| 19:55 | <Hixie> | and i didn't even post one of them :-) |
| 19:58 | <annevk> | since people complained about the lack of memes, I thought I'd add a couple |
| 19:59 | <tantek> | maybe it's a "living CR" ;) |
| 20:02 | <hober> | annevk: that one presumably refers to TTA |
| 20:03 | <annevk> | hober: well sure and presumably the person writing that one thought the others were written by someone on the CSS WG |
| 20:03 | <annevk> | hober: even so though, unprefixing has nothing to do with the W3C Process |
| 20:03 | <hober> | indeed |
| 20:04 | <hober> | i'm ashamed to admit i don't get the fraft one |
| 20:04 | <Ms2ger> | That was just a typo on my part, I think |
| 20:05 | <annevk> | heh |
| 20:07 | <Ms2ger> | Dec 11 18:02:11 <krisk> E.g. draft and not master |
| 20:07 | <Ms2ger> | Dec 11 18:02:24 <Ms2ger> Everything is a fraft |
| 20:09 | annevk | tunes in to w3cmemes history channel |
| 20:41 | <jamesr_> | annevk, prefixes are handled within the w3c process in the csswg, roughly speaking |
| 21:01 | <tantek> | jamesr_, annevk, not really. The CSSWG has its own process for prefixes, which got heavily amended this past year, due to widespread acceptance that the previous process for prefixes wasn't working. |
| 21:01 | <tantek> | There's no W3C process for "prefixes". |
| 21:02 | <tantek> | W3C-wide that is. |
| 21:02 | <tantek> | No other WG that I know of re-uses CSSWG prefix processes either. |
| 21:06 | <JonathanNeal> | a lot of w3c memes about cr |
| 21:06 | <hober> | jamesr_: apis defined in the webapps wg, for instance, get unprefixed in a much more informal manner than css properties |
| 21:07 | <JonathanNeal> | http://24.media.tumblr.com/tumblr_mebyf5EMTk1rvsbh9o1_400.gif haha |
| 21:09 | <JonathanNeal> | I liked <main>, Hixie. :| |
| 21:10 | <Hixie> | <main> (and role=main) don't do anything you can't do more effectively in other ways, as far as i can tell |
| 21:13 | <JonathanNeal> | All right. I will try to do it the right way. How should I do it? |
| 21:16 | <jgraham> | WebApps doesn't have any prefix process that I know of. If vendors prefix webapps things that's a choice not a decree from on high |
| 21:16 | <JonathanNeal> | I'm sorry if that seems like a baiting question. I'm actually very interested in html element and class naming conventions. |
| 21:17 | <jgraham> | JonathanNeal: Hixie's opinion on <main> is not universially shared :) |
| 21:17 | <JonathanNeal> | jgraham: well, I would really appreciate contrasting examples. Are there any on the web / in a gist right now? |
| 21:18 | <jgraham> | JonathanNeal: (I have no idea what your originl question was) |
| 21:18 | <JonathanNeal> | jgraham: my question is that, if <main> (and role=main) don't do anything you can't do more effectively in other ways, how should I do it then? |
| 21:19 | <JonathanNeal> | and by "do it" I mean "markup something that would have used <main> or role=main" |
| 21:19 | <jamesr_> | JonathanNeal, that image is gold :D |
| 21:20 | <jgraham> | JonathanNeal: I don't think I agree with the premise there |
| 21:20 | <jgraham> | At least |
| 21:20 | <JonathanNeal> | That's great. I'm probably going to learn something then. |
| 21:21 | <jgraham> | I am under the impression that role=main is actually supported in screenreaders in a way that the "scooby doo" alternative isn't |
| 21:21 | <JonathanNeal> | Would it help if I posted a gist of how I might have used role="main" in a simple html document, or would this still proceed the questionable premise? |
| 21:21 | <jgraham> | And that it is more likely that they will implement <main> than the scooby doo algorithm |
| 21:21 | <jgraham> | No, that seems quite reasonable. |
| 21:22 | <JonathanNeal> | What is the "scooby doo" alternative? |
| 21:22 | <Hixie> | JonathanNeal: what is "it" that you are trying to do? |
| 21:23 | <jgraham> | My understanding is that if you are thinking "<main> surrounds the content that is *this page* rather than site-wide content, or navigation, or whatever" you are doing it right |
| 21:24 | <jgraham> | Alternatively, if you prefer a more practical way of looking at it, it should be the content that you would like a AT user to skip to if they ask to skip to the main content |
| 21:24 | <JonathanNeal> | jgraham: what you just said is what I thought it was, and how I was using role="main". Like an ID, it was a solitary and unique grouping. |
| 21:24 | <tantek> | jgraham, yes is my understanding as well |
| 21:24 | <JonathanNeal> | jgraham: I was, however, confused over whether <main> was per group or per page. |
| 21:24 | <jgraham> | per page |
| 21:24 | <tantek> | JonathanNeal, you can go ahead and use <main> right now as long as you close your <p> … </p> elements explicitly ;) |
| 21:26 | <jgraham> | JonathanNeal: the "scooby doo" algorithm is the alternative approach. You enumerate all the characters in the story, subtract out the ones you recognise (Scooby, Shaggy, Velma, Daphne, etc.) and whoever's left is the villian. Except s/story/markup/, s/characters/section elements/ and s/villian/main content/ |
| 21:26 | <JonathanNeal> | I see. In other areas, many <elements> were scoped per group, like <header>, <footer>, <nav>, even <section>, <article>, etc. This would make <main> very unique, like <title>, <html>, <body>. |
| 21:26 | <JonathanNeal> | Am I understanding this correctly? |
| 21:26 | <jgraham> | Yes |
| 21:27 | <jgraham> | It is more-body-than-body |
| 21:27 | <jgraham> | if you like |
| 21:28 | <erlehmann> | oh hello people |
| 21:28 | <erlehmann> | i just posted this on the list http://daten.dieweltistgarnichtso.net/src/media-fragments-html-polyfill/ |
| 21:29 | <erlehmann> | how can i help bringing this into the browsers? |
| 21:31 | <JonathanNeal> | erlehmann: is there supposed to be something more than <http://example.org/podcast.html#episode1&t=01:23>; ? Like, an element name? |
| 21:31 | <erlehmann> | JonathanNeal, episode1 is the element name. |
| 21:31 | <erlehmann> | in my example, #audio and #video are the element names |
| 21:32 | <JonathanNeal> | Sorry, the element's nodeName. |
| 21:33 | <erlehmann> | JonathanNeal, I do not understand how the name of the current node comes into this |
| 21:34 | <JonathanNeal> | In your example, you have between a < and > a url. I've never seen markup like this. |
| 21:34 | <erlehmann> | oh, that is not markup. |
| 21:34 | <erlehmann> | that is a url. |
| 21:34 | <erlehmann> | sorry, is this misleading? let me correct it. |
| 21:34 | <erlehmann> | urls in plain text are delimited by < and > |
| 21:34 | <TabAtkins> | That's just a common way of indicating in plain-text markup that something is a URL, and delimiting it from surrounding text like commas and periods. |
| 21:35 | <TabAtkins> | (Works in Markdown.) |
| 21:35 | <erlehmann> | corrected. |
| 21:35 | <JonathanNeal> | Ah, sorry, I interpreted it differently on that page. |
| 21:35 | <erlehmann> | JonathanNeal, corrected. |
| 21:36 | <JonathanNeal> | Yeap. That's a fun polyfill. Good job taking advantage of the hashchange event. |
| 21:37 | <erlehmann> | JonathanNeal, i removed the brackets and wrote text clarifying that this is an URL |
| 21:37 | <JonathanNeal> | erlehmann: Yeap. I saw. It was very minor and I'm sorry it threw me off. |
| 21:37 | <erlehmann> | as far as i am concerned, misunderstandings are my fault. |
| 21:38 | <erlehmann> | so, as i regard this very useful, where do i start implementing it? |
| 21:39 | <erlehmann> | or does this suffice as proof of concept? |
| 21:41 | <annevk> | erlehmann: <abbr title=Hypertext Markup Language> does not work ;) |
| 21:41 | <annevk> | erlehmann: well it does, but Markup and Language are not valid attributes :) |
| 21:41 | <JonathanNeal> | erlehmann: is there a git project? |
| 21:42 | <annevk> | erlehmann: also, you might want to write & as & |
| 21:42 | <erlehmann> | yeah, & probably should have been escaped as & at a lots of places |
| 21:42 | <erlehmann> | annevk, thanks. |
| 21:42 | <erlehmann> | i will correct |
| 21:43 | <annevk> | maybe if we start introducing this it would be better to avoid using & again |
| 21:43 | <erlehmann> | validates now http://html5.validator.nu/?doc=http%3A%2F%2Fdaten.dieweltistgarnichtso.net%2Fsrc%2Fmedia-fragments-html-polyfill%2Findex.html |
| 21:43 | <annevk> | and use ; as a separator in the fragment |
| 21:44 | <erlehmann> | yeah, media fragments use “&” as a separator already |
| 21:45 | <annevk> | oh it's a W3C REC |
| 21:45 | <annevk> | meh |
| 21:46 | <erlehmann> | http://www.example.com/example.ogv#track=audio&t=10,20 |
| 21:46 | <erlehmann> | well … |
| 21:46 | <JonathanNeal> | erlehmann: I'm getting an error "Uncaught TypeError: Cannot call method 'split' of undefined", because there was no fragment. |
| 21:46 | <erlehmann> | JonathanNeal, well … well. Let me fix that. |
| 21:46 | <JonathanNeal> | I can fix this and send it to you, or you can fix it yourself. Could we host this on git? |
| 21:46 | <erlehmann> | Thanks! |
| 21:46 | <erlehmann> | I'll create a repository |
| 21:47 | <JonathanNeal> | Thanks. I'll subscribe, fork, and make suggestions for you to reject. 8P |
| 21:49 | <erlehmann> | JonathanNeal https://github.com/erlehmann/media-fragments-html-polyfill |
| 21:49 | <erlehmann> | 8P! 9P! |
| 21:49 | <erlehmann> | :D |
| 21:49 | <erlehmann> | :---DDD |
| 21:50 | <JonathanNeal> | Hixie, are you saying you prefer the "scooby doo" method that jgraham mentioned, where you enumerate all the characters in the story, subtract out the ones you recognize (Scooby, Shaggy, Velma, Daphne, etc.) and whoever's left is the villain. Except s/story/markup/, s/characters/section elements/ and s/villian/main content/ ? |
| 21:50 | <Hixie> | JonathanNeal: let's start from fundamentals; what's the problem you're trying to solve? |
| 21:51 | <erlehmann> | Evidence-based web standards. I like! |
| 21:52 | <erlehmann> | JonathanNeal, can you fix the uncaught type error and stuff? I am writing a README right now. |
| 21:52 | <JonathanNeal> | I would like to reflect the meaning of my document. The prerequisite is that I could use all <div>s and well phrased classnames, but I like using something more semantic than classnames. |
| 21:53 | <JonathanNeal> | erlehmann: heap, on it. |
| 21:53 | <Hixie> | JonathanNeal: if you just want to reflect the meaning of your document, then include a huge <!-- comment --> in your source code that documents the meaning in detail. |
| 21:54 | <Hixie> | (in a natural language) |
| 21:54 | <JonathanNeal> | Would you say this is a suitable alternative to my goal? |
| 21:54 | <JonathanNeal> | Sorry, to the <main> method? |
| 21:56 | <erlehmann> | JonathanNeal, what meaning you want to convey that is missing without <main> ? |
| 21:59 | <JonathanNeal> | Let me correct this bug in the most minimal way possible. There are a few failure points. |
| 21:59 | <Hixie> | JonathanNeal: if your goal is to "reflect the meaning of my document", I don't think <main> really does anything to help you at all |
| 21:59 | <Hixie> | JonathanNeal: but then i don't really think "reflect the meaning of my document" is your actual goal |
| 22:00 | <JonathanNeal> | Hixie: <header/><main/><footer/> |
| 22:00 | <Hixie> | JonathanNeal: <header/>...<footer/> |
| 22:01 | <JonathanNeal> | I understand. By remainder we have the main content. |
| 22:02 | <Hixie> | also, consider <header/>...<aside/>...<aside/>...<footer/> |
| 22:02 | <Hixie> | but again, the real question is what problem are you trying to solve? |
| 22:02 | <Hixie> | because without knowing the problem, it's hard to evaluate the solution |
| 22:02 | <Hixie> | if the problem is "my document doesn't have an element named "main"" then obviously <main> solves the problem better than anything else |
| 22:03 | <Hixie> | if the problem is "my document doesn't have anything bluew in it" then nothing we're talking about helps one way or the other |
| 22:03 | <Hixie> | blue |
| 22:04 | <Velmont> | Not having endless "what is the use for x" and how to use "y" is also a feature of kinds. |
| 22:04 | <Velmont> | (put discussions in there somewhere :P) |
| 22:05 | <JonathanNeal> | Hixie, I'm sorry that, despite my efforts, you do not believe I have asked a suitable question or presented a suitable problem that is worth solving. |
| 22:05 | <Velmont> | Mapping more to how web devs see the world -> less confusion -> win. |
| 22:06 | <Hixie> | JonathanNeal: the only problem you've described is "I would like to reflect the meaning of my document". |
| 22:06 | <JonathanNeal> | I would like to clearly define the main content of my document. |
| 22:06 | <Hixie> | why? |
| 22:07 | <Hixie> | can you describe the problem you're trying to solve in terms of the user, say? |
| 22:07 | <JonathanNeal> | So that I can dictate to computers where the main content of my document is, and so that I can control markup aspects of the main content. |
| 22:09 | <erlehmann> | JonathanNeal, rational taboo „main content“. how would you describe it then? |
| 22:10 | <JonathanNeal> | I'm unsure how to answer that question, I'm sorry. I don't understand it. |
| 22:12 | <erlehmann> | the rationalist taboo is a technique to get more accurate results in discussion http://rationalwiki.org/wiki/Rationalist_taboo |
| 22:12 | <erlehmann> | if you are not allowed to mention „main content“ how would you describe that which you want to represent? |
| 22:13 | <Hixie> | JonathanNeal: so you're saying you want to style parts of your document differently? |
| 22:14 | <Hixie> | JonathanNeal: doesn't <div> do that already? |
| 22:17 | <erlehmann> | > When you find yourself in philosophical difficulties, the first line of defense is not to define your problematic terms, but to see whether you can think without using those terms at all. Or any of their short synonyms. And be careful not to let yourself invent a new word to use instead. |
| 22:17 | <erlehmann> | i find that useful |
| 22:20 | <JonathanNeal> | As I said earlier, I could use <div classname> everywhere, so perhaps the question is "when should a element with an implied meaning be used instead of a element with generic meaning? |
| 22:20 | <JonathanNeal> | "when should there be" |
| 22:21 | <Hixie> | JonathanNeal: so far the answer has been "when authors use a class name so consistently that a single definition describes the use" and "when providing an element with a specific meaning allows for new functionality" |
| 22:21 | <Hixie> | JonathanNeal: so e.g. <section> allows for automatic heading sizing |
| 22:22 | <Hixie> | JonathanNeal: and <footer> is used pretty consistently |
| 22:22 | <JonathanNeal> | erlehmann: pull request sent. I tried to split the commits out so you could see how I arrived where I did. |
| 22:22 | <Hixie> | or rather, class=footer |
| 22:25 | <erlehmann> | JonathanNeal, this makes it less readable https://github.com/jonathantneal/media-fragments-html-polyfill/commit/72f50bc7c19ac1d920300a933f479e85a5e0dd9e |
| 22:26 | <erlehmann> | the others are fine :) |
| 22:29 | <JonathanNeal> | erlehmann: would comments resolve the readability issue? It seems less readable with functions because it makes the flow less linear. |
| 22:29 | <erlehmann> | i just don't like regular expressions |
| 22:30 | <JonathanNeal> | But I understand that's why you're naming the functions as such. Well, your split can have some adverse effects. For instance, if you split by & and return [1] then you're potentially losing [2], [3], etc. |
| 22:30 | <JonathanNeal> | This is why I switched to regular expressions, which are your friend. |
| 22:31 | <JonathanNeal> | Hixie: what about for hgroup? I always thought the web used something closer to subline. |
| 22:31 | <JonathanNeal> | Until hgroup, that is. |
| 22:32 | <Hixie> | hgroup matches the second category - it provides new functionality |
| 22:32 | <Hixie> | (namely, not confusing outliners such as used by the spec itself) |
| 22:32 | <Hixie> | heycam: http://lists.w3.org/Archives/Public/public-script-coord/2012OctDec/0007.html - is this something that was fixed in webidl, perchance? |
| 22:33 | <Hixie> | (afk, bb in 30) |
| 22:33 | <JonathanNeal> | Hixie: so in this case <main> does not add functionality that role="main" doesn't already imply? |
| 22:34 | <Hixie> | role=main doesn't add functionality either |
| 22:34 | <Hixie> | (actually afk) |
| 22:35 | <heycam> | Hixie, not fixed yet |
| 22:35 | <JonathanNeal> | It separates the main content of your document from the heading, navigation, etc. Following your criteria, "skip to main content" links have been used so consistently that a single definition describes the use. |
| 22:36 | <JonathanNeal> | erlehmann: trying to ping you off this channel about the bugs. not sure if you're getting my messages. |
| 22:38 | <erlehmann> | still there |
| 22:38 | <erlehmann> | i wrote my own irc client |
| 22:38 | <JonathanNeal> | Does it support private messaging? |
| 22:38 | <JonathanNeal> | Hixie: would skip to "main" content usage on the web qualify? |
| 23:02 | <Hixie> | back |
| 23:03 | <Hixie> | JonathanNeal: when i looked at pages, i found that actually "skip to main content" links, #main, .main, .content, etc, were actually not used that consistently at all |
| 23:03 | <Hixie> | heycam: is it tracked? should i file a bug? i want to make sure either you fix it or i do :-) |
| 23:04 | <heycam> | Hixie, I am tracking which mails I haven't responded to on the list, so I will get to it |
| 23:04 | <heycam> | at some point |
| 23:04 | <heycam> | :) |
| 23:04 | <Stevef> | hixie: why not provide data to back up your opinions or rebutt the data provided? |
| 23:04 | <Hixie> | heycam: k. If that one's on your list, I shall delete it from mine :-) |
| 23:04 | <Hixie> | Stevef: i did, long ago, nothing's changed since |
| 23:05 | <Stevef> | hixie: so point to this long ago data |
| 23:05 | <erlehmann> | JonathanNeal, my own irc client is a collection of shell scripts working upon a filesystem that has FIFOs for irc channels. |
| 23:06 | <Hixie> | Stevef: it's in the archives somewhere. i really don't care enough about it to argue the case further. |
| 23:06 | <erlehmann> | this is the foundation (not from me) http://tools.suckless.org/ii/ this is the client https://github.com/erlehmann/uii |
| 23:06 | <Hixie> | Stevef: if you're right, then you'll convince the browser vendors and they'll implement it and it'll get added to the spec without me having to argue about it. |
| 23:06 | <Hixie> | Stevef: if you're wrong, then we're already done |
| 23:07 | <erlehmann> | I see a game-theoretic problem with <main>. If there is no easier way than marking everything else up, people will mark everything else up |
| 23:07 | <erlehmann> | because it is the rational thing to do |
| 23:07 | <erlehmann> | if you enable to mark up <main> without marking up <nav> or <header> or <footer>, then you lose semantics |
| 23:08 | <Stevef> | hixie: I an optimistic on that front, and its already specced as well so you don't have to do anything :-) |
| 23:13 | <Hixie> | erlehmann: that's a concern, but not one i've examined closely since unless there's a point to the feature, i don't generally look at the feature's problems |
| 23:14 | <erlehmann> | Stevef, JonathanNeal, would it help to spec the scooby doo algorithm? |
| 23:14 | <Hixie> | it's called "interpreting HTML correctly" |
| 23:14 | <Hixie> | there's really no algorithm to spec |
| 23:17 | <JonathanNeal> | Hixie: I understand your point of view just from your initial remark. When you looked at pages, you did not see "main" being used consistently. |
| 23:17 | <Stevef> | erlehmann: there have been discussions about doing that, nothing concrete yet |
| 23:17 | <erlehmann> | i think i have not understood the hard use case of <main>. |
| 23:18 | <erlehmann> | Stevef, I would rather have a common heuristic than a new element. |
| 23:18 | <JonathanNeal> | And you do not think developers should be able to explicitly define the content that is directly related to or expands upon the central topic of the document. |
| 23:19 | <Hixie> | JonathanNeal: i think they already do explicitly do that. Just putting the content in the document is doing that. |
| 23:20 | <Hixie> | anyone with IE handy? |
| 23:20 | <erlehmann> | JonathanNeal, many of my documents do not have <aside> or <nav>. like the one with the polyfill for media fragments and stuff. |
| 23:21 | <Hixie> | looking to find out what happens in IE when you click "Open" on http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2029 |
| 23:21 | <erlehmann> | which IE? |
| 23:21 | <Hixie> | any really |
| 23:21 | <erlehmann> | let me try if it still works |
| 23:21 | <JonathanNeal> | I have IE. |
| 23:21 | <JonathanNeal> | No cat is shown and no error is thrown in IE8. |
| 23:21 | <erlehmann> | i have IE8 on linux. :3 |
| 23:22 | <Hixie> | JonathanNeal: thanks |
| 23:22 | <Hixie> | erlehmann: that's... hard core |
| 23:22 | <JonathanNeal> | erlehmann rewrote the entire thing for linux, manually sectioned off all the bugs. it can interpret the web as ie1 through 11. |
| 23:23 | <erlehmann> | hixie, nowadays, not so anymore. using a package called „playonlinux“ one can create a custom wine installation for programs. delete that folder … and. well. |
| 23:23 | <erlehmann> | here, more info about this http://www.playonlinux.com/en/commentaires-577.html |
| 23:23 | <Hixie> | fun |
| 23:23 | <erlehmann> | it is like a package manager for windows software |
| 23:35 | <erlehmann> | well, that IE is bogging down my computer ;_; |
| 23:35 | <erlehmann> | also, it was IE7 |
| 23:36 | <erlehmann> | and absolutely nothing happens when clicking that button |
| 23:36 | <Hixie> | thanks |
| 23:36 | <erlehmann> | well, i am not sure what should happen |
| 23:37 | <Hixie> | a cat should appear, per spec |
| 23:40 | <erlehmann> | this is how i tested (ogg theora video) http://mister-muffin.de/p/yZj8 |
| 23:41 | <erlehmann> | i hope it was right |
| 23:41 | <erlehmann> | and the cat was not somewhere else |
| 23:43 | <Hixie> | yup, that's right :-) |
| 23:43 | <erlehmann> | good :) |
| 23:43 | <Hixie> | if you test in webkit-based browsers or opera, you'll see the cat |
| 23:44 | <erlehmann> | you realize that sounds like a 90ies hit-the-monkey thing? ;) |
| 23:44 | <Hixie> | -_- |
| 23:48 | <erlehmann> | wait, in conkeror also nothing happens. |
| 23:48 | <erlehmann> | for http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2029 |
| 23:48 | <erlehmann> | i'll check chromium |
| 23:49 | <Hixie> | how ancient is conkeror's rendering engine? |
| 23:50 | <erlehmann> | i believe it is somewhat current xul magic |
| 23:50 | <erlehmann> | gecko |
| 23:50 | <erlehmann> | let me check |
| 23:51 | <erlehmann> | chromium shows a cat, Version 21.0.1180.89 Debian wheezy/sid (154005) |
| 23:52 | <Hixie> | if it's gecko then yeah, no cat |
| 23:52 | <erlehmann> | oh okay |
| 23:53 | <erlehmann> | cats, internet. oh well. |
| 23:55 | <zewt> | o/~ dreaming of the day vertically centering stuff isn't a migraine |
| 23:55 | <TabAtkins> | Dude, this is already a reality in browsers that support new flexbox. |
| 23:56 | <zewt> | dude, doesn't help squat until every browser has it |
| 23:56 | <Hixie> | TabAtkins: do you have a data: url example? |
| 23:56 | <TabAtkins> | Hixie: Of vertical centering? |
| 23:56 | <Hixie> | yeah |
| 23:56 | <Hixie> | i'm not up on flexbox |
| 23:56 | <TabAtkins> | Sure, one sec. |
| 23:57 | <zewt> | wonder if there are any passable flexbox polyfills, though |
| 23:58 | <zewt> | guess that's pretty hard without mutation observers (which isn't any more available) |
| 23:59 | <TabAtkins> | data:text/html;charset=utf-8,<!DOCTYPE%20html>%0A<div%20id%3Dcontainer>%0A%20<div%20id%3Dchild>foo<%2Fdiv>%0A<%2Fdiv>%0A<style>%0Adiv%20%7B%20background%3A%20rgba(0%2C0%2C0%2C.2)%3B%20%7D%0A%23container%20%7B%20height%3A%20100px%3B%20width%3A%20100px%3B%20display%3A%20-webkit-flex%3B%20-webkit-justify-content%3A%20center%3B%20-webkit-align-items%3A%20center%3B%20%7D%0A<%2Fstyle> |
| 23:59 | <zewt> | aaaaaaaaaaaaaaaaaaaaaaaaaaa |
| 23:59 | <TabAtkins> | ??? |
