Al raises a good point:
> In addition to the good explanations you've already received, there is also
> a school of thought (mine) that prefixes should not be used. Those people
> not using the default browsers that come with their OS are going to be
> keeping their Firefox, Chrome, or Opera up-to
On Tue, May 8, 2012 at 1:40 PM, Al Sparber wrote:
> On 5/8/2012 1:20 PM, meera kibe wrote:
>>
>> Hello,
>> Can someone elaborate on why all the vendor specific prefixes have to be
>> written first then the native property;
>> Thanks
>
>
> In addition to the good explanations you've already receive
On 5/8/2012 1:20 PM, meera kibe wrote:
Hello,
Can someone elaborate on why all the vendor specific prefixes have to be
written first then the native property;
Thanks
In addition to the good explanations you've already received, there is
also a school of thought (mine) that prefixes should not
On Tue, May 8, 2012 at 1:20 PM, meera kibe wrote:
> Hello,
> Can someone elaborate on why all the vendor specific prefixes have to be
> written first then the native property;
> Thanks
> Meera
> __
> css-discuss [css-d@lists.css-
Hiya Meera,
If the browser claims to have non-beta support (without the beta
prefix), then it will read that last and over-rite the previously
interpreted beta-level property. In theory, border-radius would be a
fully-functional, bugless implementation that follows the W3
specification of the same
Hello,
Can someone elaborate on why all the vendor specific prefixes have to be
written first then the native property;
Thanks
Meera
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
Li
