Comments on: Comic Update: The W3C/WHATWG Community Theater Group http://cssquirrel.com/blog/2009/07/27/comic-update-the-w3cwhatwg-community-theater-group/ opinions and news on web design Thu, 17 May 2012 05:41:57 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jin http://cssquirrel.com/blog/2009/07/27/comic-update-the-w3cwhatwg-community-theater-group/comment-page-1/#comment-26622 Jin Mon, 27 Jul 2009 21:02:27 +0000 http://www.cssquirrel.com/?p=392#comment-26622 The header/footer tags definitely drew some questions. Since I work with web apps a lot, I'm curious about the new form elements. (Mostly masked text inputs). I feel these are nice to haves, but they've already been implemented quite well using css/js. I was disappointed to see that TABLE hasn't gotten any improvement. As of now, TABLE is rather useless for displaying large tabular data(many colums, rows). I'm hopeful about the new DATAGRID tag. I hope it will have many features that TABLE lacked. The header/footer tags definitely drew some questions. Since I work with web apps a lot, I’m curious about the new form elements. (Mostly masked text inputs). I feel these are nice to haves, but they’ve already been implemented quite well using css/js. I was disappointed to see that TABLE hasn’t gotten any improvement. As of now, TABLE is rather useless for displaying large tabular data(many colums, rows). I’m hopeful about the new DATAGRID tag. I hope it will have many features that TABLE lacked.

]]> By: Kyle Weems http://cssquirrel.com/blog/2009/07/27/comic-update-the-w3cwhatwg-community-theater-group/comment-page-1/#comment-26620 Kyle Weems Mon, 27 Jul 2009 20:34:08 +0000 http://www.cssquirrel.com/?p=392#comment-26620 @Eric - With people that are so motivated to create the right spec coming from such strongly opposing viewpoints, it's no shocker that people devolve into snark at times. I can only hope that by the participants constantly reminding themselves that it is supposed to be a civil dialogue they can keep the metaphorical barbarians constantly at bay. @Jin - It's a huge dilemma, the many versus few approach. Considering the long-term impact and hoped-for lifespan of HTML5, it's hard to justify keeping the decision-makers down to a few, especially considering the far-reaching consequences of their actions on fields like accessibility. At the same time, if it's too huge there's a serious risk of paralysis. I'm just glad I'm not looked to for the solution. Regarding tags: I agree. Like, do we need both header and hgroup? Is aside actually useful in most cases, or merely a confusing tag that should be used much less frequently that in will be (sidebars)? I think I like section, but is it really more useful than div? So many questions come up about what is really needed. @Eric – With people that are so motivated to create the right spec coming from such strongly opposing viewpoints, it’s no shocker that people devolve into snark at times. I can only hope that by the participants constantly reminding themselves that it is supposed to be a civil dialogue they can keep the metaphorical barbarians constantly at bay.

@Jin – It’s a huge dilemma, the many versus few approach. Considering the long-term impact and hoped-for lifespan of HTML5, it’s hard to justify keeping the decision-makers down to a few, especially considering the far-reaching consequences of their actions on fields like accessibility. At the same time, if it’s too huge there’s a serious risk of paralysis. I’m just glad I’m not looked to for the solution.

Regarding tags: I agree. Like, do we need both header and hgroup? Is aside actually useful in most cases, or merely a confusing tag that should be used much less frequently that in will be (sidebars)? I think I like section, but is it really more useful than div? So many questions come up about what is really needed.

]]> By: Jin http://cssquirrel.com/blog/2009/07/27/comic-update-the-w3cwhatwg-community-theater-group/comment-page-1/#comment-26617 Jin Mon, 27 Jul 2009 19:47:26 +0000 http://www.cssquirrel.com/?p=392#comment-26617 Nicely done Kyle. As for the HTML5 spec group effort, like many other group efforts I've seen in the past (non tech related too) suffers from the same problem: when too many people get involved you get too many voices and directions. This essentially is a big design by committee. However, if you have one person lead it, then people would complain about that too... I think it's good to have a clearcut vision from the very start. As I was looking over the new HTML5 spec, I can't help wondering about some of the new tags: what problems are these really solving? Nicely done Kyle. As for the HTML5 spec group effort, like many other group efforts I’ve seen in the past (non tech related too) suffers from the same problem: when too many people get involved you get too many voices and directions. This essentially is a big design by committee. However, if you have one person lead it, then people would complain about that too… I think it’s good to have a clearcut vision from the very start.

As I was looking over the new HTML5 spec, I can’t help wondering about some of the new tags: what problems are these really solving?

]]> By: Erik Vorhes http://cssquirrel.com/blog/2009/07/27/comic-update-the-w3cwhatwg-community-theater-group/comment-page-1/#comment-26616 Erik Vorhes Mon, 27 Jul 2009 17:49:44 +0000 http://www.cssquirrel.com/?p=392#comment-26616 I don't post to the WhatWG list very often, but I'm afraid the list has started causing me to behave like an asshat about somewhat trivial things. It is hard to keep an honest, compassionate, friendly front up when it feels like snark pretty regularly enters the conversation. (Thanks for helping us laugh at ourselves!) I don’t post to the WhatWG list very often, but I’m afraid the list has started causing me to behave like an asshat about somewhat trivial things. It is hard to keep an honest, compassionate, friendly front up when it feels like snark pretty regularly enters the conversation. (Thanks for helping us laugh at ourselves!)

]]>