News for hackers. Stuff that matters.
Re:CSS transforms unprefixed in Firefox nightly by TazeTSchnitzel on Wednesday July 04, 2012 @03:25PM (#4200585)
Well, each of those values will only work correctly in one browser, other browsers would skip the ones they don't understand, yes?
Re:CSS transforms unprefixed in Firefox nightly by Permit on Wednesday July 04, 2012 @09:22PM (#4201367)
Because of the prefixes, yes the browser knows which properties to skip. But you were advocating removing prefixes, so I'm wondering how browser are supposed to differentiate between properties?
Re:CSS transforms unprefixed in Firefox nightly by TazeTSchnitzel on Thursday July 05, 2012 @04:32AM (#4202231)
Eh? Have you ever done, say...

  color: rgb(255, 255, 255);

  color: rgba(255, 255, 255, 0.5);
Browser which do not support rgba simply ignore it and use the rgb() value.
Re:CSS transforms unprefixed in Firefox nightly by Permit on Thursday July 05, 2012 @03:35PM (#4204584)
Wait so you want them all to use the same prefix? So you'd have five properties called "filter:" or "background-image:"?

If my gradient looked bad in Mozilla, how on earth would the I know which property to change? They'd seem identical unless I memorized every single browser specific implementation of every CSS property.

Re:CSS transforms unprefixed in Firefox nightly by TazeTSchnitzel on Thursday July 05, 2012 @03:41PM (#4204611)
Comments exist, you know.

It's not like we don't have this issue already with different versions of the same engine changing syntax.

Re:CSS transforms unprefixed in Firefox nightly by Permit on Thursday July 05, 2012 @10:38PM (#4206107)
Code should be self-documeting. You're proposing we remove something that serves to differentiate between properties in favor of simply adding the exact same information in the form of a comment.
Re:CSS transforms unprefixed in Firefox nightly by TazeTSchnitzel on Friday July 06, 2012 @06:53AM (#4207222)
Only where necessary. Where browsers do not disagree, it saves developers time and effort.
Re:CSS transforms unprefixed in Firefox nightly by emil0r on Wednesday July 04, 2012 @03:52PM (#4200666)
Now the client wonders why the website looks so different in different browsers.
Re:CSS transforms unprefixed in Firefox nightly by TazeTSchnitzel on Wednesday July 04, 2012 @04:24PM (#4200750)
Eh? Did you even read what I posted? Browsers ignore CSS they don't understand, hence you can put several versions of a rule, and a browser will use the one it understands.
Re:CSS transforms unprefixed in Firefox nightly by jonathanyc on Wednesday July 04, 2012 @05:16PM (#4200859)
How is the browser supposed to magically discern developer intent?
Re:CSS transforms unprefixed in Firefox nightly by TazeTSchnitzel on Wednesday July 04, 2012 @05:25PM (#4200878)
What do you mean? Competing syntaxes usually don't get confused by browsers as being valid.