| 00:49 | <gsnedders> | It amuses me how so many places are reporting the omission of DVD playback from Win8 as a result of saving the patent licensing fee, when they'll almost certainly be paying the capped limit anyway. |
| 01:03 | <Hixie> | anyone care about whether you can do separators in a context menu using <hr> rather than nesting a <menu>? |
| 01:04 | <zewt> | can you explain that a little for someone who hasn't been following closely enough? |
| 01:04 | <Hixie> | <menu type=popup><menuitem ...><hr><menuitem ...></menu> |
| 01:04 | <Hixie> | vs |
| 01:05 | <Hixie> | <menu type=popup><menuitem ...><menu><menuitem ...></menu></menu> |
| 01:05 | <Hixie> | (the latter will be supported either way, the question is whether to support the former) |
| 01:06 | <boogyman> | Hixie: what semantic meaning does the <hr> provide? |
| 01:06 | <Hixie> | "separator", same as its usual meaning |
| 01:06 | <zewt> | is this about whether to support divisions (eg. separation lines) between menu items, or just about how they're marked up? |
| 01:06 | <Hixie> | just about how they're marked u |
| 01:06 | <Hixie> | p |
| 01:06 | <zewt> | ok, havn't been following enough to have a meaningful opinion on that part |
| 01:07 | <Hixie> | gut opinions are fine too, i'll just give them appropriate weight -) |
| 01:07 | <Hixie> | :-) even |
| 01:07 | <zewt> | fwiw the <menu><menu> thing looks like a submenu to me, not two items at the same depth with a separator |
| 01:07 | <Hixie> | submenu would be <menu><menu label=submenu> |
| 01:08 | <Hixie> | if there's no label it just gets inserted directly in the parent with separators on either side |
| 01:08 | <boogyman> | Hixie: I cannot think of an instance where there's semantic value in an <hr> |
| 01:09 | <Hixie> | boogyman: the case here is one |
| 01:09 | <boogyman> | that wouldn't be more appropriately classified as a separate <menu> |
| 01:09 | <Hixie> | boogyman: more generally, think of a novel where in a chapter you have an unusually large gap between paragraphs |
| 01:09 | <Hixie> | boogyman: or three stars between paragraphs |
| 01:09 | <Hixie> | boogyman: the HTML spec actually uses <hr> quite a lot |
| 01:10 | <Hixie> | anytime you see a wider than usual spacing between paragraphs, it's an <hr> |
| 01:10 | <Hixie> | see the spec for more examples :-) |
| 01:10 | <boogyman> | I understand the "power" of the separator, but why not just use creative padding/border/margins? |
| 01:10 | <Hixie> | you use both, <hr> at the semantic layer, and padding/border/margins to describe what the separator should look like |
| 01:10 | <boogyman> | Given your statements, I could see a <menu> with multi-levels, possibly |
| 01:11 | <zewt> | just off the top of my head and not a very good example, but if you want to make a plain-text rendering, it's probably much cleaner to know "<hr> means add another blank line" than trying to derive different margins |
| 01:12 | <zewt> | (whether there are any benefits for the menu case, i don't have an intuition on, yet anyway) |
| 01:12 | <boogyman> | zewt: it's really about devices like JAWS, that don't care much about cosmetics, but what the separator truly means, but Ian has provided a plausible use-case, so seems okay to me |
| 01:22 | <Hixie> | ok, ye big <menu> redesign is in |
| 01:47 | <boogyman> | hey Hixie can you refresh my memory on a semantic usecase for allowing a "block" level element inside of an anchor? |
| 01:47 | <boogyman> | i disagree with the examples in the spec |
| 02:13 | <Hixie> | boogyman: see e.g. whatwg.org's home page |
| 02:16 | <boogyman> | touche |
| 12:12 | heycam | wonders in MikeSmith's general direction whether it'd be possible to have lists.w3.org serve email attachments with non-application/octet-stream Content-Types |
| 12:13 | <heycam> | e.g. http://lists.w3.org/Archives/Public/www-svg/2012Dec/0102.html it seems to know it should be image/svg+xml... |
| 12:14 | <annevk> | heycam: if your email client is configured correctly it should just work |
| 12:14 | <heycam> | oh I mean on the web |
| 12:14 | <annevk> | heycam: that is, you can set the MIME types of the attachments and w3.org will use that |
| 12:15 | <heycam> | oh really |
| 12:15 | heycam | has never considered that it might be possible to set the type when sending the mail |
| 12:16 | <heycam> | I guess it's just the list archiving software that's guessed the type |
| 12:16 | <annevk> | maybe it forces download these days for security purposes? |
| 12:16 | <heycam> | could be |
| 12:16 | <heycam> | just slightly annoying to have to save then open |
| 12:17 | <annevk> | well lots of stuff on www-archive can be opened directly, or at least used to |
| 12:17 | <annevk> | and I think that mechanism works everywhere |
| 14:25 | <annevk> | In http://url.spec.whatwg.org/#api can I just do base = "about:blank"? |
| 18:13 | <annevk> | http://vimeo.com/48858289 |
| 18:35 | <Hixie_> | has a bug at 02:45 |
| 18:40 | <annevk> | lol what is the bug? :) |
| 18:40 | <Hixie_> | it's pretty obvious :-) |
| 18:45 | <Hixie_> | same bug around 7:08 a couple of times (non-adjacent characters) |
| 23:25 | <Hixie_> | the vimeo player is annoying. |