| 14:32 | <matthiasr> | about r2220 <http://lists.whatwg.org/htdig.cgi/commit-watchers-whatwg.org/2008/001395.html>; - I don't think this is right. -wap-input-format replaces <input format=, not inputmode= |
| 14:33 | <matthiasr> | at least if http://www.developershome.com/wap/wcss/wcss_tutorial.asp?page=inputExtension2 is correct |
| 14:33 | <matthiasr> | inputmode is about something else, namely initializing the input on mobile/restricted devices |
| 14:34 | <matthiasr> | e.g. http://www.w3.org/2004/CDF/TestSuite/WICD_CDR_WP1/test-xhtml-basic11.xhtml |
| 14:36 | <matthiasr> | http://www.w3.org/TR/xforms/#mode-syntax |
| 14:39 | <matthiasr> | or have I gotten it all horribly wrong? |
| 16:06 | <MikeSmith> | matthiasr: -wap-input-format also is about initializing the input on keyboard-less mobile devices |
| 16:06 | <MikeSmith> | e.g., ones that only have 5-way keypads |
| 16:06 | <MikeSmith> | but it's also about specifying the datatype of the input |
| 16:06 | <MikeSmith> | -wap-input-format is basically poorly designed and overengineered |
| 16:07 | <matthiasr> | but I don't think it covers all cases of inputmode |
| 16:07 | <MikeSmith> | nothing covers all cases of inputmode |
| 16:07 | <MikeSmith> | but it doesn't matter, but no browsers actually support inputmode anyway |
| 16:08 | <MikeSmith> | inputmode is a pipe dream that only exists in a spec |
| 16:08 | <MikeSmith> | there are not production browsers that implement support for it |
| 16:08 | <matthiasr> | :( |
| 16:09 | <MikeSmith> | for better or worse, -wap-input-format is the only thing that's actually supported in browsers that are actually preinstalled on keyboard-less mobile devices |
| 16:09 | <matthiasr> | (and there will never be, if it's not specified) |
| 16:09 | <MikeSmith> | inputmode is specified |
| 16:09 | <MikeSmith> | in XHTML 1.1 |
| 16:09 | <MikeSmith> | the reason that it's not been implemented is that there has been no market demand for it |
| 16:10 | <MikeSmith> | it's not for lack of people trying to convince browser vendors to implement it |
| 16:15 | <matthiasr> | so it's basically been removed because no implementation cared about it anyway? |
| 17:35 | <MikeSmith> | matthiasr: it wasn't removed.. it was part of XHTML 1.1, not XHTML 1.0 |
| 17:37 | <MikeSmith> | and if they had been using the current criteria we are using now for determining when some feature can be included in an Recommendation, inputmode comes nowhere even close |
| 17:38 | <MikeSmith> | that is, lacking any implementations, it would not be included in a Recommendation |
| 17:38 | <MikeSmith> | lacking any an test cases that demonstrate it worked interoperably, it would never have made it out of CR |
| 18:27 | <henrikbjorn> | i have a dl where the dt's arent the most descriptive in the world, and my solution atm. for accessability is to hide there more descriptive part of the dt in a span. But i was wondering if theres a attribute or aria or something i could use for the more descriptive text |
| 18:28 | <henrikbjorn> | or maybe the title attribute is enough ? |
| 21:34 | <abernier> | hi |
| 21:35 | <abernier> | is a header necessarily within a section element, or can I set a header inside a <li> ? |
| 21:38 | <abernier> | In a resume, I've got an 'Experiences" section where I list different experiences in a <ol>, and for each of them, I've got a title (job) and a date so I'd like to group them into a <header> but I wonder if it is correct doing this directly within the <li> ? |
| 21:41 | <nimbupani> | a header is necessarily within a sectioning element. |
| 21:41 | <abernier> | nimbupani: ok, thanks |
| 21:41 | <nimbupani> | abernier: http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#sectioning-content |
| 21:43 | <abernier> | so for work experiences : <ol><li><section><header>{job title} {date}</header>{description}</section></li>...</ol> seems ok? |
| 21:50 | <abernier> | and is there something to markup a range of dates, eg: from April 08 to may 09 ? |