It??™s also worth noting that, as is
usually the case with proprietary code, the extensions will not pass CSS validation.
Vendor-specific Properties
369 Vendor-specific Properties
If you must use extensions, you should use those that are closely related to equivalent
CSS properties (be that CSS1, 2, or 3), so that you can switch to the standard property
later on, and remove the extension when the browser implements the correct
specification.
Bearing this in mind, let??™s go back a few years and take as an example the opacity
property, which is part of CSS3 (Candidate Recommendation May 2003), which
few browsers actually supported (opacity was implemented in Firefox 1.0, Opera
9, and Safari 1.2). Therefore, authors resorted to using vendor-specific extensions
to cater for the lack of CSS3 opacity support at the time. Gecko-based browsers (like
Mozilla) used the ??“moz-opacity property, and Safari 1.1 used -khtml-opacity.
Internet Explorer versions 5.5 and above used the non-standard filter property
(p.
Pages:
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535