| 10:24 | <Ms2ger> | "Return the readAsText() method, but continue to process the steps in this algorithm" |
| 15:02 | <toss2> | are here any guys that work on Chrome? I have found a bug in Chrome |
| 15:38 | <aleray> | hi, does it makes sense to use wrap the content of a list page (with links to detail pages) in a section tag |
| 15:40 | <aleray> | something like this: http://dpaste.com/1506414/ |
| 15:45 | <Ms2ger> | http://qdb.us/62195 |
| 16:00 | <MikeSmith> | Hixie: see comments from Dominic Cooney and Maciej about inheriting from HTMLInputElement in http://lists.w3.org/Archives/Public/public-webapps/2013OctDec/1051.html |
| 16:01 | <MikeSmith> | another data point for why it's a bad idea to create any new elements that follow the input@type (anti)pattern |
| 16:02 | <MikeSmith> | e.g., menu@type=toolbar|popup |
| 16:42 | <annevk-cloud> | matjas: not explicitly mentioned atm |
| 16:43 | <annevk-cloud> | mostly because I need to write up the choices again I think and ask what others think |
| 17:16 | <dekiss> | how to make empty link that will not refresh the page? |
| 18:40 | <Hixie> | MikeSmith: sure, nothing new there. the problem is that it's equally bad, possibly worse in fact, to have the language be inconsistent. |
| 18:40 | <Hixie> | MikeSmith: to create new custom <input type=> values, you'd need a dedicated mechanism for it |
| 18:41 | <Hixie> | MikeSmith: closely related to, but distinct, from the mechanism for binding to other elements. |
| 18:41 | <Hixie> | MikeSmith: web controls 1.0 actually had a start of an API to do this, ten years ago |
| 20:28 | <matjas> | annevk: alright, i’ll go ahead and file a bug for it (in an attempt to keep the discussion in one place) |
| 20:28 | <matjas> | annevk: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24104 |