Comments on: Future of web standards (my take) http://friendlybit.com/css/future-of-web-standards-my-take/ You have found Friendly Bit, a web development blog. I focus on client side technologies like CSS, HTML and Javascript. You find my articles below and categories to the right. Fri, 04 Jul 2008 13:18:41 +0000 http://wordpress.org/?v=2.5.1 By: Sonali Sengupta http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30796 Sonali Sengupta Fri, 04 Jul 2008 10:46:39 +0000 http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30796 Interesting....need to check it out. Interesting….need to check it out.

]]> By: Gaurav http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30076 Gaurav Sat, 05 Jan 2008 18:41:06 +0000 http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30076 There are loads of such experimental features already. We just need some decent documentation... There are loads of such experimental features already. We just need some decent documentation…

]]> By: Blog Surfer » Linkbait: Tasty morsels to entice readers http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30038 Blog Surfer » Linkbait: Tasty morsels to entice readers Sun, 30 Dec 2007 20:42:49 +0000 http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30038 [...] Future of web standards (my take) Stuart Landridge sums up the ongoing debate about the future of CSS. My thoughts on this are that we should: 1. Let browser makers run loose with implementing new features, based on feedback from web developers. 2. Have a standard body (or some other group) that look at those existing features and see how they can be […] [...] [...] Future of web standards (my take) Stuart Landridge sums up the ongoing debate about the future of CSS. My thoughts on this are that we should: 1. Let browser makers run loose with implementing new features, based on feedback from web developers. 2. Have a standard body (or some other group) that look at those existing features and see how they can be […] [...]

]]> By: Blog Surfer » The future of friendlybit.com http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30032 Blog Surfer » The future of friendlybit.com Sun, 30 Dec 2007 16:13:30 +0000 http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30032 [...] Future of web standards (my take) Stuart Landridge sums up the ongoing debate about the future of CSS. My thoughts on this are that we should: 1. Let browser makers run loose with implementing new features, based on feedback from web developers. 2. Have a standard body (or some other group) that look at those existing features and see how they can be […] [...] [...] Future of web standards (my take) Stuart Landridge sums up the ongoing debate about the future of CSS. My thoughts on this are that we should: 1. Let browser makers run loose with implementing new features, based on feedback from web developers. 2. Have a standard body (or some other group) that look at those existing features and see how they can be […] [...]

]]> By: Goodbye 2007 - Happy New Year! - Robert’s talk http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30022 Goodbye 2007 - Happy New Year! - Robert’s talk Sat, 29 Dec 2007 21:43:18 +0000 http://friendlybit.com/css/future-of-web-standards-my-take/#comment-30022 [...] Future of web standards (my take) [...] [...] Future of web standards (my take) [...]

]]> By: Robert Nyman http://friendlybit.com/css/future-of-web-standards-my-take/#comment-29975 Robert Nyman Thu, 20 Dec 2007 09:40:45 +0000 http://friendlybit.com/css/future-of-web-standards-my-take/#comment-29975 Absolutely right. Absolutely right.

]]> By: Tobz http://friendlybit.com/css/future-of-web-standards-my-take/#comment-29974 Tobz Thu, 20 Dec 2007 00:55:49 +0000 http://friendlybit.com/css/future-of-web-standards-my-take/#comment-29974 It makes total sense to me. if browsers implement they're experimental features similarly to how they currently have some css3 features - with a prefix, eg: moz-/op-/webkit- and remove that prefix when/if that feature becomes standardized. for html elements maybe something like <operavideo src="...? It makes total sense to me.

if browsers implement they’re experimental features similarly to how they currently have some css3 features - with a prefix, eg: moz-/op-/webkit-

and remove that prefix when/if that feature becomes standardized.

for html elements maybe something like <operavideo src=”…?

]]>