CSS3 property vendor prefixes

[garethjmsaunders]

Hi guys, any plans to include CSS vendor prefixes in the autocomplete and inspector lists, particularly for CSS3 properties? It's great that WeBuilder 2011 now includes CSS3 properties but it doesn't appear to include any of the vendor prefixes, e.g. -moz, -ms, -o and -webkit particularly as some of these employ slightly different syntax to the W3C properties.

Rather than relying on autocomplete or the inspector I'm having to create snippets in my library for my most frequently used properties, which is a little time consuming first hunting them down and adding them to my library in as generic a way as I can (which is a one-off activity) but then re-editing them every time I need to use them. I'm finding writing this kind of code in Aptana to be more efficient, to be honest.

I guess one solution might be to retain the W3C properties in the inspector and autocomplete, but to have an option in the preferences where you can choose whether WeBuilder also automatically includes vendor prefixed declarations too. So you could choose to include then or not, and if you wanted them you could then select which you wanted: -moz, -ms, -o and -webkit and then WeBuilder would automatically enter those in the correct order (i.e. before the W3C declaration).

Gareth

[Gatis]

Hi,

Actually you can see at least some of the CSS browser vendor prefixes. You just need to select the browser you need from the Inspector:
1) open a CSS file;
2) open Inspector from Main Menu; View; Inspector;
3) select the browser specification you need.

It seems the CSS prefixes for Firefox are missing, so I will see what can be done to fix it.

[garethjmsaunders]

Hi Gatis,

Actually you can see at least some of the CSS browser vendor prefixes. You just need to select the browser you need from the Inspector:
1) open a CSS file;
2) open Inspector from Main Menu; View; Inspector;
3) select the browser specification you need.

It seems the CSS prefixes for Firefox are missing, so I will see what can be done to fix it.

Thanks for the reply -- I can now see the prefixes, although when you say you need to select the browser required the list now seems out of date: Firefox 2, 3 and 4, Netscape 8 (?! -- that was out between 2005-2007!) and Safari 4 and 5 but no mention of Chrome, or perhaps a more generic Webkit. I'm guessing that most people won't be familiar with the subtle differences between CSS capabilities of Firefox 4 and 6, for example and might just prefer to assume they are writing for the latest version unless they could specify elsewhere

This setup just seems to me to be rather too time consuming if I want to add, say, border-radius for Firefox, Chrome/Safari and Opera to have to add one value, change the browser type in the inspector, scroll to the relevant property, add the value, change to the next browser type, etc.

What would be a nice time-saver would be, instead, a way to tell WeBuilder which browser/capabilities you are writing for on a particular project and when adding border-radius it automatically adds the appropriate vendor prefixed values, e.g.

I specify that I want border-radius 5px solid #000; and WeBuilder fills in:

border: 5px solid #000000;
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;

Just a thought. Thanks.