| 00:04 | <MikeSmith> | Hixie: along with those stats I saw others from the corpus that Steve got data from that suggest <hgroup> is used way less than that |
| 00:06 | <MikeSmith> | JonathanNeal: a Chrome/Blink dev posted an Intent to Implement for <picture> to the blink-dev list |
| 00:07 | <Hixie> | steve's corpus is significantly smaller |
| 00:08 | <Hixie> | he's probably got data biased towards front pages and major sites, whereas google has much more depth in the tail |
| 00:20 | <MikeSmith> | Steve's report is at http://blog.paciellogroup.com/2012/04/html5-accessibility-chops-data-for-the-masses/ |
| 00:20 | <MikeSmith> | data if from a "Top 10,000 sites" data set |
| 00:23 | <MikeSmith> | "Of the top 8915 HTML pages, 79 (0.89%) were found to include use of the HTML5 hgroup element." |
| 00:24 | <JonathanNeal> | Change Proposal: replace hgroup with the subline element - attaboy |
| 00:24 | <JonathanNeal> | (from Steve's report) |
| 00:33 | <stevefaulkner> | JonathanNeal: we are discussing in the html wg about developing <subline> further, have had quite a bit of positive developer feedback |
| 00:35 | <JonathanNeal> | stevefaulkner: just talk, anything particular? |
| 00:37 | <GPHemsley> | Safari will download anything willy nilly |
| 00:37 | GPHemsley | wonders how vulnerable that makes it to attacks |
| 00:38 | <JonathanNeal> | More notes on Safari Reader http://mathiasbynens.be/notes/safari-reader |
| 00:38 | <stevefaulkner> | JonathanNeal: developing it as an extension spec, its got the basis for it already there http://www.html5accessibility.com/HTML5extensions/subline.html but needs some further work |
| 00:41 | <JonathanNeal> | I had seen that popping up on Google lately. I am a <subline> advocate. We had it in the html5shiv for a while. |
| 00:42 | <JonathanNeal> | But, it's always good to challenge those perspections and collect new data. |
| 00:42 | <JonathanNeal> | For instance, I did not know that w3c and whatwg had forked on it. |
| 00:44 | <stevefaulkner> | JonathanNeal: look forward to your input as we develop subline spec further then |
| 00:44 | <JonathanNeal> | ha, can't imagine i'll have anything new to contribute, but i'll always be around, and I'll always be looking for reasons I am wrong. |
| 00:44 | <JonathanNeal> | Because, in the end, I usually am. |
| 00:45 | <stevefaulkner> | likewise |
| 00:46 | <GPHemsley> | interesting... both Chrome and Safari will display a file marked as "text/<256-char string>" as plaintext |
| 00:47 | GPHemsley | wonders if that's a good idea |
| 00:48 | <GPHemsley> | (as I assumed, they do that for anything where the top-level type is "text") |
| 00:49 | <GPHemsley> | logically, that seems like a good idea |
| 00:49 | <GPHemsley> | but I wonder if there are instances where it isn't |
| 00:49 | <GPHemsley> | s/logically/intuitively/ |
| 00:49 | <TabAtkins> | Yeah, everything that's text/* is... text. Any further information just seems to be for helpful naming purposes. |
| 00:50 | <boogyman> | GPHemsley: maybe, but then you would have to question why it's being marked as "text/" if it's not truly text |
| 00:50 | <GPHemsley> | anyone have IE handy? |
| 00:50 | <boogyman> | unfortunately. lol what version? |
| 00:51 | <boogyman> | 7-10* |
| 00:52 | <JonathanNeal> | I have IE handy. |
| 00:53 | <JonathanNeal> | Have 6 on a VM because I double as a sadist? |
| 00:53 | <GPHemsley> | any version |
| 00:53 | <GPHemsley> | you can start with this: http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=web%20test |
| 00:53 | <JonathanNeal> | Interesting https://www.google.com/search?q=define:sadist "someone who obtains pleasure from inflicting pain or others" I FOR ONE ENJOY INFLICTING OTHERS |
| 00:54 | <GPHemsley> | but actually, there's one that'd be more useful |
| 00:54 | <JonathanNeal> | IE6 and IE6 want to download this file. |
| 00:54 | <GPHemsley> | JonathanNeal: What's the encoding on this page? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml;test=asdf\;charset=ISO-8859-3%20test;charset=ISO-8859-2%20te\%22st;testing=te%22st;charset=ISO-8859-5 |
| 00:54 | <JonathanNeal> | *IE7 |
| 00:55 | <JonathanNeal> | okay, hold up, testing the new link you sent. |
| 00:55 | <JonathanNeal> | IE6, IE7, and IE8 on XP all look at the file. |
| 00:56 | <JonathanNeal> | They show what appears to be the source code of a document, but the content within <body> is all squares. |
| 00:56 | <GPHemsley> | yeah, in that case I only care about which encoding they chose |
| 00:57 | <GPHemsley> | squares suggests -3 |
| 00:57 | <GPHemsley> | IIRC |
| 00:58 | <JonathanNeal> | It looks like rich markup |
| 00:58 | <JonathanNeal> | Yea, IE6 devtool says "<BODY class=st>" |
| 00:59 | <JonathanNeal> | Or is this IE's way of reading an XML document? |
| 00:59 | <GPHemsley> | it's an HTML document that's tagged as XML for debugging purposes |
| 01:00 | <GPHemsley> | (if the Content-Type header is ignored, then it should output as HTML; otherwise, it should output as XML) |
| 01:00 | <GPHemsley> | but I'm really just interested in what the text actually looks like |
| 01:00 | <GPHemsley> | (i.e. the charset/encoding) |
| 01:00 | <GPHemsley> | based on your description, it seems to be ISO-8859-3 |
| 01:01 | <GPHemsley> | (-2 would be accented letters, -5 would be Cyrllic) |
| 01:01 | <GPHemsley> | s/letters/Latin/ |
| 01:01 | <GPHemsley> | utf-8 would be Japanese |
| 01:01 | <GPHemsley> | Cyrillic, that is |
| 01:01 | <GPHemsley> | (for -5) |
| 01:03 | <GPHemsley> | JonathanNeal: How does IE treat this? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml%20plain |
| 01:03 | <boogyman> | GPHemsley: IE10 wants to open the file |
| 01:03 | <JonathanNeal> | Just a moment. |
| 01:03 | <JonathanNeal> | IE6 wants to open the fie. |
| 01:03 | <GPHemsley> | boogyman: Which? web test? |
| 01:03 | <JonathanNeal> | *file |
| 01:04 | <JonathanNeal> | Same with IE7 and IE8. |
| 01:04 | <boogyman> | web test = dl, xml/plain = view source |
| 01:04 | <GPHemsley> | boogyman: Does that mean it treats it as XML? (I don't know what that looks like in IE.) |
| 01:05 | <boogyman> | seems to believe there's a <pre> around the contents |
| 01:07 | <GPHemsley> | ah, like Safari |
| 01:07 | <GPHemsley> | gotcha |
| 01:07 | <GPHemsley> | boogyman: How does it treat this? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/whatever |
| 01:09 | <boogyman> | http://i44.tinypic.com/auth6b.gif SS |
| 01:09 | <boogyman> | text/whatever = dl |
| 01:10 | <GPHemsley> | boogyman: What about this? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml%20charset=ISO-8859-3 |
| 01:10 | <boogyman> | xml tree without styling |
| 01:10 | <GPHemsley> | Ah, OK, that looks like XML |
| 01:10 | <boogyman> | oops, sorry that's Fx |
| 01:11 | <boogyman> | text/xml = <pre> encapsulated |
| 01:11 | <GPHemsley> | Hixie: Thanks to you, that link makes Safari do plaintext with an ISO-8859-3 charset ^^ |
| 01:11 | <GPHemsley> | boogyman: Japanese? |
| 01:11 | <boogyman> | yup |
| 01:11 | <GPHemsley> | k |
| 01:12 | <boogyman> | well, i assume the characters are japanese |
| 01:12 | <boogyman> | 文書の etc. |
| 01:12 | <GPHemsley> | yeah, if it looks Japanese, assume it is |
| 01:12 | <GPHemsley> | (I know what the other encodings that I'm giving you look like) |
| 01:13 | <GPHemsley> | (and they don't look like Japanese) |
| 01:13 | <GPHemsley> | -3 has unknown characters, -2 has accented Latin, -5 has Cyrillic |
| 01:13 | <GPHemsley> | and utf-8 is Japanese |
| 01:16 | <GPHemsley> | boogyman: What about this? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml;charset=%22 |
| 01:17 | <boogyman> | <pre> with Japanese characters |
| 01:17 | <GPHemsley> | and this? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml;charset=%22;charset=ISO-8859-3 |
| 01:17 | <boogyman> | same |
| 01:18 | <GPHemsley> | and this <pre> differs from what you showed in the screenshot? |
| 01:19 | <boogyman> | the </body> is inline, opposed to the screenshot where it's on a new line |
| 01:22 | <GPHemsley> | does it get colored? |
| 01:25 | <boogyman> | is what colored? |
| 01:27 | <GPHemsley> | what you're calling <pre> |
| 01:28 | <GPHemsley> | (the screenshot you showed me is colored, and represents an XML parsing) |
| 01:28 | <boogyman> | correct, all markup like tags are colored |
| 01:29 | <GPHemsley> | ah, ok, then that's XML |
| 01:30 | <boogyman> | ah |
| 01:31 | <boogyman> | okay, then substitute all <pre> remarks with xml representations |
| 01:36 | <MikeSmith> | so, looking at http://mathiasbynens.be/notes/safari-reader , the Reader-ifiable requirements that matjas reverse-engineered and describes there seem pretty arbitrary and some even bizarre |
| 01:39 | <MikeSmith> | e.g., "Every paragraph should have at least 100 characters." |
| 01:41 | <MikeSmith> | " Readability then loops through all these ‘paragraphs’ and assigns a score to them based on how ‘content-y’ they look. This score is determined by things like the number of commas, class names used in the markup, etc." |
| 01:42 | <MikeSmith> | the number of commas? |
| 01:45 | <TabAtkins> | zcorpan: How much bridge text needs to exist between the Syntax spec and the CSSOM? That is, what do you need me to define about how to produce a CSSOM tree from a "stylesheet" as produced by the Syntax spec? |
| 01:47 | <GPHemsley> | TabAtkins: Did you see my suggestion about re-registering text/css? |
| 01:47 | <TabAtkins> | GPHemsley: Yeah. What would I need to do? |
| 01:48 | <GPHemsley> | TabAtkins: Follow the instructions here: http://tools.ietf.org/html/rfc6838 |
| 01:49 | <GPHemsley> | (Like HTML, etc., include a registration form in the spec and let IANA know about it.) |
| 01:49 | <TabAtkins> | kk |
| 01:49 | <GPHemsley> | (section 4 down) |
| 02:02 | <JonathanNeal> | MikeSmith: yea, it's pretty bad. |
| 02:08 | <MikeSmith> | Hixie: I think maybe the validator.nu/Mozilla HTML parser wasn't up-to-date yet with the current HTML spec for <menuitem> anyway, but instead parsed it per the way Mozilla had unilaterally implemented it before you actually specced it |
| 02:10 | <MikeSmith> | hsivonen: I wonder if you've noticed in difference in load on bugzilla.validator.nu/html5.validator.nu now that the HTML4+Schematron stuff is no longer happening |
| 02:50 | <GPHemsley> | Feedback welcome: http://mimesniff.spec.whatwg.org/#parse-a-mime-type |
| 03:37 | <MikeSmith> | GPHemsley: nice |
| 03:38 | <MikeSmith> | GPHemsley: "whitespace character" is as defined in the HTML spec? |
| 03:46 | <SimonSapin> | GPHemsley: do you expect this to be used for data: URLs? |
| 03:49 | <SimonSapin> | I suppose we could do the percent-decoding before calling this algorithm, and not worry too much about it |
| 03:50 | <SimonSapin> | Assume that there isn’t much content that does funny percent-encoding of MIME delimiters in their data: URLs |
| 04:54 | <kochi> | MikeSmith: ping? |
| 04:57 | <MikeSmith> | kochi: here now |
| 04:57 | <MikeSmith> | got your message |
| 04:57 | <MikeSmith> | lemme change the assignee now |
| 04:57 | <MikeSmith> | one minute |
| 04:58 | <MikeSmith> | kochi: btw I been in Matsumoto this week |
| 04:58 | <MikeSmith> | I'll be back in Tokyo on Saturday |
| 04:59 | <MikeSmith> | kochi: OK, changed the default assignee now |
| 05:00 | <kochi> | MikeSmith: thanks! |
| 05:00 | <MikeSmith> | cheers |
| 05:00 | <kochi> | and one question: one of my colleagues want to have a write access to shadow DOM spec. who to consult? |
| 05:00 | <MikeSmith> | me |
| 05:00 | <MikeSmith> | is that colleague a member of the WebApps WG already? |
| 05:00 | <kochi> | ok, i'll let him contact you. |
| 05:01 | <kochi> | maybe not. I'll forward what I did to join WG. |
| 05:01 | <MikeSmith> | every member of the WebApps WG has push access to that spec |
| 05:01 | <MikeSmith> | but I can add people manually too |
| 05:01 | <MikeSmith> | so just e-mail the info if you want me to add somebody |
| 05:01 | <kochi> | I see. I remember I got approval to join WG by TV Raman, but you can also do, right? |
| 05:02 | <MikeSmith> | yeah |
| 05:02 | <kochi> | i see |
| 05:02 | <MikeSmith> | but the person at least needs to have a W3C account/username already |
| 05:02 | <kochi> | btw, are you working there in Matsumoto? |
| 05:02 | <kochi> | is a W3C account/username different from W3C bugzilla account? |
| 05:03 | <MikeSmith> | yeah, they are two different accounts |
| 05:03 | <MikeSmith> | and yeah I am working here in Matsumoto] |
| 05:04 | <kochi> | heh, but enjoy staying there! |
| 05:05 | <kochi> | MikeSmith: btw, you may find *him* in http://dena.com/recruit/students/internship/techstudig2013.html |
| 05:06 | <JonathanNeal> | Sometimes I look at the sectioning elements in print, and I just about give up http://desktoppub.about.com/od/newsletters/a/newsletter_part.htm |
| 05:15 | <JonathanNeal> | The anatomy of an <hgroup> in print seems to be: Headline, the H1. Kicker, the H2 coming before the H1, Hammer/Slammer, the H2 coming before the H1, but styled larger, Hammer being block, Slammer being inline. Deck, the H2 coming after the H1 (or the P in a SUBLINE). |
| 05:20 | <kochi> | MikeSmith: According to http://www.w3.org/Consortium/activities DOM working group is no longer active, usually DOM related issue is handled in WebApps WG? |
| 05:21 | <kochi> | I know www-dom ML is good place to discuss any DOM issues, though |
| 05:22 | <kochi> | mm, http://www.w3.org/DOM/Activity has the answer to that. |
| 05:25 | <zewt> | the web died a horrible death the day it allowed pages to play audio without asking permission from the user |
| 05:25 | <zewt> | murderous raging hatred |
| 05:36 | <JonathanNeal> | zewt: when was this? 1996? |
| 06:11 | <MikeSmith> | kochi: yeah WebApps WG is where DOM-related work is now |
| 06:12 | <MikeSmith> | kochi: (sorry for delay in replying -- I stepped away for a bit) |
| 06:17 | <kochi> | MikeSmith: np, thanks! |
| 07:42 | <hsivonen> | MikeSmith: I deployed earlier this week. Let's see how it goes |
| 08:04 | <zcorpan> | TabAtkins: i haven't looked into hooking in to css-syntax yet. however, my hunch is that you can use abstract concepts like "declaration" and i can hook into that from cssom |
| 08:06 | <darobin> | mounir: I got replies from the GitHub team, they're on the issue |
| 08:08 | <SimonSapin1> | zcorpan: Syntax defines things like "A declaration has a name, a value which consits of a list of component values, and an "important" flag." |
| 08:08 | <zcorpan> | SimonSapin: yeah |
| 08:09 | <zcorpan> | so the text in the beginning saying that the output is a CSSOM tree seems like a lie, since it's not defined in terms of CSSOM objects |
| 08:10 | <SimonSapin> | yeah, I sent a comment that maybe Syntax should not mention CSSOM at all |
| 08:12 | <zcorpan> | if we need to keep CSSCharsetRule for compat, css-syntax needs to have an object for it in its output |
| 08:14 | <SimonSapin> | it does, "parse a stylesheet" will have a corresponding at-rule in the list of rules it returns |
| 08:15 | <SimonSapin> | although this parsed at-rule does nothing, so I’m still convinced that it shouldn’t appear in the OM |
| 08:19 | <zcorpan> | ah, right, i thought it was stepped over after sniffing it or some such |
| 08:22 | <annevk> | the parser should build CSSOM objects I think |
| 08:25 | <kochi> | MikeSmith: We got a comment from Microsoft about IME API spec, and the comment included recommendation for whatwg inputmode attribute. |
| 08:25 | <zcorpan> | there are several ways we can define things. either css-syntax is the central place where all css features are listed (it would need to be aware of the features to generate the right CSSOM objects instead of generic objects like now) |
| 08:25 | <kochi> | MikeSmith: where is it best to discuss inputmode spec? |
| 08:25 | <zcorpan> | or CSSOM is the central place that is aware of all css features |
| 08:26 | <zcorpan> | or it's distributed across all the specs that define the relevant feature to say what CSSOM object it maps to (and maybe define the CSSOM interface, too) |
| 08:26 | <Ms2ger> | Mm, DE |
| 08:26 | <zcorpan> | or a combination of these |
| 08:27 | <zcorpan> | in HTML, the DOM interface of an element is defined where the element is defined, and the parser is aware of the element if it needs special parsing |
| 08:28 | <zcorpan> | CSS doesn't need special parsing though |
| 08:29 | <Ms2ger> | I'd say it doesn't make sense to implement the interface without the feature or the other way around, so it makes more sense to define them together |
| 08:29 | <zcorpan> | yeah |
| 08:32 | <MikeSmith> | hsivonen: OK, great |
| 08:33 | <MikeSmith> | kochi: a good place to discuss inputmode is on the whatwg mailing list |
| 09:06 | <mounir> | darobin: good news |
| 09:06 | <mounir> | though, I will have no more excuse to slack :( |
| 09:08 | <asmodai> | So I was working on some Selenium tests and noticed that I had tests working for Chrome/Firefox, yet failing for PhantomJS. Tracked it down to doing a (mistaken I think) get_attribute('label') call on an option element. FF en Chrome gave back what the visible text would be. PJS gave an empty string. Did I manage to grab an UA-internal attribute for the element in the case of FF/Chrome? |
| 09:19 | <darobin> | mounir: they haven't fixed it just yet, so enjoy the slacking while you can! |
| 09:33 | <asmodai> | Interesting, fiddling with some JavaScript myself on the same element gives me only id, value, selected. Wonder if Web Driver gets some additional information from the browser with the getElementAttribute() call. |
| 09:44 | <kochi> | MikeSmith: thanks! i was away. |
| 10:13 | <andyjpb> | hi peeps |
| 10:13 | <andyjpb> | I'm looking at http://wiki.whatwg.org/wiki/IRC |
| 10:13 | <andyjpb> | what is the rationale for this not being an HTTP header like the other cross origin policy stuff? |
| 10:14 | <jgraham> | Wrong link? |
| 10:14 | <tomasf> | IRC being an HTTP header? |
| 10:15 | <andyjpb> | oops |
| 10:15 | <andyjpb> | http://wiki.whatwg.org/wiki/Meta_referrer |
| 10:17 | <jgraham> | abarth: ^ |
| 10:17 | <jgraham> | (I guess he is asleep though) |
| 10:17 | <jgraham> | (so you might want to wait 6 hours or so) |
| 10:17 | <andyjpb> | It's ok.. I have all day |
| 10:17 | <andyjpb> | ;-) |
| 10:18 | <jgraham> | One common reason for preferring meta over http headers is that they are relatively easy to add |
| 10:19 | <andyjpb> | ...or forget to add ;-) |
| 12:06 | <darobin> | MikeSmith: were you involved in setting up some of the test media files like http://media.w3.org/2010/05/sound/sound_5 ? |
| 12:10 | <Ms2ger> | darobin, that was plh |
| 12:10 | <darobin> | Ms2ger: ah, ok, thanks |
| 12:10 | <Ms2ger> | http://www.w3.org/mid/1273815461.31439.19.camel@chacal |
| 12:11 | <darobin> | thanks, that's helpful |
| 12:11 | <Ms2ger> | Np |
| 12:11 | <darobin> | one of those is 160MB — I'm not entirely convinced we need that :) |
| 12:13 | <jgraham> | Sometimes having large resources can be helpful for certain tests |
| 12:13 | <jgraham> | It's always nice if they aren't large static files though |
| 12:13 | <jgraham> | Need a bot here that can give messages when people reconnect |
| 12:18 | <darobin> | do you know what the examples directory is for at the root of the test repo? |
| 12:18 | <darobin> | because the big file is only needed for that |
| 12:18 | <jgraham> | Ask plh |
| 12:18 | <Ms2ger> | Nothing |
| 12:19 | <jgraham> | Although I think Ms2ger's answer is correct |
| 12:19 | <jgraham> | Pretty sure only plh has added stuff there, and that if he wants to continue his idea of having a collection of examples it should go elsewhere |
| 12:23 | <darobin> | ok, thanks |
| 12:23 | <darobin> | because most of the big files are referenced from there |
| 12:23 | <darobin> | so I'll just ignore those |
| 12:29 | <MikeSmith> | darobin: was not involved in setting those up |
| 12:30 | <darobin> | MikeSmith: thanks, Ms2ger traced it to plh for me |
| 12:31 | <MikeSmith> | ah ok |
| 12:35 | <darobin> | mmmm |
| 12:36 | <darobin> | I wonder if I should've used the submission/ prefix for these PRs, even though they're not submissions |
| 12:36 | <darobin> | anyway: I just made PRs to 1) add a license, and 2) switch the media to local |
| 13:41 | <asmodai> | After some confusion on my part earlier today, I found out that it seems PhantomJS doesn't adhere to the specs (unless I still misunderstood things): https://github.com/ariya/phantomjs/issues/11365 |
| 13:42 | <SimonSapin> | How related are W3C document licensing and the patent policy? https://lists.w3.org/Archives/Member/w3c-ac-forum/2013AprJun/0267.html (Member only link, sorry) |
| 13:44 | <SimonSapin> | can’t we have both open licensing and and patent policy? |
| 13:44 | <annevk> | read the reply |
| 13:46 | <hsivonen> | I’m [redacted] that [redacted] [redacted] [redacted] in the Member space of the W3C. |
| 13:46 | <asmodai> | lol |
| 13:49 | <SimonSapin> | damn, I fell right into the FUD |
| 13:52 | <annevk> | @w3cwtf tweeting it should give you a hint too |
| 13:52 | <SimonSapin> | yeah |
| 13:54 | <darobin> | SimonSapin: you're not the only one who thinks there may be something fishy with that argument :) |
| 13:56 | <SimonSapin> | one more reason I’m glad I picked this side |
| 14:03 | <jgraham> | Member space is good for giving a nice place to post the crazy without being ridiculed in public |
| 14:04 | <Ms2ger> | That's not exactly accurate |
| 14:04 | <Ms2ger> | We still ridicule in public |
| 14:05 | <SimonSapin> | by the way, who’s behind @w3cwtf? |
| 14:06 | <Ms2ger> | No comment |
| 14:06 | <SimonSapin> | that was quick :) |
| 14:15 | <GPHemsley> | MikeSmith: I haven't yet decided how to define "whitespace character" because I haven't decided whether to treat the MIME type as a byte sequence or a string of characters. |
| 14:16 | <GPHemsley> | SimonSapin: The intention is to use it anywhere that MIME types appear. I have to add the caveat that protocol-specific handling would have to be done first. |
| 14:20 | <gsnedders> | Hixie: thx for like actually mentioning this (at some point I'm gonna have to sit down and make sure we actually match the spec in html5lib…) |
| 14:20 | <gsnedders> | Hixie: And that's going to be painful. |
| 14:23 | <jgraham> | gsnedders: BTW asserting that all tag names/attribute names/values are strings in the treewalker broke stuff |
| 14:23 | <jgraham> | Well, broke end users |
| 14:23 | <jgraham> | s/strings/unicode/ |
| 14:24 | <jgraham> | Because they would parse a tree, do something like document.body.appendChild(document.createElement("foo")) |
| 14:24 | <jgraham> | and then the document wouldn't serialize |
| 14:27 | <gsnedders> | jgraham: So I guess we just need to rely on implicit unicode conversion there, lovely. |
| 14:28 | <darobin> | yay baby fucking yay! |
| 14:28 | <darobin> | \o/ |
| 14:28 | darobin | solved the PHP configuration problem |
| 14:29 | <Ms2ger> | Are you sure? |
| 14:29 | <darobin> | turns out that Debian adds its own layer of fuckedupness atop the ample doses of moronitude provided by Apache and PHP |
| 14:29 | <darobin> | Ms2ger: not in general, just for w3c-test.org |
| 14:30 | <darobin> | well, that's just hour upon hour of my life that I'm not getting back |
| 14:45 | <gsnedders> | jgraham: So the question is then how do we decode everything to unicode using the default encoding on Python 2 and raise TypeError on Python 3 without ugly hacks. |
| 14:45 | gsnedders | wonders if u"" + u"abc" causes an allocation |
| 15:01 | <mounir> | kochi: ping |
| 15:36 | <GPHemsley> | Anyone have IE handy? |
| 15:36 | <GPHemsley> | http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml;%22=;charset=iso-8859-3%20%22=iso-8859-5 |
| 15:37 | <JonathanNeal> | At least User Agent Strings are starting to calm down… not |
| 15:37 | <JonathanNeal> | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.20 Safari/537.36 OPR/15.0.1147.18 (Edition Next) |
| 15:38 | <GPHemsley> | JonathanNeal: You always seem to appear right after I say something that might be relevant to you |
| 15:38 | <GPHemsley> | (in this case, it's another IE request) |
| 15:38 | <JonathanNeal> | Go for it. |
| 15:38 | <GPHemsley> | http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml;%22=;charset=iso-8859-3%20%22=iso-8859-5 |
| 15:40 | <SimonSapin> | fwiw, I found http://www.modern.ie/en-us/virtualization-tools#downloads pretty strig |
| 15:40 | <SimonSapin> | pretty straightforward |
| 15:40 | <JonathanNeal> | Okay, in Chrome it appears like an xml doc, text/xml. Same in IE6,7,8, except the Japanese is just squares. |
| 15:40 | <zewt> | jeez, google can be outright disgraceful sometimes |
| 15:41 | <GPHemsley> | SimonSapin: Yeah, I'm looking at that now, actually. I'll get it set up eventually :P |
| 15:41 | <zewt> | code.google.com/p/android/issues/detail?id=10076 "can you document this?" closed by design "but can you document this?" two years later "hey guys this is still not documented can you document it" their solution: ticket flagged to not allow comments |
| 15:41 | <zewt> | problem solved! |
| 15:42 | <GPHemsley> | JonathanNeal: It's that square thing that I'm interested in. That suggests it uses -3. |
| 15:42 | <GPHemsley> | Which makes my life more difficult |
| 15:42 | <GPHemsley> | perhaps |
| 15:43 | <GPHemsley> | JonathanNeal: What about this? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml;%22charset%22=iso-8859-3 |
| 15:44 | <JonathanNeal> | Little squares. |
| 15:44 | <JonathanNeal> | Almost every time I see little squares. |
| 15:44 | <JonathanNeal> | (almost every time you share one of these links) |
| 15:45 | <GPHemsley> | squares means it's using iso-8859-3 encoding |
| 15:45 | <GPHemsley> | (-5 would be Cyrillic characters) |
| 15:45 | <GPHemsley> | that's intriguing |
| 15:45 | <GPHemsley> | in this case |
| 15:47 | <GPHemsley> | JonathanNeal: and this? http://whatwg.gphemsley.org/tests/mimesniff/sniffing.php?ct=text/xml;%22charset=iso-8859-3 |
| 15:49 | <SteveF> | JonathanNeal: http://lists.w3.org/Archives/Public/public-html/2013May/0164.html |
| 15:51 | GPHemsley | happens to think that <hgroup> and <subline> can coexist |
| 15:52 | <JonathanNeal> | Checking |
| 15:52 | <GPHemsley> | For example, <subline> could also be associated with an <hgroup> |
| 15:53 | <GPHemsley> | Hixie: I wonder if you should treat singleton headers as having an implicit hgroup, barring explicit ones? |
| 15:53 | <JonathanNeal> | IE6-8, little squares. |
| 15:53 | <GPHemsley> | s/barring/except when there are/ |
| 15:53 | <JonathanNeal> | Wish there was a control so I could see something other than squares. |
| 15:53 | <GPHemsley> | The squares are replacement/missing characters |
| 15:53 | <GPHemsley> | if you want, change -3 to -5 |
| 15:53 | <GPHemsley> | then you'll get Cyrillic |
| 15:57 | <JonathanNeal> | Nice, SteveF! |
| 16:00 | <JonathanNeal> | In traditional news print, there were at least four different ways of marking up the elements of a header. http://i.imgur.com/jwcBObk.png I am glad to see the web normalizing these, based on content rather than appearance. |
| 16:00 | <GPHemsley> | oh wow, this IE virtualization is pretty neat |
| 16:05 | <GPHemsley> | JonathanNeal: Oh, apparently I was wrong. In this case, the squares mean utf-8 |
| 16:09 | <Hixie> | MikeSmith: 0.89% for 8000 pages vs 1%-10% for 1-10 billion pages is well within the margin of error for the former, so that is quite consistent data. |
| 16:10 | <Hixie> | MikeSmith: makes sense (re <menuitem>) |
| 16:11 | <JonathanNeal> | SteveF: what does zero or more div/p elements mean? |
| 16:12 | <Hixie> | GPHemsley: not sure what you mean re implicit <hgroup> |
| 16:12 | <JonathanNeal> | I can't say I've seen a restriction on the content of an element like that. |
| 16:12 | <Hixie> | JonathanNeal: what kind of content goes in each of those parts of the header? |
| 16:13 | <GPHemsley> | Hixie: If any occurrence of a <hN> occurs outside of an explicit <hgroup>, assume an implicit <hgroup> around it |
| 16:13 | <GPHemsley> | Hixie: Then <subline> can be associated with an hgroup |
| 16:13 | <Hixie> | JonathanNeal: (btw, the spec tries to distinguish between "header" and "heading", where the former is a variety of things including navigation, and the latter is specifically what should appear in the table of contents) |
| 16:13 | <Hixie> | GPHemsley: not sure what you mean by "assume an implicit" |
| 16:13 | <GPHemsley> | Hixie: Like if <tbody> is missing, for example |
| 16:13 | <Hixie> | oh in the parser? |
| 16:14 | <JonathanNeal> | Hixie: googling any of those key words usually brings up one or another example, http://desktoppub.about.com/od/newsletters/a/newsletter_part.htm http://www.uiowa.edu/~c019136/136s5online17/hedjargon.html http://behindbylines.wordpress.com/2013/02/13/journalist-lingo-confusion-cleared/ |
| 16:14 | <GPHemsley> | sure |
| 16:14 | <Hixie> | that's a non-starter, we'd break a ton of the Web |
| 16:14 | <Hixie> | lots of CSS assumes there's no <hgroup> there |
| 16:14 | <GPHemsley> | is tbody explicitly exposed to the styling when it's not there? |
| 16:15 | <JonathanNeal> | GPHemsley: I think so, yes? |
| 16:15 | <GPHemsley> | oh, hm |
| 16:15 | <Hixie> | GPHemsley: it's in the DOM, so yes |
| 16:15 | <GPHemsley> | m |
| 16:16 | <Hixie> | JonathanNeal: are "hammer" and "slammer" the same thing, or two things? |
| 16:17 | <JonathanNeal> | Hixie: much like early HTML, the names are synonymous with their styling. |
| 16:18 | <JonathanNeal> | kicker is before and diminutive. |
| 16:19 | <JonathanNeal> | rather, kicker is before and lesser in importance than the headline. |
| 16:19 | <JonathanNeal> | hammer is before and stronger in importance than the headline. e.g kicker is small and hammer is big. |
| 16:19 | <JonathanNeal> | Slammer is before and stronger in importance, but inline with the headline. |
| 16:19 | <Hixie> | are there web sites styled this way i could look at? |
| 16:19 | <Hixie> | all these examples seem to be about print |
| 16:20 | <Hixie> | cnn for example doesn't seem to use this style |
| 16:20 | <JonathanNeal> | Exactly, my original point was that I'm glad the web has normalized these. However, probably due to the original constraints of the web, most of these ceased to exist online. |
| 16:20 | <Hixie> | it's more <hgroup>-like |
| 16:20 | Ms2ger | wonders if Hixie meant these slammers: http://derek.broox.com/photo/closet-cleaning/full/11163/pog-slammers.jpg |
| 16:20 | <JonathanNeal> | The deck is about the only thing that survives. |
| 16:20 | <JonathanNeal> | And I've seen it mislabeled as a byline, by Twitter Bootstrap for instance. |
| 16:21 | <Hixie> | the deck isn't part of the heading, it's just a paragraph |
| 16:21 | <Hixie> | can be part of the header |
| 16:21 | <Hixie> | but that's a separate issue |
| 16:21 | <JonathanNeal> | The deck is what we think of as the hgroup's h2-6, or the subline. |
| 16:21 | <Hixie> | oh? in http://www.cnn.com/interactive/2013/05/us/sutter-walk-oklahoma/ what would you say is the deck? |
| 16:21 | <JonathanNeal> | The deck isn't necessarily a paragraph, it can be just a part of a sentence. |
| 16:21 | <Hixie> | oh, wait, i'm confusing the deck and the lede |
| 16:22 | <Hixie> | yeah the deck is just the h2 in the hgroup |
| 16:22 | <JonathanNeal> | In your example, according to traditional print, the <h2> is the heading. |
| 16:23 | <Hixie> | both the h1 and the h2 are the heading |
| 16:23 | <Hixie> | that page is actually a perfect example of what hgroup was designed for |
| 16:23 | <Hixie> | it perfectly wraps the h1/h2 |
| 16:23 | <JonathanNeal> | But the <h2> could also be the deck. It would be contextual with the styling of the newspaper as a whole. As writers who care about the meaning regardless of style, we're left to guess. |
| 16:24 | <Hixie> | imho <hgroup> is quite well-designed -- it fits right into how authors actually write pages today, it just paves a cowpath |
| 16:24 | <Hixie> | i don't understand why it's controversial |
| 16:24 | <JonathanNeal> | Based on the source, "Walking the path of a tornado" is the headline. Based on appearance and print tradition, "A journey into the heart of a 17-mile storm" is the heading. |
| 16:25 | <JonathanNeal> | *headline |
| 16:25 | <Hixie> | they're both the heading |
| 16:25 | <JonathanNeal> | Yes, they are. |
| 16:25 | <JonathanNeal> | A deck is also a headline. |
| 16:26 | <Hixie> | anyway, gotta head out, meeting. bbiab. |
| 16:26 | <Hixie> | if someone could explain why hgroup is controversial while i'm away, please do, i'll read the scrollback :-) |
| 16:26 | <JonathanNeal> | But on the web, we've tried to learn from and distinguish content better than print. |
| 16:27 | <JonathanNeal> | Hixie: I would say http://www.w3.org/html/wg/wiki/ChangeProposals/hgroup does a pretty good job. |
| 16:48 | <annevk> | Hixie: btw, you're behind in commits, @WHATWG has more followers than you have commits these days |
| 16:49 | <GPHemsley> | (isn't that kind of the goal?) |
| 16:50 | <annevk> | only take me serious when needed GPHemsley :p |
| 16:52 | <GPHemsley> | hgroup has structural semantics, subline has content semantics |
| 16:53 | <GPHemsley> | I'm telling you, they're different things |
| 17:09 | <JonathanNeal> | Another good example of headline elements in print http://www.tameri.com/dtp/elements.html |
| 17:12 | <GPHemsley> | I would argue the CNN article mentioned earlier should use <hgroup> |
| 17:13 | <GPHemsley> | when it comes to a news article, <hN> and <hgroup> should be in headlinese |
| 17:14 | <GPHemsley> | <subline> should be in full sentences |
| 17:15 | <GPHemsley> | <hgroup> should be used if you could alternatively put a colon between the headers |
| 17:15 | <GPHemsley> | s/headers/<hN>s/ |
| 17:15 | <GPHemsley> | So, for the CNN article, "Walking the path of a tornado: A journey into the heart of a 17-mile storm" |
| 17:16 | <JonathanNeal> | We're both trying to distinguish content from the body of an article / section / page, right? |
| 17:17 | <JonathanNeal> | If you've got a moment, GPHemsley, I want to get us on the same page, and then work from there. |
| 17:17 | <GPHemsley> | abstractly, yes |
| 17:19 | <GPHemsley> | we're trying to put the right content into the right buckets |
| 17:36 | <GPHemsley> | http://i.imgur.com/5vsMypV.jpg |
| 17:37 | <GPHemsley> | <subline> is better for those |
| 17:39 | <GPHemsley> | subline p:first-child { font-weight: bolder; } |
| 17:41 | <GPHemsley> | <subline> is like a pseudo-hgroup; it's a header that's not a header |
| 17:41 | <GPHemsley> | (maybe use it for pull quotes, too) |
| 17:42 | <TabAtkins> | zcorpan: Okay, cool, I'll remove mentions of CSSOM. |
| 17:43 | <TabAtkins> | SimonSapin: Syntax could remove the @charset rule from the input stream if necessary. |
| 17:43 | <GPHemsley> | hmm... actually, this paper only uses bold on the first one if there's more than one |
| 17:43 | <GPHemsley> | I wonder how you could style that... |
| 17:45 | <GPHemsley> | (it's almost as if it's the header of the subline...) |
| 17:46 | <GPHemsley> | oh, maybe subline > header |
| 17:46 | <GPHemsley> | though that's less automated |
| 17:46 | <GPHemsley> | SteveF: Thoughts? |
| 17:47 | <SteveF> | GPHemsley: not a lot at the mo, am reading in between wrangling kids and preparing dinner |
| 17:47 | GPHemsley | wonders why extensions refer specifically to HTML5 when they plan to be versioned separately (or won't make it into HTML5.0) |
| 17:47 | <GPHemsley> | SteveF: Ah, OK; wasn't sure you were here |
| 17:49 | <SteveF> | GPHemsley: yeah here lurking |
| 17:49 | <GPHemsley> | SteveF: In particular, I think your Dr. Strangelove examples should actually use hgroup too |
| 17:50 | <GPHemsley> | because "Or: How I Learned to Stop Worrying and Love the Bomb" is most certainly part of the title |
| 17:52 | <SteveF> | GPHemsley: the why not use a single hx? |
| 17:52 | <GPHemsley> | Because it's a secondary part of the title |
| 17:54 | <SteveF> | GPhemsley: I can do the same with a span and display:block in h1 |
| 17:54 | <GPHemsley> | http://pastebin.mozilla.org/2458800 |
| 17:55 | <GPHemsley> | but that doesn't give it semantic substance |
| 17:56 | <GPHemsley> | JonathanNeal: Thoughts? |
| 17:57 | <JonathanNeal> | I like it. I'm writing up something similar, myself. |
| 17:59 | <GPHemsley> | You should be able to remove all <subline> elements from an <article> and still be able to comprehend the contents |
| 17:59 | <GPHemsley> | I think |
| 18:00 | <GPHemsley> | you can't do that for <hN> or <hgroup> |
| 18:00 | <SteveF> | GPhemsley: this is what is supposed to be convyed to assitive tech http://pastebin.mozilla.org/2458803 don't see any differentiation there |
| 18:01 | <SteveF> | GPHemsley: as per the implementation pushed by hixie |
| 18:01 | <GPHemsley> | Is that so? Because that's not what I would expect |
| 18:01 | <SteveF> | GPhemsley:what would you expect? |
| 18:02 | <GPHemsley> | To me, <hgroup> means "these headings all refer to the same section", not "these are all the same heading" |
| 18:03 | <SteveF> | GPhemsley: thats not how the acc layer is specced |
| 18:03 | <GPHemsley> | well, then perhaps that is the problem, Hixie? |
| 18:03 | GPHemsley | wonders how long the meeting is |
| 18:04 | <GPHemsley> | normally, a new <hN> element implicitly creates a new section |
| 18:04 | <GPHemsley> | <hgroup> prevents that from happening |
| 18:05 | <GPHemsley> | at least, according to my intuitive understanding |
| 18:05 | <GPHemsley> | it doesn't make any heading level any different from what it is stated as |
| 18:06 | <GPHemsley> | like I said earlier, it should be treated like a colon separator |
| 18:07 | <GPHemsley> | (the Strangelove example is a little different, since it explicitly uses "or", but still) |
| 18:08 | <SteveF> | GPHemsley: "HGROUP elements are essentially equivalent to headings that contain multiple "paragraphs" (in the sense defined in the HTML specification). They should be conveyed as such to accessibility tools. This means setting the "heading" role on the HGROUP element, and treating the Hx elements in the HGROUP element the same way as paragraphs are treated normally. " http://wiki.whatwg.org/wiki/C |
| 18:08 | <SteveF> | hange_Proposal_for_ISSUE-129#Bug_10592:_Request_regarding_the_ARIA_role_of_heading_elements_inside_HGROUP_elements |
| 18:09 | <JonathanNeal> | Here's my mud to the mix. https://gist.github.com/jonathantneal/5672276 |
| 18:09 | <GPHemsley> | ah, hmm |
| 18:09 | <SteveF> | GPHemsley: from horses mouth |
| 18:09 | <SteveF> | anyway sorry gotta go for real witll read scrollback |
| 18:10 | <SteveF> | laters |
| 18:11 | <GPHemsley> | JonathanNeal: I think the kicker/hammer/slammer concept is a bit complex |
| 18:12 | <GPHemsley> | I'm also not sure whether bylines should go in <subline> |
| 18:12 | <GPHemsley> | (and I'm also not sure about having out-of-order <hN>s in <hgroup>) |
| 18:13 | <GPHemsley> | so that's about half your document that I'm not sure about :P |
| 18:14 | <JonathanNeal> | It's food for thought. I think the limitations of web have created this bias. |
| 18:14 | <JonathanNeal> | Just like you might find it weird to have multiple sublines http://prosintraining.com/gateway/wp-content/themes/CherryTruffle/timthumb.php?src=http://prosintraining.com/gateway/wp-content/uploads/2010/03/headline.gif&h=200&w=200&zc=1 |
| 18:15 | <GPHemsley> | that third one seems like a deck |
| 18:16 | <JonathanNeal> | And here's a kicker http://unix.temple.edu/~susanj/design/new/kicker.jpg http://unix.temple.edu/~susanj/design/new/kicker2.jpg |
| 18:16 | <JonathanNeal> | and another kicker http://www.osu.edu/assets/brand/unitid-kicker.png |
| 18:16 | <JonathanNeal> | Alive and well in print. |
| 18:17 | <GPHemsley> | yeah, I'm down with having a kicker |
| 18:17 | <GPHemsley> | I just don't know if this is the appropriate place for it |
| 18:17 | <JonathanNeal> | But kickers are reverse order <hN>s in an <hgroup>. |
| 18:17 | <GPHemsley> | Are they? They seem more like categories to me |
| 18:18 | <JonathanNeal> | How would you mark those up? http://desktoppub.about.com/od/glossary/g/Kicker.htm |
| 18:19 | <GPHemsley> | well, that's why I said it was more complex — I'm not sure :P |
| 18:19 | <GPHemsley> | we could have <supline> |
| 18:20 | <GPHemsley> | but we're kind of blurring the line between style and semantics |
| 18:20 | <GPHemsley> | keep in mind that one kicker could apply to multiple articles |
| 18:21 | <GPHemsley> | (e.g. in "Nation" and "World" sections, where the state/country is in the kicker) |
| 18:24 | <TabAtkins> | annevk: What ever happened with the XML5 or MicroXML or Error-Tolerant XML or whatever effort? |
| 18:24 | <JonathanNeal> | Looking at the example provided earlier, <hgroup> and/or <subline> answer http://www.cnn.com/interactive/2013/05/us/sutter-walk-oklahoma/ addressing the headings and bylines. |
| 18:24 | <Ms2ger> | TabAtkins, nobody cares enough to implement it, I guess |
| 18:24 | <TabAtkins> | annevk: Asking because one of our implementors is starting an experiment with just using the HTML parser (in foreign content mode) for standalone SVG, just like SVG-in-HTML currently uses. |
| 18:25 | <JonathanNeal> | <hgroup> alone does not, if we think bylines should matter to outline / accessibility. |
| 18:26 | <JonathanNeal> | Ha, http://www.concordmonitor.com/readerservices/informationalpages/5618276-95/web-headline |
| 18:28 | <GPHemsley> | JonathanNeal: Was that an agreement, then? (I can't tell) |
| 18:28 | <JonathanNeal> | I'm not agreeing that we're blurring the line between semantics and style. I'm just referring to the usage of lesser headings that come before main headings. |
| 18:29 | <JonathanNeal> | Especially those that catagorize the heading, where it's "beforeness" is clearly there for meaning more than style. |
| 18:30 | <GPHemsley> | I'm just not clear on what you mean in reference to the CNN article |
| 18:30 | <GPHemsley> | (which has no kicker, AFAICT) |
| 18:30 | Ms2ger | kicks this conversation already |
| 18:30 | <GPHemsley> | :) |
| 18:31 | <GPHemsley> | JonathanNeal: To me, anything in <hgroup> should be in a document outline; if it shouldn't be in a document outline, then it shouldn't be in <hgroup> |
| 18:33 | <JonathanNeal> | Stuff that belongs in <header> but not <hgroup>, yes. |
| 18:33 | <JonathanNeal> | I guess a kicker could be a <p> in a <header> above an <h1> |
| 18:33 | <GPHemsley> | that sounds relatively reasonable |
| 18:34 | <GPHemsley> | (though it certainly loses its semantic value) |
| 18:34 | <JonathanNeal> | Exactly, that later part is why I've liked <subline> |
| 18:34 | <GPHemsley> | right |
| 18:35 | <nimbu> | TabAtkins: pingping |
| 18:35 | <JonathanNeal> | Except, I think <subline> should be liberal, so it can address kickers as well as decks. Then again, I also think <hgroup> should be liberal, and accept out of order <hN>, like "Lord of the Rings" and "The Return of the King". |
| 18:35 | <GPHemsley> | <header><subline class="kicker">...</subline><hgroup class="headline">...</hgroup><subline class="deck">...</subline></header> |
| 18:36 | <GPHemsley> | yeah, perhaps we need a better name than "subline" |
| 18:36 | <GPHemsley> | IDK |
| 18:37 | <GPHemsley> | JonathanNeal: Also, I'm not necessarily arguing against out-of-order <hN>s in <hgroup>; I was just stating that I don't think they're currently allowed |
| 18:37 | <GPHemsley> | your example is a good one |
| 18:37 | <GPHemsley> | I suppose |
| 18:37 | <GPHemsley> | depending on what you were trying to focus on |
| 18:47 | <tantek> | could someone here who is *not* a W3C member / invited expert see if they can access this? https://www.w3.org/2002/09/wbs/33280/html-charter-2013-2/results |
| 18:48 | <tantek> | just trying to double-check its W3C member-only-ness |
| 18:54 | <svl> | tantek: I get a basic authentication request for "W3CACL" (so can't access it) |
| 18:56 | <tantek> | thanks svl - that was what I was wondering. |
| 19:09 | <TabAtkins> | nimbu: pomg |
| 19:10 | <TabAtkins> | tantek: Just turn on your incognito mode or whatever when you need to check that stuff. |
| 19:10 | <tantek> | thanks TabAtkins - good work around - except some IP blocks are whitelisted as from members |
| 19:10 | <TabAtkins> | tantek: Oh, interesting. I didn't know that. |
| 19:11 | <tantek> | e.g. for example, *anyone* inside Microsoft's corpnet can access W3C member resources |
| 19:11 | <tantek> | wouldn't surprise me if the same thing was true for Google's internal net |
| 19:11 | <TabAtkins> | It's not. |
| 19:11 | <tantek> | it's also true inside Apple's internal net |
| 19:12 | <tantek> | TabAtkins - next time you're at a WG meeting of any sort at a W3C member company, try it out |
| 19:13 | <tantek> | suffice it to say, sometimes hosting companies "accidentally" give WG members internal net access, probably trusting them on the honor system |
| 19:13 | <tantek> | (and assume all traffic is logged obv) |
| 19:17 | <gsnedders> | jgraham: I wonder if we should ask the Bleach guys if they want to maintain the sanitizer… |
| 19:35 | <jgraham> | gsnedders: Well the thought had crossed my mind |
| 19:36 | <jgraham> | But it doesn't solve the problem that it's fundamentally broken |
| 19:38 | <gsnedders> | jgraham: In what way? That it's designed for the tokenizer? |
| 19:39 | <jgraham> | That it tries to deal with two different types of input as if they were the samewhen they are not |
| 19:40 | <jgraham> | Or "yes" |
| 19:48 | <jgraham> | tantek: I thought W3C had stopped doing the ip whitelist thing |
| 19:51 | <tantek> | jgraham - really? as of when? |
| 19:52 | <jgraham> | Well it stopped working at Opera a couple of years ago iirc |
| 19:52 | <jgraham> | Possibly Microsoft are more special, I don't know |
| 19:58 | <Hixie> | GPHemsley: that seems to be a print thing. Does that kind of thing happen on the Web? |
| 19:58 | <Hixie> | gsnedders: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21308 indicates tests that html5lib needs |
| 20:06 | <JonathanNeal> | GPHemsley: http://i.imgur.com/bAueHbF.png |
| 20:10 | <Hixie> | <header> <p class="category">Today in WWW</p> <h1> <strong> <h?>: </strong> Why writing headlines is too hard </h1> <p>Unsure of what to use, developers are now fighting over semantics.</p> </header> <p>It was... |
| 20:14 | <TabAtkins> | +1 |
| 20:37 | <tantek> | jgraham - perhaps Opera changed their network provider and someone forgot to tell someone at W3C they had new IP addresses. |
| 20:37 | <tantek> | easily could be one of the things that falls through the cracks |
| 21:04 | <Hixie> | can someone come up with a case where in the HTML parser, generating a </dd> when you've seen a <dd> and are going through the in-body steps for "dd", will not cause the earlier <dd> to be closed as we hoped before adding foreign content lands? |
| 21:12 | <JonathanNeal> | Same with bylines, in the <header>? |
| 21:13 | <JonathanNeal> | <h1>The Chronicals of Naria <strong>The Lion, The Witch, and the Wardrobe</strong></h1> ? |
| 21:13 | <Hixie> | that one is just an <hgroup> |
| 21:14 | <Hixie> | <hgroup> <h1>The Chronicals of Narnia</h1> <h2>The Lion, The Witch, and the Wardrobe</h2> </hgroup> |
| 21:14 | <Hixie> | or actually |
| 21:14 | <Hixie> | even without the hgroup |
| 21:14 | <Hixie> | since it's actually a site header followed by a page header |
| 21:14 | <Hixie> | so just <h1>The Chronicals of Narnia</h1> <h2>The Lion, The Witch, and the Wardrobe</h2> |
| 21:21 | <JonathanNeal> | Hixie: it's a category for the heading, but not the main heading. |
| 21:21 | <JonathanNeal> | Think, <h2>Flower of the Day</h2><h1>Roses</h1> |
| 21:26 | <Hixie> | then <hgroup> <h2>Flower of the Day</h2><h1>Roses</h1></hgroup>, probably? |
| 21:27 | <Hixie> | i'm not familiar with that style on the web |
| 21:29 | <JonathanNeal> | Interesting, does the <header> accomplish the same thing as <hgroup> or is HGTV getting it a little off? http://www.hgtvgardens.com/perennials/flower-of-the-day-delphinium |
| 21:29 | <TabAtkins> | <header> doesn't do anything to the outline algorithm. |
| 21:29 | <JonathanNeal> | Or rather http://viewsource.in/hgtvgardens.com/perennials/flower-of-the-day-delphinium#L316-318 |
| 21:45 | <JonathanNeal> | Awesome http://2.bp.blogspot.com/-PrFpbT8fQoo/TwnGjeJSUqI/AAAAAAAAAWc/Sn7mjr-BZ1I/s1600/IMG_0565.JPG |
| 21:47 | <JonathanNeal> | I would say that the way the web works has made it harder for websites to implement kickers and reverse order <hgroup> stuff, which is why we see less of them in the wild. The fact that decks and bylines survive is a testimony of their importance as an element of communication. |
| 21:48 | <Hixie> | JonathanNeal: come now, it's trivial to fake it with <div>s and <span>s |
| 21:49 | <JonathanNeal> | or <p>s |
| 21:49 | <JonathanNeal> | I guess the subject was made less trivial when <hgroup> was introduced. |
| 21:51 | <JonathanNeal> | What i mean by that is, for me the subject was made less trivial. Sorry, I'm still shaking bad communication habits. |
| 21:55 | <JonathanNeal> | gsnedders: do you still work on the outliner? |
| 21:57 | <JonathanNeal> | Do sections without headings inherit the headings of their parent, or are they considered Untitled, like http://gsnedders.html5.org/outliner/process.py?url=http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#the-title-attribute |
| 21:57 | <TabAtkins> | untitled |
| 21:59 | <JonathanNeal> | The OCD I went through with <nav>... |
| 21:59 | <JonathanNeal> | I was hoping it might inherit. |
| 22:00 | <TabAtkins> | It seems like that would usually be a bad idea. |
| 22:00 | <Hixie> | that would make little sense :-) |
| 22:00 | <TabAtkins> | I mean, literally putting the same <hn> element into the subsections would almost certainly be wrong. |
| 22:02 | <JonathanNeal> | For a <nav> element, this has been frustrating. |
| 22:04 | <JonathanNeal> | I often see <header><h1/><h2/><nav/><p/></header> working similarly as an <hgroup>, except that it doesn't according to spec. |
| 22:06 | <JonathanNeal> | Where many <hn> elements are merged similar to <hgroup>, and I can expect anything in <header> to be header material for the article. |
| 22:06 | <Hixie> | well if the <h1> is a site header and the <h2> a page header, that's fine |
| 22:07 | <Hixie> | it's only a problem if there's a later <h2> that's supposed to be a subheading of the <h1>/<h2> combo |
| 22:07 | <Hixie> | as opposed to just the <h1>, at the same level as the earlier <h2> |
| 22:07 | <JonathanNeal> | <header><h2>Flower of the Day</h2><h1>Roses</h1></header><h2>Their Beautiy</h2><p/><h2>Their Color</h2><p/><h2>Their Grace</h2><p/> |
| 22:08 | <Hixie> | that's clearly bogus, yes |
| 22:08 | <Hixie> | since it is the same as <section><h1>Flower of the Day</h1></section> <section><h1>Roses</h1> <section><h1>Their Beauty</h1></section> <section.../> <section.../> </section> |
| 22:22 | <JonathanNeal> | Can you see what it is trying to be? |
| 22:30 | <JonathanNeal> | Well, that's not the kind of question or discussion you like to have, I know. |
| 22:31 | <Hixie> | it's presumably trying to be |
| 22:31 | <TabAtkins> | If you replaced <header> with <hgroup>, that would be a correct implementation of what they're trying to do. |
| 22:31 | <Hixie> | <hgroup><h1>Flower of the Day</h1><h2>Roses</h2></hgroup> <section><h1>Their Beauty</h1></section> <section.../> <section.../> |
| 22:31 | <Hixie> | or |
| 22:32 | <Hixie> | <hgroup><h2>Flower of the Day</h2><h1>Roses</h1></hgroup> <section><h1>Their Beauty</h1></section> <section.../> <section.../> |
| 22:32 | <JonathanNeal> | I suspect <hgroup> is better than <h1>Lord of the Rings <strong>The Two Towers< strong> <small>A Book Review</small></h1> |
| 23:08 | GPHemsley | cries over tag soup |
| 23:55 | <tantek> | I found a site that uses longdesc - web comic CSSquirrel, e.g. http://cssquirrel.com/comic/?comic=107 |
| 23:56 | <tantek> | longdesc="http://www.cssquirrel.com/comicscripts/script102.htm"; |
| 23:56 | <tantek> | which … 404s |
| 23:56 | <tantek> | sigh |
| 23:56 | <TabAtkins> | Yeah, he uses it solely to disprove the "nobody uses longdesc correctly" argument. |
| 23:56 | <tantek> | TabAtkins - uh, you mean to *prove* ? |
| 23:57 | <tantek> | also goes to show no one is viewing it - because no one has reported it - because he hasn't fixed it. |
| 23:57 | <TabAtkins> | Hahaha, nice. |
| 23:57 | <tantek> | although I guess I just viewed it - by viewing the source |
| 23:57 | <tantek> | doing some analysis on comic markup |
| 23:57 | <tantek> | you know, for #indiewebcamp |
| 23:57 | <tantek> | just in case I wanted to publish a comic on my own site |
