| 00:22 | <SamB> | ... data URLs have fragment identifiers now? |
| 00:23 | SamB | is looking at the filter property on the logo img on http://www.whatwg.org/specs/web-forms/current-work/ ... |
| 00:24 | <Hixie> | "now"? |
| 00:27 | <qFox> | mmm in that doc, "Ian Hickson, Google, ian⊙hc" followed by "© Copyright 2004, 2005 Apple Computer, Inc., Mozilla Foundation, and Opera Software ASA.", looks kind of weird :) |
| 03:23 | SamB | wonders what the old browsers do with new tags ... |
| 03:58 | <Hixie> | SamB: depends on the element |
| 03:59 | <SamB> | Hixie: how would they know the difference between <foo> and <bar> (which is pretty much the way it would see elements with names it never heard of, isn't it?) |
| 04:00 | <Hixie> | some of the "new" elements aren't actually so new |
| 04:00 | <SamB> | ah |
| 04:00 | <Hixie> | and some of the "new" elements are void, which means that while they get treated the same as non-void in legacy UAs, there are bigger concerns for people using them now |
| 04:00 | <Hixie> | same with any elements which we've added to <head> or in other places |
| 04:00 | <Hixie> | like <template> |
| 04:01 | <SamB> | well, as it happens I was thinking of stuff like <article> and <header> and <footer> |
| 04:01 | <Hixie> | those all more or less get treated like <span> in legacy UAs |
| 04:03 | <SamB> | hmm, not quite as nice as if it were <div> but it doesn't sound terrible either |
| 04:04 | <SamB> | and it's good for things like <time> that it is the way it is, I guess |
| 04:29 | <Hixie> | it's kind of academic since we can't change what it is. it just is what it is. |
| 04:29 | <SamB> | true |
| 16:04 | <MikeSmith> | smola_: can you remind me where I can get a jar of v0.0.2 of galimatias? |
| 16:08 | <MikeSmith> | ah maven |
| 18:26 | <sicking> | Hixie: what's the use case for the inert attribute? |
| 21:01 | <Hixie> | sicking: makes it possible to "gray out" parts of the page and make them non-interactive. A lot of pages do that, e.g. as part of doing dialog-like things. |
| 21:02 | <sicking> | Hixie: i can't think of any cases where i've seen someone gray out a subsection of a page. The only thing I can think of is graying out everything exception a subsection of a page |
| 21:02 | <sicking> | Hixie: do you have examples? |
| 21:02 | <Hixie> | it's possible that all the practical use cases are just handled by <dialog>, true |
| 21:03 | <Hixie> | though iirc there were some use cases for inert="" without <dialog> |
| 21:03 | <Hixie> | i can look into it in more detail on monday if you like - file a bug? http://whatwg.org/newbug |
| 21:04 | <sicking> | Hixie: that's certainly my gut reaction (that <dialog> solves all use cases), but that's why I asked |
| 21:04 | <sicking> | i can file a bug |
| 21:05 | <Hixie> | thanks |
| 21:05 | <Hixie> | i'll look into it and if i can't find why it was added i'll remove the attribute |
| 21:05 | <Hixie> | (the attribute doesn't do much, it just hooks into the logic that exists anyway for dialogs) |
| 21:06 | <sicking> | implementation-wise I suspect that they are quite different |
| 21:06 | <sicking> | at least in Gecko |
| 21:10 | <Hixie> | really? |
| 21:10 | <Hixie> | why? |
| 21:10 | <Hixie> | i guess <dialog> can be implemented more efficiently? |
| 21:11 | <sicking> | first of all I think we could disable any checking if we don't have a <dialog> up |
| 21:12 | <sicking> | also, things like making find-as-you-type only search a subsection is easier than seach anything that isn't inert |
| 21:12 | <Hixie> | makes sense |
| 21:58 | <SamB> | so, the difference between inert= and disabled= was what again? |
| 21:58 | SamB | knows disabled doesn't DTRT, FYI |
| 22:16 | <NoodlesNZ> | Anyone here involved with the w3c github account? Seems a bunch of repos have disappeared over the weekend |