Mobile/Open Web/CSS

From MozillaWiki
Jump to: navigation, search

CSS Background & Borders Level 3

background-attachment: local
Status Not supported by Firefox
Parity WebKit, IE, Opera
How to detect Presence of the keyword local in the, eventually prefixed, property. There may be several keywords, comma-separated. If one is local the Web site may be broken.
# affected sites Unknown (Expected low)
Workaround TBD, not sure there is a CSS-only one (may need some JS)
Bug 483446
Evangelism status Minor issue (no report)
border-image & border-image-*
Status A previous draft is supported as -moz-border-image. A patch does exist which creates the border-image-* longhand properties and extend the shorthand syntax to make it match.


Some Web sites does work now with both WebKit & Gecko, but are broken when we add the new final syntax (and remove -moz-border-image).

border-image-repeat: space is not implemented (and of course its shorthand equivalent neither). It may adds to this problem [See its own box].

Parity Not yet, though WebKit support it (Chrome 20?)
# affected sites Significant number (748253 )
Workaround None, we are stuck.
Bug original bug (in Firefox 3.5), bug for revisions (in Firefox 15 after multiple backouts), followup bug to revisions (in Firefox 15)
Evangelism status Important issue (several apps are using this). Cannot go on release for the moment.
border-image-repeat: space
Status Not implemented (and of course its shorthand equivalent neither).
Parity  ?
How to detect Presence of the keyword space in the, eventually prefixed, property. There keyword may also appears in the shorthand background-image.
# affected sites Unknown (Expected: very low)
Workaround None
Bug 720351
Evangelism status Minor issue (no report)
background
Status Not all new CSS3 B&B background properties are allowed in the shorthand background.



570326 background-size
570896 Allows different background-origin & background-clip

Parity "unknown"
How to detect The value of background-size is preceded by a /. No other properties do this: the mere presence of a / is enough to detect it.

The values of background-origin & background-clip are one of the following: border-box, content-box & padding-box. The presence of one of these keywords, or one of the non-standard WebKit-specific equivalent (padding, border, content), is enough to detect it.

# affected sites Unknown (expected low, but to increase)
Workaround Use the longhand properties
Bug 613659, 570326, 570896
Evangelism status Minor issue (no report)
box-decoration-box
Status Not supported by Firefox. We have an old version of the spec implemented until a different names. If Web sites do use it, we should look in more details
Parity "unknown"
# affected sites Unknown (expected low)
Workaround Implement the Gecko-specific properties, but to be checked on practical cases
Bug 613659
Evangelism status Minor issue (no report)

CSS Transitions

Not yet in CR, or even in LC. Fairly good interoperability.

CSS Animations

Not yet in CR, or even in LC.

CSS Transforms

Not yet in CR or even in LC. The skew() function has been removed and may be a compatibility hazard.

CSS Values

We are ahead of WebKit (or very close), no compatibility problems right now

CSS Flexbox

The spec changes all the time right now. But the first WebKit-only website may appears. There is no work-around possible as long as we don't support flexbox (WIP)

CSS Columns

We don't support column-span and have not unprefixed. Not much in use, though.

CSS Images Level 3

linear-gradient()
Status -moz supported, patch (almost) ready to unprefix (and fix the angle). Landing the patch will break Web sites.

Note that Gecko doesn't support gradients in every properties where it should.

Parity None, nobody unprefixed it right now
# affected sites Potentially a lot
Workaround -moz + unprefixed (but we cannot ask Web devs to do that as they can't test). Maybe we should keep both syntax for a while?
Bug 752187
radial-gradient()
Status -moz supported, patch (almost) ready to unprefix (and fix the syntax). Landing the patch will break Web sites.

Note that Gecko doesn't support gradients in every properties where it should.

Parity None, nobody unprefixed it right now
# affected sites Potentially, but probably not that much
Workaround -moz + unprefixed (but we cannot ask Web devs to do that as they can't test). Maybe we should keep both syntax for a while?
Bug 752187