Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
The Internet

W3C Member Proposes "Fix" For CSS Prefix Problem 144

Pieroxy writes "The W3C is proposing a set of new rules for CSS prefixing by browser vendors. This would greatly mitigate the problem caused today where vendor specific prefixing is seeing its way through production sites. The problem is so bad that some vendors are now tempted to support other browsers' prefixing. The article also has a link to an email from Mozilla's Henri Sivonen that does a nice job of addressing many potential issues and shortcomings of this new proposal." I was under the impression that browser prefixes existed to allow use of experimental CSS features before standardization; just ditching the vendor prefix seems like a step backward.
This discussion has been archived. No new comments can be posted.

W3C Member Proposes "Fix" For CSS Prefix Problem

Comments Filter:
  • Re:The solution is.. (Score:3, Interesting)

    by Anonymous Coward on Wednesday May 09, 2012 @10:32AM (#39941185)

    What we need is a more "amateur" web, where people only do the work in your first step, maybe also do the second step (test on one or more other (non-IE) browsers) which only takes a minute or two, and then say they're done -- simply blowing off the question of whether or not the site looks perfect on IE.

    You can't do that (neither can I) at our jobs but for a situation where there isn't some boss telling you "21% of our users are still using IE so the site has to look ok," then blowing off IE is simply no problem.

    I mean it's not a problem for anyone, not even the IE users, because they would either accept they're not seeing the same web as everyone else (and there's actually nothing wrong with that) or else they'd upgrade. Or, worst case, they would bitch like they always do and balkanize off to their own web and the world wouldn't miss them.

    Nobody loses, if only we had a less professional approach. "Pro" doesn't mean "better."

  • by WankersRevenge ( 452399 ) on Wednesday May 09, 2012 @12:13PM (#39942581)
    At least until the end of life of Windows XP, the role of holding everybody back falls to IE8. HTML5? No show.

    Funny ... I've been writing HTML5 for awhile now and it works fine in ie6 and up. Granted it requires conditionals and some clever use of css, but it renders fine in older browsers and modern browsers get to experience some of the latest features. And no - there is no "best viewed" anywhere in my sites. Everything just works with or without JavaScript all written in standard markup.

    It takes work, but so does anything worth doing.

It is not for me to attempt to fathom the inscrutable workings of Providence. -- The Earl of Birkenhead