Comments on: Call for action on Vendor Prefixes http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/ Working together for standards Wed, 27 Mar 2013 12:19:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: addey http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78501 addey Tue, 01 May 2012 03:56:18 +0000 http://www.webstandards.org/?p=2142#comment-78501 I know most of us have little pull, if any, with the W3, but the root of the problem is them. What can we do to speed W3′s adoption of design principles? Do we need another WHATWG? I know most of us have little pull, if any, with the W3, but the root of the problem is them. What can we do to speed W3′s adoption of design principles? Do we need another WHATWG?

]]> By: Tobias http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78476 Tobias Sat, 21 Apr 2012 15:54:36 +0000 http://www.webstandards.org/?p=2142#comment-78476 What kind of programmers is developing web browsers? When ever I do something I follow the standards. I know that the people that made the standards are probably smarter than me and that's why they did something in a way that I think is insane. Every programmer should have that as a rule of thumb: Follow the standards or make a standard your self. What kind of programmers is developing web browsers? When ever I do something I follow the standards. I know that the people that made the standards are probably smarter than me and that’s why they did something in a way that I think is insane.

Every programmer should have that as a rule of thumb: Follow the standards or make a standard your self.

]]> By: Richard D. http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78469 Richard D. Wed, 18 Apr 2012 23:26:31 +0000 http://www.webstandards.org/?p=2142#comment-78469 I have implemented a change in our corporate website to supporting web standards browsers with graceful degradation for all others. We have removed the browsers and browser version we support and have replaced it with a comment that simply says we support web standards browsers. It would be fantastic if you could provide a page with a list of browsers that are deemed by you to be compliant so that we can direct users to the list. I believe this would helpful to other large corporations as well. Cheers I have implemented a change in our corporate website to supporting web standards browsers with graceful degradation for all others. We have removed the browsers and browser version we support and have replaced it with a comment that simply says we support web standards browsers.

It would be fantastic if you could provide a page with a list of browsers that are deemed by you to be compliant so that we can direct users to the list. I believe this would helpful to other large corporations as well.

Cheers

]]> By: John A. Bilicki III http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78458 John A. Bilicki III Sun, 15 Apr 2012 11:19:39 +0000 http://www.webstandards.org/?p=2142#comment-78458 No, that's the wrong approach. Telling browser vendors to do the wrong thing because people are doing things they should not? If someone isn't doing their job competently they either correct their actions or they should eventually get fired. Only using the WebKit prefix shows that the person generating the code is incompetent. Two wrongs don't make a right. No, that’s the wrong approach. Telling browser vendors to do the wrong thing because people are doing things they should not? If someone isn’t doing their job competently they either correct their actions or they should eventually get fired. Only using the WebKit prefix shows that the person generating the code is incompetent. Two wrongs don’t make a right.

]]> By: Immigration to Canada http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78394 Immigration to Canada Thu, 29 Mar 2012 08:06:09 +0000 http://www.webstandards.org/?p=2142#comment-78394 Really a informative post. I agreed that most of designers and developers are understanding the root problem is important to theorize a more permanent solutions. Really a informative post. I agreed that most of designers and developers are understanding the root problem is important to theorize a more permanent solutions.

]]> By: Kjøp Viagra http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78391 Kjøp Viagra Wed, 28 Mar 2012 14:47:07 +0000 http://www.webstandards.org/?p=2142#comment-78391 Whether you like Vendor Prefixes or not, we have a problem. Due to the rise in mobile browser usage, and many of those mobile browsers being based on WebKit, many developers have decided to essentially only use the -webkit- prefix, even for properties that have been implemented by other browsers. Today Daniel Glazman, W3C CSS Working Group Co-chairman, wrote a blog post Whether you like Vendor Prefixes or not, we have a problem. Due to the rise in mobile browser usage, and many of those mobile browsers being based on WebKit, many developers have decided to essentially only use the -webkit- prefix, even for properties that have been implemented by other browsers. Today Daniel Glazman, W3C CSS Working Group Co-chairman, wrote a blog post

]]> By: Recently in Web Development (February ’12 Edition) » Ezee2Know http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78363 Recently in Web Development (February ’12 Edition) » Ezee2Know Tue, 13 Mar 2012 04:51:45 +0000 http://www.webstandards.org/?p=2142#comment-78363 [...] Do You Exclusively Use webkit Prefixes? Now Vendor Prefixes Have Become a Problem Call For Action On Vendor Prefixes [...] [...] Do You Exclusively Use webkit Prefixes? Now Vendor Prefixes Have Become a Problem Call For Action On Vendor Prefixes [...]

]]> By: Web Developers Sound Off on WebKit Prefixes | Witty City Blog http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78355 Web Developers Sound Off on WebKit Prefixes | Witty City Blog Sat, 10 Mar 2012 15:30:07 +0000 http://www.webstandards.org/?p=2142#comment-78355 [...] Andrew of the web standards project generally agrees with Glazman writing, “once again we run the risk of having sites built only for one platform, and [will] find it [...] [...] Andrew of the web standards project generally agrees with Glazman writing, “once again we run the risk of having sites built only for one platform, and [will] find it [...]

]]> By: Stephane Deschamps http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78347 Stephane Deschamps Mon, 05 Mar 2012 20:37:04 +0000 http://www.webstandards.org/?p=2142#comment-78347 FWIW I've committed change proposals to the SVN repository that holds all the SPIP galaxy (CMS, plugins, templates). http://zone.spip.org/trac/spip-zone/changeset/59092 Message in French reads: +/* + + ATTENTION + L'usage de proprietes -webkit-* sans leurs contreparties + (-o-*, -moz-*, etc.) est fortement deconseille ! + cf. http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/ + + Prenez le temps de corriger s'il vous plait : les proprietes CSS prefixees ne sont en theorie + destinees qu'a des fins de test. + +*/ Which means: BEWARE: using -webkit-* properties without any counterpart is strongly not recommended. Take the time to correct please: prefixed CSS properties are only theoretically for testing purposes. All in all the SPIP community is very respectful of diversity: out of several tens of thousands of files, I found only a dozen lonely -webkit-* rules. :) FWIW I’ve committed change proposals to the SVN repository that holds all the SPIP galaxy (CMS, plugins, templates).

http://zone.spip.org/trac/spip-zone/changeset/59092

Message in French reads:
+/*
+
+ ATTENTION
+ L’usage de proprietes -webkit-* sans leurs contreparties
+ (-o-*, -moz-*, etc.) est fortement deconseille !
+ cf. http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/
+
+ Prenez le temps de corriger s’il vous plait : les proprietes CSS prefixees ne sont en theorie
+ destinees qu’a des fins de test.
+
+*/

Which means: BEWARE: using -webkit-* properties without any counterpart is strongly not recommended. Take the time to correct please: prefixed CSS properties are only theoretically for testing purposes.

All in all the SPIP community is very respectful of diversity: out of several tens of thousands of files, I found only a dozen lonely -webkit-* rules. :)

]]> By: TL;DR on Vendor Prefix Drama | StevenCodes http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/comment-page-1/#comment-78333 TL;DR on Vendor Prefix Drama | StevenCodes Fri, 24 Feb 2012 06:02:25 +0000 http://www.webstandards.org/?p=2142#comment-78333 [...] folks in this this ain’t good crowd: Rachel Andrew, Bruce Lawson, and Gilles [...] [...] folks in this this ain’t good crowd: Rachel Andrew, Bruce Lawson, and Gilles [...]

]]>