CSS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(similar intro as DOM)
(→‎Houdini: Clarify Chrome parity is longer term than 2018)
Line 156: Line 156:
==== Houdini ====
==== Houdini ====
* [[CSS/Houdini|CSS Houdini]] - see inside for Houdini implementation thoughts/plan
* [[CSS/Houdini|CSS Houdini]] - see inside for Houdini implementation thoughts/plan
* parity with: [https://developers.google.com/web/updates/2018/01/paintapi Chrome 65 supporting CSS Paint API by default]
* working towards (longerterm than 2018) parity with: [https://developers.google.com/web/updates/2018/01/paintapi Chrome 65 supporting CSS Paint API by default]


=== Actively Implementing ===
=== Actively Implementing ===

Revision as of 09:56, 11 May 2018

CSS is short for Cascading Style Sheets (CSS), and typically includes the full set of Selectors, CSS properties, values, and @-rules supported by browsers.

CSS is one of several web standards.

For documentation on CSS, how to develop for it, use various properties, see:

CSS

Priorities

The following CSS specs/proposals are a priority.

2018 Priorities

These are *in progress* 2018 Priorities for CSS features in Firefox.

Close to shipping

These features have implementations that are already well in progress and thus it is a priority to finish them and ship.

Variable Fonts

Fonts Level 4 for Variable Fonts support in particular:

Reprioritize Fonts Level 4 accordingly once we have Variable Fonts.

Shapes

Critical Fixes

Critical fixes to features or larger specs we already support (more important than new features in general)

Multi-column

(Jen has a demo of bugs / test page at http://labs.jensimmons.com/examples/multicolumn-3-bug-demo.html)

Values and Units 3

CSS Values and Units Module Level 3 (CR) metabug

  • [ ] calc() function in particular. metabug
  • re-prioritize Values and Units 3 once calc fixes have landed.
  • [ ] attr function (at risk) — very useful in combination with CSS Shapes, in the context of a CMS

Scroll Snap update

Media Queries

2018 Medium Priorities

2018 medium priorities are "maybe" items that we're not sure we can get to in 2018, but would really like to (had a lot of interest during yallhands).

Containment

Grid Level 2

Grid Level 2 AKA subgrid (use-cases, a11y implications)

Container Queries Prerequisites

There's a lot of anecdotal demand for Container Queries / Element Queries. See replies here:

We should at least figure out what features / bug fixes we would need to address to even consider something like Container Queries (which we should also give input on)

2018 Lower Priorities

Features or areas that are lower priority based on a number of factors.

CSS Images 3

Box Alignment

  • CSS Box Alignment (WD), metabug
    • all properties for blocks (e.g. 1105571)
    • and some details for flexbox (see metabug 1105570 Depends on)
    • spec CR depends on resolving open css-align-3 issues
  • unlikely mobile impact (mobile layouts more likely to use flexbox with box alignment properties)

Inline Layout

Scrollbar Styling

Spec in editor's draft - many requests for this

text-decoration-skip

SVG properties in CSS

This bit from SVG2:

Sizing

CSS Intrinsic & Extrinsic Sizing Module Level 3 (TR WD) metabug

  • intrinsic size keywords: fix #567039 & #1055887, and unprefix (#1322780
  • medium mobile impact from height related properties

Motion Path

CSS Color Level 4

CSS Color Module Level 4 (ED), metabug

  • Color improvements (wide gamut, color correction, note CSS color correction preffed off)
  • low mobile impact (variable lighting anyway, users use of filters)

Implement correct color management of CSS colors (which is really earlier levels of CSS color).

Better Print Support

Start looking at what specs and features would significantly improve print support. Much of this is testing and bugfixing edgecases of existing features, some of it may require or benefit from new specs/features.

More specs / features in particular TBD.

Houdini

Actively Implementing

Beyond the above priorities, we should continue to actively implement, fix bugs on the following:

Flexbox

Mozilla has a pretty solid complete Flexbox (W3C CR, just waiting on feature-interaction tests to go PR) implementation. We are working on some fixes to make it even better, e.g.

Grid

3D Transforms

Masking

Text Decoration

CSS Text Decoration Module Level 3 (2013 CR) (metabug), e.g.:

Writing Modes

CSS Writing Modes Level 3 (2015 CR) (metabug)

Fonts Level 3

Wrap-up the few remaining bugs, or declare that we're done (e.g. font-variant as a descriptor?)

Under the hood and related

Evaluating

Font Rendering Controls

CSS Font Rendering Controls Module Level 1 (ED)

Font Loading

CSS Font Loading Module Level 3 https://developer.mozilla.org/en-US/docs/Web/API/CSS_Font_Loading_API shipped in 41

  • CSS Font Loading Improvements, Multiple bugs

Other

  • font inflation removed
  • CSS Transform properties (shorthands)

Related HTML5

HTML5 layout and presentation related work:

Recent CRs

Cascading and Inheritance

Upcoming CRs

These CRs are expected in 2017:

For all potential CRs:

  • Which browsers have openly announced implementations or intent to implement? (links?)
  • Box Alignment (see above)

Text Level 3

Selectors 4

Selectors 4 (need list of changes since 3), metabug

  • No explicit dependency on Stylo, just lower priority
  • Selectors4 remaining features
    • CSS ::selection fixes + unprefixing
    • ... remaining new features? (JS)

Shipping Soon

As the above priorities get implemented, moving down here to note we're waiting for them to ship.

Image Values and Replaced Content

[2] (CR)

  • image() function
  • [ ] xywh fragment syntax

Style sheet APIs for Add-ons

  • style sheet APIs in add-ons SDK / loading async APIs (to be handled by stylo)

Filter Effects Level 2

Device Adaptation

CSS Device Adaptation Module Level 1 (WD)

properties

Please add subpages for each (unprefixed) CSS property in alphabetical order.

in development

CSS properties which have not yet made it to a Candidate Recommendation (or later), or are only implemented in the wild in prefixed form.

new pseudo-classes

new properties

See Also

Retrieved from "https://wiki.allizom.org/index.php?title=CSS&oldid=1193607"