- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
Do You Remember Browser Vendor Prefixes?
Typically, these are prefix syntaxes that need to be added before certain experimental and non-standard CSS, such as: -webkit-, -moz-, -o-, -ms-. These prefixes are meant to allow developers to implement new CSS features in situations where the browser has not yet officially supported them. At that time, it was also common to use preprocessors like PostCSS with the autoprefixer plugin to preprocess CSS and add these prefixes, so that the website syntax could adapt to a wider range of users.
As for why browser prefixes have gradually disappeared?
The reason is that the prefixes used for testing have deviated from their original purpose — functional experimentation. With the increasing number of prefixes, things became more chaotic. Browser vendors gradually recognized that an excess of experimental prefixes could lead developers to rely on non-standardized features, which in turn affects the compatibility of websites across different browsers. Therefore, modern browsers are more cautious about introducing experimental features, ensuring that new features have sufficient completeness and cross-browser consistency before introduction, and gradually moving away from using browser vendor prefixes to test new features. Instead, they provide manual toggles within the browser or offer test versions of browsers for experimental purposes, such as Chrome Canary or Firefox Nightly.
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1