DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Join us tomorrow at 1 PM EST: "3-Step Approach to Comprehensive Runtime Application Security"
Save your seat
  1. DZone
  2. Coding
  3. Languages
  4. How To Avoid Non-Standard CSS3 (And Make Great CSS Standard)

How To Avoid Non-Standard CSS3 (And Make Great CSS Standard)

John Esposito user avatar by
John Esposito
·
Feb. 14, 12 · Interview
Like (0)
Save
Tweet
Share
3.68K Views

Join the DZone community and get the full member experience.

Join For Free

Quite a few web devs reeled and fired back against a recent CSS Working Group meeting that seriously considered admitting WebKit prefixes as part of the CSS spec (1,2,,4). So far, so good: the developer community is supposed to respond to WG discussions, and the WG generally welcomes this kind of feedback.

If you're on board against the (supposed) threat of WebKit hegemony, you can certainly make your voice heard on the W3C mailing lists -- or you can just keep writing standards-compliant CSS3, avoiding

But vendor prefixes don't always indicate divergence from the standard. CSS3 modules are still under development, and much of the purpose of vendor prefixing is, simply and nobly, to ensure that experimental implementations themselves do not become set in browser-and-code stone.

So how can you avoid accidentally using a WebKit-only prefix, while still implementing experimental but standard CSS3 for WebKit browsers?

CSS guru Lea Verou offers some great advice: just Google it. Use quotes, and check only w3.org.

But you could have figured that out. You might not have enough CSS experience, however, to follow her more aggressive advice, on 'how to help standardize a feature', without reading her full discussion. 

Three things to do, in descending order of preference:

  1. Reseach standards-compliant alternatives.
  2. If there are none, then see if the feature is already proposed.
  3. If it hasn't been proposed, then propose the feature. 

The blogpost shows you exactly how to do each of these things (where to search, how to research, how to propose effectively -- emphasis on use-cases). A great supplement to Move the Web Forward, an essential resource for standards-refining web developers everywhere.

So check out Lea's longer discussion, and join the defense and advance of CSS3 standards today!

CSS

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Top 3 Challenges Facing Engineering Leaders Today—And How to Overcome Them
  • Simulate Network Latency and Packet Drop In Linux
  • Real-Time Stream Processing With Hazelcast and StreamNative
  • The Role of Data Governance in Data Strategy: Part II

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: