[Bug 27933] Add private prefixes for CSS3 properties automatically in CSS processing

2013-02-10 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=27933 Daniel Friesen changed: What|Removed |Added CC||mediawiki-bugs@nadir-seen-f

[Bug 27933] Add private prefixes for CSS3 properties automatically in CSS processing

2012-11-11 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=27933 Bartosz DziewoƄski changed: What|Removed |Added CC||matma@gmail.com --- Comment #

[Bug 27933] Add private prefixes for CSS3 properties automatically in CSS processing

2012-01-13 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=27933 Antoine "hashar" Musso changed: What|Removed |Added CC||has...@free.fr --- Comment #4

[Bug 27933] Add private prefixes for CSS3 properties automatically in CSS processing

2011-03-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=27933 --- Comment #2 from Trevor Parscal 2011-03-08 18:39:46 UTC --- I was going to also point out, that there are libraries like SASS, xCSS, and Less that do meta CSS programming. Because these start from a more sanitary source, they can do tricky

[Bug 27933] Add private prefixes for CSS3 properties automatically in CSS processing

2011-03-08 Thread bugzilla-daemon
https://bugzilla.wikimedia.org/show_bug.cgi?id=27933 --- Comment #1 from Trevor Parscal 2011-03-08 18:36:31 UTC --- What's the proposed behavior when such private rules already exist neaby? I think figuring out ways to make development easier is clever and useful, but we have to be careful beca