| 00:00 | <jarek> | boogyman: yeah, that's what I'm doing right now, but this is used so often that it really deserves better API |
| 00:01 | <jarek> | Attribute nodes have the property "node" which gives me lowercase values |
| 00:02 | <jarek> | I mean "name", not "node" |
| 00:02 | <jarek> | it would make perfect sense to also have "node" property on elements |
| 00:03 | <jarek> | oops, I meant "name", not "node", again |
| 00:22 | <ek_> | hello |
| 00:38 | <karlcow> | jarek: maybe better https://github.com/search?q=%22nodeName.toLowerCase%28%29%22&ref=searchresults&type=Code&utf8=%E2%9C%93 |
| 00:38 | <karlcow> | even https://github.com/search?l=javascript&q=%22nodeName.toLowerCase%28%29%22&ref=searchresults&type=Code&utf8=%E2%9C%93 |
| 00:45 | <jarek> | karlcow: Github code search is broken |
| 00:45 | <jarek> | e.g. try https://github.com/search?utf8=%E2%9C%93&q=%22tagName.toLowerCase%22&type=Code&ref=searchresults |
| 00:49 | <jarek> | or even https://github.com/search?l=javascript&q=tagName+toLowerCase&ref=searchresults&type=Code&utf8=%E2%9C%93 |
| 00:50 | <jarek> | almost every bigger project uses this hack somewhere |
| 00:52 | <karlcow> | ah better search. Cool |
| 01:29 | <MikeSmith> | for anybody around who's knowledgeable about Chrome's WebRTC implementation: it seems like a bug that doesn't recognize RTCPeerConnection.createOffer() (with no args) |
| 01:29 | <MikeSmith> | so I'm wondering if there might be an open Chromium bug for that |
| 01:30 | <MikeSmith> | the WebIDL at http://w3c.github.io/webrtc-pc/#interface-definition says: |
| 01:31 | <MikeSmith> | interface RTCPeerConnection : EventTarget { Promise<RTCSessionDescription> createOffer (optional RTCOfferOptions options); |
| 02:54 | <MikeSmith> | heycam: any chance you might be able to rope in somebody to review the SVG tests you submitted? |
| 02:55 | <MikeSmith> | otherwise they might end up just sitting for a while |
| 02:55 | <MikeSmith> | wonder if ed could be talked into reviewing |
| 02:55 | <heycam> | MikeSmith, I sent an email to jgraham asking about review procedures but maybe it got caught in a spam filter |
| 02:56 | <MikeSmith> | oh |
| 02:56 | <heycam> | MikeSmith, how do we (SVG WG members) become allowed to review tests? |
| 02:56 | <MikeSmith> | or maybe jgraham just not made time to reply yet |
| 02:56 | <MikeSmith> | anybody can review |
| 02:56 | <MikeSmith> | just not everybody can merge to master |
| 02:57 | <heycam> | I see |
| 02:57 | <heycam> | how do you indicate r+? |
| 02:57 | <MikeSmith> | using this critic tool thing that came from Opera originally |
| 02:57 | <heycam> | aha |
| 02:57 | <heycam> | and then someone will be alerted to the fact that it passed review, and one of you wpt owners will merge it? |
| 02:57 | <MikeSmith> | yup |
| 02:58 | <MikeSmith> | exactly that |
| 02:58 | <heycam> | ok, great |
| 02:58 | <heycam> | I had a couple of questions about file format / testing approach in those two PRs |
| 02:58 | <MikeSmith> | I don't know if you've used critic before but it's not so bad |
| 02:58 | <MikeSmith> | oh |
| 02:58 | <MikeSmith> | OK I might be able to answer |
| 02:58 | <heycam> | so hopefully one of you can answer those, so I've got a baseline I can review other tests from |
| 02:58 | <MikeSmith> | ok |
| 02:59 | <MikeSmith> | did you send the questions to a mailing list? |
| 02:59 | <MikeSmith> | if not, you might want to |
| 02:59 | <heycam> | no, they're just in the PRs |
| 02:59 | <MikeSmith> | ah OK |
| 02:59 | MikeSmith | looks now |
| 02:59 | <heycam> | is there a mailing list that's good for wpt discussion? |
| 03:00 | <MikeSmith> | yeah, we use public-test-infra⊙wo |
| 03:00 | <MikeSmith> | https://lists.w3.org/Archives/Public/public-test-infra/ |
| 03:00 | <heycam> | ok, I'll get on that one |
| 03:01 | <MikeSmith> | so about the question of the best way to handle scripted SVG tests, I take it you mean putting the script in HTML test file itself vs a separate file |
| 03:02 | <MikeSmith> | if so there's no policy nor any recommended best practice really |
| 03:02 | <heycam> | yeah, or even just having the SVG document as the top level thing and including testharness.js in there |
| 03:02 | <heycam> | I figure the test harness reporting thing won't work if you do that though |
| 03:02 | <MikeSmith> | ah |
| 03:03 | <MikeSmith> | yeah the reporting thing wouldn't work in that case |
| 03:03 | <MikeSmith> | I guess we could figure out a way to make it work, if that would make it easier to write SVG tests |
| 03:04 | <heycam> | nah, it should be fine. we're not really caring about UAs that support SVG and script but not HTML |
| 03:04 | <MikeSmith> | ah yeah |
| 03:05 | <heycam> | one other question: my reftest for <rect> is comparing against an <div>. some people in the WG (last week at the F2F) said they would prefer not comparing against HTML, and would rather a PNG reference there |
| 03:05 | <heycam> | wdyt? |
| 03:09 | <MikeSmith> | I guess comparing against HTML is what existing wpt tests would normally do, but I suppose in that's in part just because it's all assuming an HTML UA to begin with |
| 03:09 | <MikeSmith> | but SVG is different of course |
| 03:09 | <MikeSmith> | so anyway it wouldn't be against policy or best practice to compare against a PNG reference |
| 03:10 | <MikeSmith> | there are probably some existing tests that already do I guess |
| 03:10 | <heycam> | ok |
| 03:10 | <heycam> | I figure if we do that it's probably only go to be for some of the base tests that all the rest of the tests rely on |
| 03:10 | <MikeSmith> | it's maybe just more work for you as the test authro |
| 03:10 | <MikeSmith> | ok |
| 03:10 | <heycam> | yeah, generating the PNG is a little annoying |
| 03:11 | <MikeSmith> | yeah but it's not a huge hardship and if is makes others happier I guess it might be worth it |
| 03:12 | <MikeSmith> | btw about <link rel=help> thing, is there a reason to not point it to the ED? |
| 03:12 | <heycam> | yeah. it will make it easier for example for Inkscape to import the tests. |
| 03:12 | <heycam> | no good reason; I just copied another test that pointed to TR/ |
| 03:12 | <MikeSmith> | ah Inkscape yeah (the PNG thing) |
| 03:13 | <heycam> | still there are probably a bunch of SVG text tests that would warrant testing against HTML |
| 03:13 | <MikeSmith> | yeah |
| 03:14 | <MikeSmith> | and for better or worse, I think the harness and infrastructure overall pretty much assume an HTML UA |
| 03:15 | <heycam> | for sure. though hopefully do have their own harness to import and run the tests in an automated fashion. |
| 03:15 | <heycam> | *hopefully vendors |
| 03:16 | <heycam> | I will get a bit more time to look at the tests after the end of this month. thanks for the answers; I'll direct questions to public-test-infra as they come up. |
| 03:16 | <MikeSmith> | yeah (about automation), though jgraham has been working hard on making it possible for all vendors to integrate wptrunner into their CI (similar to the way mozilla CI does already) |
| 03:16 | <MikeSmith> | super |
| 03:17 | <MikeSmith> | and if/when it's faster, feel free to also ping me any time here or on #testing |
| 03:18 | <heycam> | ok, cheers |
| 05:02 | annevk | wonders why jarek doesn't use localName |
| 05:03 | <annevk> | heycam: MikeSmith: using PNGs seems bad |
| 05:03 | <annevk> | heycam: MikeSmith: it's one of the reasons WebKit/Blink have so much overhead |
| 05:03 | <annevk> | heycam: MikeSmith: in their testing infrastructure |
| 05:03 | <heycam> | it would only be for a couple of basic tests |
| 05:04 | <heycam> | I agree we don't want to have PNGs for everything |
| 05:04 | <heycam> | (their repo was massive because they had PNGs for everything) |
| 05:04 | <annevk> | heycam: I don't really understand why on the one hand the WG is okay with accepting HTML / scripting, but on the other hand they'd want to use PNG for reftests |
| 05:05 | <annevk> | heycam: but that does sound better |
| 05:05 | <heycam> | it would help at least for the Inkscape folks, who can't run script, but do want to be able to run the reftests |
| 05:05 | <heycam> | though Rossen preferred the PNG for the <rect> test too |
| 05:05 | heycam | shrugs |
| 05:06 | heycam | should look up what Gecko has for <path> reftests, if anything |
| 05:07 | <heycam> | the answer is: very little |
| 05:33 | <MikeSmith> | annevk: heycam I would assume that enabling a few ad-hoc PNG reftests for some SVG tests wouldn't require any additional infrastructure outside of what those tests need themselves, nor require needing to provide some general supported mechanism in the wpt infrastructure to do it for other tests |
| 05:34 | <MikeSmith> | but that said, if it requires any python modules that we aren't already requiring, then even just that would make it a non-starter probably |
| 05:34 | <MikeSmith> | see jgraham comment at https://lists.w3.org/Archives/Public/public-test-infra/2015AprJun/0010.html |
| 05:35 | <annevk> | MikeSmith: the problem for WebKit/Blink is 1) weight of the repo and 2) the cost of having to regenerate those images |
| 05:35 | <annevk> | MikeSmith: 2) might be less of a problem for SVG than it is for ordinary layout tests |
| 05:35 | <annevk> | MikeSmith: but once you start with fonts, it's still tricky I think |
| 05:36 | <heycam> | annevk, I reckon for text/font tests that need it, comparing against HTML should be ok |
| 05:36 | <heycam> | and hopefully Ahem can be used for most of the rest of SVG text tests |
| 05:37 | <MikeSmith> | as far at the PNGs, if it's possible for static PNGs to be used rather than needing be dynamically generated, the those can just be checked in and we don't have any cost other than the additional footprint |
| 05:38 | <heycam> | yeah I'm not expecting the reference PNGs to change |
| 05:38 | <MikeSmith> | I wouldn't think we'd be looking at much additional weight for the repo if it's just isolated to these SVG tests |
| 05:39 | <heycam> | and it's not like we have the problem of pixel-perfect checking that WebKit's tests require (or required?), over multiple platforms |
| 05:39 | <MikeSmith> | heycam: yeah OK then I think the potential problems annevk mentioned might not be so relevant in this particular case |
| 05:41 | <MikeSmith> | (but that said I agree with annevk that we'd never want to end up with that problems that WebKit/Blink have created for themselves with what they built out for the general case) |
| 05:41 | <heycam> | right, I agree |
| 05:48 | <annevk> | Hmm, going through http://krijnhoetmer.nl/irc-logs/whatwg/20141119#l-235 again I can't find the bug rubys was talking about |
| 05:48 | <annevk> | As far as I can tell prepending always works fine |
| 05:49 | <annevk> | Because the buffer is cleared after each time you see @ |
| 05:51 | <MikeSmith> | annevk: other than "hmm, yeah, there's a bug there, I can't reproduce reordering in Firefox"? |
| 05:52 | <annevk> | MikeSmith: I guess I should test browsers |
| 05:53 | <annevk> | MikeSmith: afaict for http://@test@test⊙ec/ you want a username that is %40test%40test and Firefox seems to do just that |
| 05:53 | <annevk> | Chrome does the same |
| 05:53 | <annevk> | So maybe I was reading the specification wrong back then? |
| 05:53 | <annevk> | In any event, I should check that this is tested |
| 06:20 | <MikeSmith> | annevk: yeah (about %40test%40test for username) |
| 06:22 | <Ms2ger> | So is it me or have I not seen Hixie in a long time? |
| 06:52 | <MikeSmith> | Ms2ger: yeah he's not been around here so much recently |
| 06:53 | <MikeSmith> | abarth not been around as much for a while either |
| 07:51 | <philipj> | Ms2ger: how do you pronounce your nick? |
| 07:51 | <philipj> | is it like i18n, so "messenger" or something? |
| 07:52 | <Ms2ger> | There is no canonical pronunciation |
| 07:53 | <philipj> | Well OK, I'll just make stuff up then :) |
| 07:53 | <annevk> | miss-too-ger |
| 07:54 | <philipj> | I think of V'ger |
| 07:58 | <MikeSmith> | I just say "em es two gee ee are" |
| 07:59 | <MikeSmith> | which is longer but more elegantly symmetrical in that it has the same number of syllables as "Anne van Kesteren" |
| 07:59 | <philipj> | We'll just have to wait until Ms2ger writes a book that gets recorded as an audio book |
| 08:00 | <philipj> | MikeSmith: coincidence? I think not! |
| 08:00 | <MikeSmith> | I vote for that book to be narrated either by Benedict Cumberbatch or Ian McShane |
| 08:02 | <philipj> | "A technological history of mutation events, by em es two gee ee are, narrated by that guy from Sherlock" |
| 08:04 | <Ms2ger> | I have no connection with Wimbledon Tennismatch |
| 08:05 | <MikeSmith> | "with interludes from Henry Miller's Tropic of Cancer read by James Graham in the speaking manner of Blackbeard from one of those Johnny Depp pirate movies" |
| 08:06 | <philipj> | :) |
| 08:06 | <Ms2ger> | Based on interviews with /smaug/ |
| 08:09 | <MikeSmith> | heh |
| 08:13 | <annevk> | It seems Safari simply returns failure if it sees a duplicate @ |
| 08:17 | <annevk> | Sebmaster: https://github.com/w3c/web-platform-tests/pull/1907 |
| 08:17 | <annevk> | MikeSmith: ^ |
| 08:18 | MikeSmith | looks |
| 08:18 | <Sebmaster> | annevk: got it ;) |
| 08:19 | <MikeSmith> | annevk: will review it shortly |
| 08:22 | annevk | reaches out to the Safari team |
| 08:28 | <MikeSmith> | annevk: I don't find a test for "http://`{}:`{}@h/`{}?`{}" in Sebmaster's file at https://github.com/jsdom/whatwg-url/blob/master/test/additional-tests.txt |
| 08:29 | <annevk> | he tests for `, {, and }, based on recent changes to the specification |
| 08:29 | <MikeSmith> | I see one for "http://test:a{b@localhost" and one for "http://localhost?query=a`b"; |
| 08:29 | <MikeSmith> | ok |
| 08:29 | <annevk> | I adjusted the test to cast a somewhat wider net |
| 08:30 | <MikeSmith> | hai |
| 08:37 | MikeSmith | sees the "Use the username and password encode sets within authority state" spec change come across |
| 08:40 | <Sebmaster> | annevk: sweet, i think the new fragment tests found a bug in my implementation |
| 08:41 | <annevk> | Sebmaster: well I had to change the specification for them, so :-) |
| 08:41 | <Sebmaster> | ohh :< |
| 08:41 | <annevk> | Sebmaster: https://github.com/whatwg/url/commit/7468c397f600b72f650f52fc02466f051bf96ad3 |
| 08:41 | <Sebmaster> | but the @ flag didnt break anything i think |
| 08:41 | <annevk> | Sebmaster: yeah, the @ flag was a non-issue |
| 08:42 | <annevk> | Sebmaster: at least, I can't think of a reason why I thought it was a problem and looking at the specification today it seems fine |
| 08:43 | <annevk> | Sebmaster: you could watch whatwg/url if you want to see the commits come by |
| 08:43 | <annevk> | or follow on Twitter I suppose |
| 08:44 | <Sebmaster> | hrm... but watching gives me all issue comments right? |
| 08:44 | <annevk> | Yeah it would |
| 08:44 | <Sebmaster> | twitter it is |
| 08:50 | <annevk> | mathiasbynens: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27641 (feel free to sort this out) |
| 08:51 | <annevk> | mathiasbynens: I think hober also has some insights here and a funny demo URL that shows how broken RTL URLs are |
| 08:51 | <annevk> | mathiasbynens: my thinking at the moment is that I'll wait and put a recommendation in the specification once UAs have demonstrated something that works reasonably well |
| 08:52 | <MikeSmith> | annevk: wow https://code.google.com/p/chromium/issues/detail?id=351639 is epic (the "Security: Spoofable RTL URLs in the UI" bug) |
| 08:53 | <annevk> | quick, resurrect John Milton for a poem |
| 08:53 | <MikeSmith> | heh |
| 08:54 | <MikeSmith> | annevk: does the proposal from Matt Giuca have agreement? |
| 08:54 | <MikeSmith> | I mean as far as Chrome goes |
| 08:54 | <annevk> | MikeSmith: not sure, I had not read that far |
| 08:55 | <MikeSmith> | ah yeah I see mathiasbynens just recently cc'ed you |
| 08:56 | <annevk> | This does not look as bad as what Safari does |
| 08:56 | <annevk> | Safari puts part of the path into the domain |
| 08:56 | <Sebmaster> | annevk: i think im missing a set relative flag now to make `pathname` return schema data instead of "/" |
| 09:00 | <annevk> | Sebmaster: hmm yes |
| 09:00 | <annevk> | Sebmaster: I guess I should just inline it |
| 09:00 | <Sebmaster> | so not my impl? |
| 09:00 | <annevk> | Sebmaster: bug in spec |
| 09:01 | <Sebmaster> | great |
| 09:01 | <Sebmaster> | ... for me, that is :D |
| 09:03 | <MikeSmith> | finding spec bugs is the greatest achievement possible, so it's always good |
| 09:04 | <MikeSmith> | the prayer bells ring in heaven every time somebody finds a spec bug |
| 09:09 | <jgraham> | MikeSmith: I think you need to recalibrate your achievementometer there |
| 09:09 | <Ms2ger> | Morning jgraham |
| 09:10 | <jgraham> | Ms2ger: What do you want? :) |
| 09:17 | <annevk> | Sebmaster: fixed |
| 09:18 | <Sebmaster> | annevk: on it |
| 09:18 | <Sebmaster> | annevk: lookin good |
| 09:18 | <Sebmaster> | all tests pass again (including the new ones) |
| 09:22 | <annevk> | I guess I should start working on (new URL("test", "test://x/")).href === "test://x/test" as that's going to be a lot of work :-( |
| 09:26 | <Sebmaster> | annevk: good luck... or something :D |
| 10:10 | <annevk> | Yeah, this is a giant mess |
| 10:37 | <Ms2ger> | jgraham, just to say good morning |
| 10:44 | <hsivonen> | so, according to Wikipedia, it seems like Gecko's Big5-HKSCS support has been stuck to a pre-2004 level for a decade... |
| 10:46 | <Ms2ger> | When did ftang leave? :) |
| 10:46 | <hsivonen> | Ms2ger: in 2003 at the latest if not before |
| 12:10 | <annevk> | SimonSapin: https://lists.w3.org/Archives/Public/public-whatwg-archive/2015Jun/0028.html |
| 12:14 | <SimonSapin> | annevk: data:/../ becomes data:/ ‽ |
| 12:14 | <annevk> | yeah |
| 12:14 | <SimonSapin> | this makes no sense |
| 12:14 | <annevk> | that's actually pretty much what RFC 3986 says |
| 12:14 | <annevk> | so things will be much closer to what the IETF does |
| 12:15 | <annevk> | also, see topic? |
| 12:15 | <SimonSapin> | so are you supposed to use something like data:%2F..%2F ? |
| 12:16 | <annevk> | SimonSapin: data URLs don't start with a slash typically so it's not a problem |
| 12:16 | <SimonSapin> | is it only at the start? |
| 12:16 | <annevk> | if you start with a slash you become a relative URL |
| 12:16 | <SimonSapin> | what about, say, data:,a/../ |
| 12:17 | <annevk> | that would stay as-is, obviously |
| 12:17 | <annevk> | it's no longer a path |
| 12:17 | <SimonSapin> | is that current impls, or a proposal? |
| 12:17 | <annevk> | current impls per the email? |
| 12:17 | <SimonSapin> | obviously, not that obvious to me |
| 12:23 | <SimonSapin> | annevk: I’d like to take more time to look into this, but I can’t really in the next two weeks |
| 12:28 | <annevk> | SimonSapin: I'm pretty sure about my general outline, but I guess I can always revert if you find a showstopper |
| 12:28 | <annevk> | SimonSapin: we can discuss it more next week if you want |
| 12:35 | <SimonSapin> | annevk: will you be in Whistler ? |
| 12:35 | <annevk> | yeah |
| 12:36 | <SimonSapin> | ok, we can chat about it then |
| 12:55 | <annevk> | philipj: https://bugzilla.mozilla.org/show_bug.cgi?id=912470#c69 |
| 12:55 | <annevk> | philipj: hsivonen is implementing your big5 work |
| 12:58 | <philipj> | annevk, hsivonen, I hope it works out, it would be sweet if we can have the big5 label always mean the same thing |
| 13:01 | <annevk> | philipj: if you didn't click, you might want to look and answer the question about that test |
| 13:01 | annevk | hopes it works out too |
| 13:07 | <philipj> | annevk: I did follow the link, but didn't recognize test_big5.js as my thing, is it just the data from the spec? |
| 13:08 | <annevk> | oh oops |
| 13:08 | <annevk> | it's from jsbell |
| 13:08 | <annevk> | my bad |
| 13:08 | <annevk> | I assumed it must be yours if he found it someplace online |
| 13:10 | <annevk> | Sebmaster: supporting relative URLs all over might not actually be that bad, a lot can be reused, though it depends a bit on how we decide to do certain things |
| 13:10 | <annevk> | Sebmaster: I guess I'll start with writing tests though so you can catch all my bugs :p |
| 13:10 | <philipj> | nope, I wasn't involved with that. Just a single input and a single output seems not enough to test this well, someone (tm) needs to write tests that target specific steps of the algorithm in the spec I think |
| 13:11 | <annevk> | if only I could get a hold of that someone (tm) I might make them write some other tests too |
| 13:24 | <jgraham> | MikeSmith: I think they're talking about you ;) |
| 13:29 | <MikeSmith> | heh |
| 13:29 | <Sebmaster> | annevk: i love tests |
| 13:29 | <Sebmaster> | not writing them though :> |
| 13:30 | <MikeSmith> | the only thing funner than writing tests is reviewing them |
| 13:30 | <MikeSmith> | wait not, debugging intermittent test failures is the funnest beyond those two things put together |
| 14:26 | <annevk> | SimonSapin: I'm going with your idea btw of clearly calling out "ASCII strings" in the specification |
| 14:26 | <SimonSapin> | annevk: ok |
| 14:56 | <annevk> | Hmm, https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/0901.html only Domenic's email is not clickable |
| 14:57 | <annevk> | Did someone use a regular expression to parse email addresses and assumed everyone would use at least two characters? |
| 14:57 | <SimonSapin> | or have a TLD whitelist |
| 14:57 | <wanderview> | this is my new mental image for spec writers: http://www.shutterstock.com/video/clip-2985172-stock-footage-happy-engineer-holding-blueprints-against-a-white-background.html |
| 14:58 | <annevk> | Seems arbitrary to recognize the Netherlands but not Montenegro |
| 14:58 | <SimonSapin> | annevk: at some point I had rust-url use a string type that is guaranteed to b ASCII (like String is guaranteed to be UTF-8) but that was inconvenient for users so I went back to String. Still, ASCII strings make sense for the spec |
| 14:58 | <JoWie> | maybe the regexp was written by someone from nl |
| 14:59 | <annevk> | SimonSapin: users should not directly modify those slots though |
| 14:59 | <annevk> | SimonSapin: oh, I guess you'd have to cast? |
| 14:59 | <SimonSapin> | yeah, even accessing is annoying |
| 15:00 | <annevk> | bah |
| 15:00 | <SimonSapin> | things like `if url.scheme == "http"` wouldn’t work |
| 15:00 | <annevk> | yeah that sucks |
| 15:00 | <annevk> | you need the cleverness of the ECMAScript engine I guess |
| 15:00 | <annevk> | s/need/want/ |
| 15:01 | <SimonSapin> | maybe it wouldn’t be as bad with newer fancy language features, but I think it’s enough to document "these strings are always ASCII" |
| 15:01 | <annevk> | that's pretty much what the spec says now |
| 15:02 | <annevk> | A few of them could be restricted even more, but not worth it for now |
| 15:02 | <SimonSapin> | the spec’s algorithms don’t have a type checker :) |
| 15:02 | <annevk> | It's called SimonSapin|Sebmaster |
| 15:06 | <SimonSapin> | wanderview: spec writing actually looks like this: https://imgur.com/44qdOfz |
| 15:19 | <Sebmaster> | annevk: huh? |
| 15:19 | <Sebmaster> | what joke did i not get? |
| 15:19 | <annevk> | Sebmaster: that you're the type checker of the spec |
| 15:19 | <Sebmaster> | sweet :> |
| 17:51 | <annevk> | Hmm... If either A or B is X, but not both nor neither, terminate these steps. |
| 17:51 | <annevk> | What would be a vastly better way of writing that out? |
| 17:51 | <annevk> | Two steps? If A and B are both X, terminate. If A and B are both not X, terminate? |
| 17:53 | <caitp> | that sounds like the opposite of the instructions you said above |
| 17:53 | <caitp> | if A is X and A is not B, terminate these steps |
| 17:53 | <annevk> | Hmm yeah, the second set of instructions are wrong. |
| 17:54 | <annevk> | Sorry, X is a set |
| 17:54 | <annevk> | They need to either both belong or both not belong |
| 17:56 | <terinjokes> | If A and B are in the set X, terminate. If A nor B are in the set X, terminate. |
| 17:56 | <caitp> | if A is in set X then if B is not in set X, terminate these steps; else if B is in set X, terminate these steps |
| 18:16 | <TabAtkins> | annevk: Use xor. |
| 18:17 | <annevk> | TabAtkins: I thought of that, but ... |
| 18:17 | <TabAtkins> | Or just use "but not both". No need for "nor neither", since the first part of the clause already requires at least one. |
| 18:18 | <annevk> | If A exclusive or B is a X, ... |
| 18:18 | <Domenic> | I would do: If A is in X and B is not in X, terminate these steps. If A is not in X and B is in X, terminate these steps. |
| 18:18 | <TabAtkins> | Or say "if exactly one of the following is true:" with a bulleted list after. (This is more useful for three conditions.) |
| 18:18 | <TabAtkins> | annevk: "If a xor B is a X", with xor linked to a definition for clarity. |
| 18:18 | <annevk> | Domenic: that's what the commit says |
| 18:19 | <annevk> | I guess I'll leave this as is, thanks for all the thoughts :-) |
| 18:20 | <caitp> | there isn't a very high bar for readability in html |
| 18:44 | <bholley_> | Hixie: yt? |
| 20:55 | <gde33> | greetings logicians |
| 20:59 | <gde33> | I was curious if there have been proposals for html to get a nice standard outliner. |
| 21:00 | <gde33> | something like <outline href="foo.opml"> |
| 21:01 | <gde33> | http://dev.opml.org/spec2.html |
| 21:02 | <gde33> | can have a nice fold out tree with nested opml files and site feeds files |
| 21:03 | <Sample> | I'm trying to discern the outline esp. regaring headers not rising above sections. Say you have <body><nav id="masthead"><h1>Navigation<h1><nav><h1>Rest of the document</h1> isn't the bodys outline children totally meaningless? |
| 21:03 | <Sample> | the whole document I'd think should be under the body outline |
| 21:03 | <Sample> | <body><nav> creates a totally meaningless body section right |
| 21:04 | <Sample> | it says "The body has a nav and only a nav. The rest of the document lies within other sections" |
| 21:04 | <Sample> | (second <nav> in my first example should be </nav> obviously) |
| 21:05 | <TabAtkins> | No? |
| 21:05 | <Sample> | <body><nav></nav><h1> |
| 21:05 | <Sample> | Creates "Untitled BODY" > "NAV Title" |
| 21:05 | <caitp> | html and xml differ in some ways |
| 21:05 | <Sample> | followed by new outline section H1 |
| 21:06 | <caitp> | for better or worse |
| 21:06 | <Sample> | Essentially the body's section extends only until the first Sectioning element |
| 21:06 | <Sample> | that seems super odd |
| 21:09 | <TabAtkins> | That's how you wrote it. You didn't give a heading to the body, so it gets an "implied heading". |
| 21:09 | <TabAtkins> | Order matters in an outline. |
| 21:09 | <Sample> | right |
| 21:10 | <TabAtkins> | If you want the tnire body to have a heading (that is, the nav and all other sections are children of the heading'd section), put the heading first. That's what makes the most sense in any format. |
| 21:10 | <Sample> | but is it correct to say the body's section (titled or not) extends only until the first sectioning element or <h1> |
| 21:10 | <TabAtkins> | No. The body's section contains all of its children. |
| 21:10 | <TabAtkins> | Including, in your example, the nav, and the <h1>'d section. |
| 21:11 | <Sample> | hmm |
| 21:11 | <TabAtkins> | Or, rather, <body> doesn't have a section in and of itself. It's a root for the section tree. |
| 21:11 | <TabAtkins> | The way the ouline tree is defined, the sectioning roots aren't sections themselves. |
| 21:15 | <Sample> | ah okay |
| 21:16 | <TabAtkins> | In <body>foo<nav>bar</nav><h1>baz</h1>, "foo" gets an anonymous implied section for itself, first in the outline. Then <nav> happens, making a second section (explicit, but anonymous). Then <h1> happens, making a third section (implicit, but named). So three sibling sections. |
| 21:16 | <TabAtkins> | (If I'm reading the algo correctly.) |
| 21:16 | <Sample> | my confusion was the presumption that the first <h1> was defining a title to the body's section |
| 21:17 | <TabAtkins> | Right, it's not, because there's no such thing as "the body's section". |
| 21:17 | <TabAtkins> | Tho in practice quite often the <body> contains only a single section, and all other sections are nested within it. |
| 21:17 | <Sample> | <body><nav></nav><h1></h1> confused me because I created this totally meaningless section to house just a NAV |
| 21:18 | <Sample> | my <h1> was actually wrapped in a <main> which made semantic sense but I guess I should wrap it in a <section> to prevent this odd outline |
| 21:19 | <gde33> | <nav> is just for screen readers? |
| 21:19 | <Sample> | no? |
| 21:19 | <Sample> | It's a sectioning element like section, article, aside |
| 21:19 | <gde33> | ah ok |
| 21:20 | <Sample> | nav article and aside are essentially <section> with more meaning |
| 21:21 | <boogyman> | which are all div with more meaning. |
| 21:21 | <Sample> | except div isn't sectioning content |
| 21:21 | <Sample> | and doesn't contribute to outlines |
| 21:21 | <Sample> | so not relaly |
| 21:21 | <gde33> | so much meaning one doesn't know what it all means |
| 21:24 | <gde33> | I was thinking, I want html documents in a folder but I want a menu on all pages that can be updated. Ideally it would also be cached. In stead of using javascript to document.write a few links to the page [pun mine] it would be cool to just have something like <nav src="/feed/"> |
| 21:25 | <gde33> | and a nice fold out tree with an opml in it that contains other opml files and site feeds |
| 21:27 | <gde33> | a nice fold out tree without the need for complex css, images and javascript |
| 21:27 | <Sample> | TabAtkins: well I've solved my problem by just replacing <main> with <section> so that the <h1> wasn't creating a meaningless outline within the body root |
| 21:28 | <Sample> | kind of odd because I feel like main and section have totally different meanings but I felt like I had to since headings don't rise |
| 21:28 | <Sample> | also decided <article> shouldn't represent the <main> of the document but <section> could |
| 21:33 | <Sample> | e.g. <body><nav id="document-navigation"></nav><main><h1>This represents the main content but cannot be wrapped in main or it creates a meaningless section |
| 21:35 | <boogyman> | Sample: have you tried role="presentation" |
| 21:39 | <Sample> | boogyman: you don't understand the outline =) |
| 21:39 | <boogyman> | mayb |
| 21:40 | <Sample> | it's funny the W3C version of the HTML spec totally contradicts itself regarding <main> but the WHATWG version doesn't |
| 21:40 | <boogyman> | whatwg is the source of truth according to Hixie |
| 21:40 | <Sample> | it actually made me curious to see a diff between the two |
| 22:28 | <Sample> | TabAtkins: another quick question. should links within a nav be wrapped in a header tags to make them navigible in the outline? aka, so the outline for the nav section shows both the nav header (if present) and the list of its links |
| 22:28 | <Sample> | even though the link (headers) may not have actual section content of their own |