Explore >> Select a destination
|
You are here 
|
www.quirksmode.org | ||
| | | | |
hsivonen.fi
|
|
| | | | | [AI summary] The text discusses the issue of vendor-specific CSS prefixes and their impact on web development. It outlines the problems caused by prefixes, such as fragmentation and maintenance difficulties, and proposes solutions like moving towards unprefixed standards and better coordination among browser vendors. The author highlights the need for web developers to avoid creating WebKit-only sites and for browser vendors to stop supporting prefixes to promote a more unified web. | |
| | | | |
snook.ca
|
|
| | | | | Leave it to PPK to come out with a bold statement like, "CSS vendor prefixes considered harmful". Moreso, It's time to abolish all vendor prefixes. They've become solutions ... | |
| | | | |
alistapart.com
|
|
| | | | | Any -webkit- feature that doesn't exist in a specification (not even an Editor's draft) is not CSS3. Yes, they are commonly evangelized as such, but they are not part of CSS at all. This distinction is not nitpicking. It's important because it encourages certain vendors to circumvent the standards process, implement whatever they come up... | |
| | | | |
thinkdobecreate.com
|
|
| | | With the growth of native CSS features - including nesting - what features do we still gain by using Sass, and what is available to use in its place? | ||
