What are the worst CSS features in terms of cross-platform compatibility?

[Luke Crouch]

dev-webdev, dev-mdc,

In Q3, MDN devs started building up a new store & API for browser
compatibility data [1] to replace the current tables on the wiki.

In Q4, we started researching MDN services for 2015, and it looks like
we'll include some kind of compatibility service. [2]

So, we're converging these efforts and want to build a minimum viable
product that validates 1. technical feasibility and 2. real value for
web developers.

To focus our work, we want to know:

What are the 5-10 worst CSS features in terms of cross-browser
compatibility?

Thanks,
-L

[1]
https://bugzilla.mozilla.org/showdependencytree.cgi?id=989448&hide_resolved=1
[2]
https://docs.google.com/a/mozilla.com/document/d/1c5w87-KDZCP9eltjfk98GL_i-hyqQ193J86_e1L4wnQ/edit#

--
Q: Why is this email five sentences or less?
A: http://five.sentenc.es

[Chris Mills]

Flexbox is way up there. 2009 syntax, 2011 syntax, and “modern” syntax implementations still out there. And they are still changing the spec as we speak.


Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
cmi...@mozilla.com || @chrisdavidmills

> _______________________________________________
> dev-mdc mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdc
> MDN contributor guide: http://bit.ly/ContributorGuide

[Matthew Claypotch]

1) Flexbox (old syntax, new syntax, prefix, no prefix)
2) Gradients (better these days but still not great)
3) Transitions & Transforms (listed together because their interaction is the source of the most headaches
4) "Box Model Control"- this covers box-sizing, Firefox's inane ::-moz-focus-inner, other enemies of sizing elements sanely
5) Clipping elements (support for only raster masks in blink/webkit, only vector masks in Firefox)

Top 5 I can think of.

~potch

> dev-webdev mailing list
> dev-w...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-webdev
>

[Karl Dubost]

Luke,

Le 7 nov. 2014 à 02:14, Luke Crouch <lcr...@mozilla.com> a écrit :
> To focus our work, we want to know:
>
> What are the 5-10 worst CSS features in terms of cross-browser
> compatibility?

To be clear here you are looking for:

1. CSS features which are implemented in browser X and not in browser Y?
2. CSS features which are widely used on the Web in an incompatible way?
3. the 1, with the twist that they create serious Web Compatibility issues?



--
Karl Dubost, Mozilla
http://www.la-grange.net/karl/moz

[Luke Crouch]

We want to know what parts of CSS hurt developers most in terms of time
and effort spent making it work across browsers.

That seems most like your #1, but I would love to know all the rest too.

Is there a way to measure the others? I.e., how much broken flexbox is
out there on the web right now?

That would be incredible.

-L