Last Call for Comments on Media Queries Level 4
The CSS WG has published its hopefully last Working Draft of Media Queries Level 4.
Media Queries allow authors to test and query values or features of the user agent or display device, independent of the document being rendered. They are used in the CSS @media rule to conditionally apply styles to a document, and in various other contexts and languages, such as HTML and Javascript.
Level 4 extends and supersedes the features defined in Media Queries Level 3. It brings significant improvements on the syntax, and a shift from using media types to finer-grained media features.
This is the last call for comments, as we plan to request a transition to CR at the end of June unless issues are brought up or anyone specifically requests more time for review.
Significant changes since Media Queries 3 are listed in the Changes section.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([mediaqueries-4]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2017-05-17
- Resolved: Request PR for Writing Modes.
- Those who had done a review generally thought the proposal for the interaction of the ‘inherit’ keyword and ::first-line (comment here) sounded sane, but conversation will continue on github to handle specifics and get more opinions.
- Resolved: Close issue (any-hover can’t be used to detect mixed hover and non-hover capable pointers) no change.
- Resolved: Mark the various hover and pointer things as at-risk.
- Resolved: Push scripting media query values to L5.
- Resolved: New WD of media queries 4.
- Resolved: Change the title to subsequent. (In reference to better terminology for ~ sibling combinator: GitHub issue)
- Resolved: Request PR on Selectors 3.
- Resolved: Accept the spec text proposed here (Should negative scroll-padding be allowed?)
- There will be a request for publication of Scroll Snap next week.
- Resolved: FPWD of Overflow 4
Full Minutes
Minutes Telecon 2017-05-03
- Moving specs toward REC:
- Writing Modes: fantasai will confirm that the proposed edits are okay.
- Fonts: Myles has finished changing the test font.
- Values & Units: fantasai will confirm the DoC is ready for republication.
- Transforms: Rossen will ask Bogden to help smfr with edits.
- Resolved: FPWD of Logical Properties with a short name of css-logical
- There was a lot of browser interest in achieving compatibility on scrollbar styling since it’s used widely enough that it can’t be removed. smfr had an explainer of the implementation that the Edge folks will review to see what additional information would be needed to make a compat spec, which would likely be added to CSS UI4. Anything extending beyond compat will be deferred until working group members have a better understanding of what’s out there now.
- The issue on defining/standardizing
line-height: normal (issue here) needs to be resolved before the issue on avoiding accidental double spacing (issue here) can be resolved. myles will write a test font to help make the test cases for line-height: normal more robust.
- fremy will file a bug on the appropriate browsers for the flex-shrinking propagating back down the flex chain issue (issue here)
- Resolved: Move gradient midpoint to Images L3.
- Resolved: Add the x unit to
resolution type in Values & Units 4.
- Resolved: Revert the edit to image-set in CSS Images.
Full Minutes
Minutes Telecon 2017-04-12
- Moving specs to REC:
- There is a goal to take Writing Modes to PR at the F2F next week, so anyone with interest was asked to review the DoC & Implementation Report in advance of the meeting.
- Some of the changes were made to the Fonts 3 test font, the rest will be made soon.
- The SVG breakout call made it through most of the Transforms topics that needed SVG input.
- Resolved: Allow
text-justify:none to apply to inlines.
- Resolved: Only spec the unitless 0 quirk for transforms & gradients.
- Resolved: Add proposed DOM load events to Values & Units.
- The proposed solution is lh includes calculation of line-height-step and if lh is used in line-height-step property, it refers to unadjusted line-height property. The group will resolve once the formal spec text is available.
- Resolved: Push fallback alignments to L4.
- Resolved: Safe & unsafe keywords ordered before alignment keywords.
- Resolved: Drop
justify-content:baseline.
Full Minutes
Minutes Telecon 2017-04-05
- The inaugural call between the CSSWG and those interested in SVG will be 6 April at 9pm UTC.
- Moving specs to REC:
- Fonts 3: Myles was actioned to make the changes to the test font requested by ChrisL and Rossen.
- Cascade 3: The edits to drop scoped styles were made.
- Values & Units: smfr was actioned to review the
position edits.
- Resolved: Update motion draft on TR
- Resolved: Meeting Houdini Aug 1, CSS Aug 2-4 in Paris
- Resolved: Move everything with no implementation to next level and mark everything with 1 implementation as at risk (in reference to Images 3).
- Everyone agreed that limiting the name space in
grid-row-start was bad and should be avoided in the future. Unfortunately, it is too late to fix this issue.
- Resolved: No change on issue 1137 (Grammar of grid-row-start and friends is ugly and harms value space for line names)
- Resolved: Have column-span elements create a bfc even if not in a multi-col container.
- Resolved: Create a WICG repo for this new feature (scroll-boundary-behavior) and work there for now.
Full Minutes
Minutes Telecon 2017-03-29
- Resolved: FPWD of fill-stroke as level 3
- Resolved: Republish Conditional Rules CR update
- Moving specs to REC:
- Fonts 3: ChrisL requested some help getting the test font to work in Edge and Firefox. The decisions on what to move into Level 4 are blocked on the test font issue.
- Cascade 3: Some tests have been added, Microsoft is working on adding more.
- Conditional Rules: The edits around CSSOM will wait until during or after the F2F.
- Values & Units: Publication is waiting on review of the
position changes. Review was requested over the next week.
- Background and Borders: The implementation report from tmichel had 82% passage. 20 of the tests had problems so he’ll fix them and re-run the tests.
- Transforms: fantasai is preparing an agenda before scheduling a conference call with SVG folks.
- Flexbox: Open items will be added to the agenda. gregwhitworth is working to understand what tests are currently in the test suite.
- CSS UI: The open pull requests have been reviewed and those that needed changes are ready for re-review.
- Resolved: Republish updated WD of css-align-3
- Resolved: Add leaverou as co-editor for CSS Images
- Resolved: New WD publication for CSS Images 4
- Resolved: Update shortname to css-images-4
- Resolved: column-spans create a formatting context, not a specific one
- Issue 1074 (definition of `column-span` should say what happens without an ancestor multicol) was discussed, but no resolution was reached.
- Originally a few people believed that the logical behavior would be to retain the formatting context as the author laid out the context with the assumption that it establishes a new formatting context.
- However, it was then brought up that this is inconsistent with how other layout modes like flexbox and grid work.
- These two sides couldn’t agree on the best solution during the course of the call, so conversation will continue on github.
Full Minutes
Minutes Telecon 2017-03-22
- Moving specs to REC:
- Cascade 3: fantasai reported that there are edits that need to be made. gregwhitwoth with port the Microsoft tests into the test suite.
- Conditional Rules: dbaron & zcorpan need to incorporate edits.
- Values & Units: Approval for the edits will be added to next week’s agenda.
- Background and Borders: There are working group approved edits that need to be made to the spec and then have a republish. tmichel will put together an implementation report.
- Transforms: About half the open issues need feedback from people who have worked on SVG. smfr will reach out members of the old SVG working group to set up a call, perhaps during the old SVG telecon time. smfr will need assistance in evaluating the test suite.
- Flexbox: Open items are actively being discussed on telecons (including today) and after that there will be a republication ask. gregwhitworth and/or gsnedders will evaluate the test suite coverage.
- CSS UI: astearns and fantasai will split the work of reviewing the tests Florian submitted.
- Resolved: Publish FPWD for CSS Paint
- Resolved: Short name is fill-stroke with a title of Fill and Stroke
- Though there was agreement that the use case in issue 401 was broken by the change, the group felt that the change was throughly considered and still the right choice.
- Resolved: No change on issue 401
- fremy will open bugs on those browsers that do not conform to spec when sizing images with intrinsic aspect ratio. These bugs will reference issue 1112 in case a behavior change is needed.
- fantasai requested more review of the flex basis and box-sizing issue to see if there’s actually a compat risk to fixing the behavior to be as intended.
- The remaining issues that need discussion will be added to next week’s agenda so that Flexbox can be republished.
Full Minutes
Minutes Telecon 2017-03-15
- Grid Issues:
- Issue #1: minmax max value
- The group agreed that the use case was valid, but that it should be solved in a different way then the proposal so that the standard min/max priority can be maintained.
- Resolved: Reject this issue for L1 of grid.
- Issue #8: dominant-baseline should apply to grid/flex containers
- Issue #16: Defer subgrid
- TabAtkins & fantasai proposed to not defer as there wasn’t a solid counter proposal.
- As the group discussed the proposal, it developed that there was a desire to get subgrid right since no implementor had yet implemented the partial proposal that was originally placed in Grid in order to encourage implementation.
- Resolved: Move subgrid to level 2 of Grid
- Issue #17: Is fr a length?
- Resolved: length & frs are not combinable, but will reconsider if/when length & auto are combinable.
- Resolved: Republish Grid
- Rossen introduced the group to the plan he and astearns developed to help the group move specs towards REC. At the beginning of each call there will be a status check for all specs that are in CR or are stable WD to see what steps have been taken to move them to REC and give authors the opportunity to request assistance. This new process will begin on either the 22 or 29 March calls, depending on progress agreeing upon the beginning list of specs to prioritize.
Full Minutes
Minutes Telecon 2017-03-08
- The suggested date for the dev meetup in Japan is either 18 or 19 April (the evening before the first F2F meeting day or the evening of the first meeting).
- There was some interest in simplifying to make
column-span apply only to direct children of the multicol element however there was also concern about headings nested in sections and similar use cases. There was a desire to find out what browsers do to see if there’s already compatibility which would also lead to adding some test cases to the test suite.
- The group was in favor of the fix to clarify segment break transformation rules when there are multiple segment breaks (available here).
- The actual definition of “form control” will defer to the HTML group’s open issue.
- Resolved: Add font-presentation to the spec and have it effect font fallback. (Accepting this proposal).
Full Minutes
CSS Basic UI Level 3 Updated Candidate Recommendation
The CSS WG has published a Candidate Recommendation and invites implementations of the CSS Basic UI Module Level 3:
This specification includes and extends user interface related features from the properties and values of CSS level 2 revision 1. It uses various properties and values to style basic user interface elements in a document.
This document is intended to be essentially complete, and pending approval of a few recently submitted tests, will have an exhaustive test suite, most of which already passes in two or more implementations. Implementors are encouraged to look through the test suite and to fix areas where they are not yet conforming. Unless this last effort uncovers some unexpected problem, this specification should to move to PR and REC relatively soon.
However, CSS-WG would like to draw attention one feature which is at risk of being postponed or dropped: Directional Focus Navigation. This feature is not implemented in any current desktop or mobile browser. One known implementation is the defunct Presto engine by Opera Software. It is also known that TV browsers, especially UAs conforming to HbbTV use this feature, but the state of these implementations is unknown. The CSS-WG encourages TV manufacturers, software vendors for these platforms, or anyone else with an implementation to get in touch, so that we can evaluate how many independent implementations there are, and how conforming they are. In the absence of this information, it is likely that this feature will be postponed.
Significant changes are listed in the Changes section.
A Disposition of comments is available.
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-ui-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
![[Photo: group photo of the CSS working group in Lyon, France]](/Style/CSS/csswg-2010.jpg)
Contact: