Implement :focus-visible so that fewer developers remove all focus styles https://www.youtube.com/watch?v=ilj2P5-5CjI

New in CSS Media Queries Level 5:
https://drafts.csswg.org/mediaqueries-5/#prefers-reduced-motion

WebKit blog post covering the feature, justification, and examples:
https://webkit.org/blog/7551/responsive-design-for-motion/

The overflow-block and overflow-inline media queries from Media queries level 4 let people tell apart media that paginate vs media that scroll or media that clip using media features instead of media types.

That way, you can do

@media (overflow-block: paged) {
/* do something smart for pagination */
}

and that will do the right thing when printing AND in ebook readers that paginate instead of scrolling, instead of

@media print {
/* do something smart for pagination */
}

which would work on print but fail in ebook readers.

The specification is over here:
https://drafts.csswg.org/mediaqueries-4/#mf-overflow-block
https://drafts.csswg.org/mediaqueries-4/#mf-overflow-inline

`display: flow-root` is a modern way to force a block to be a formatting context that floated elements are contained in (aka clearfix).

From the spec [1]:

> The element generates a block container box, and lays out its contents using flow layout. It always establishes a new block formatting context for its contents.

Tab Atkins and Elika Etemad (fantasai) from CSSWG consider the feature stable enough to be implemented [2].

[1] https://drafts.csswg.org/css-display-3/#valdef-display-flow-root
[2] https://discourse.wicg.io/t/1835/6

Other browsers support some level of CSS hints for printing to hint to the browser to use landscape over portrait, and what margins to use.

https://stackoverflow.com/questions/43755490/how-to-define-the-scale-and-letter-size-on-a-print-preview-in-microsoft-edge-or/45721616#45721616

<style>
@media print{
@page{
margin:1in;/* Default margin (for page content) */
/*margin:0in; Sets margin to zero AND hides all the page #/date/URL fluff */
size:landscape;/* Default to Landscape */
}
}
</style>

The update media query from Media queries level 4 let people tell apart media that responsively update the screen, from those that cannot, or those that can but only slowly.

Authors can use that to style things differently on print vs ebook readers, even though both media are paginated. This kind of nuance was not possible to express just with @media print {...}

The specification is over here:
https://drafts.csswg.org/mediaqueries-4/#descdef-media-update

When you're rendering to PDF, this is a vector format, so there's not actual limit on the resolution. The resolution media feature has been extended in media queries 4 to be able to express that.

https://drafts.csswg.org/mediaqueries-4/#valdef-media-resolution-infinite

See https://drafts.csswg.org/css-overflow-4/#max-lines

Chrome recently added "scroll anchoring" and Edge should too! see here for more info https://blog.google/products/chrome/taking-aim-annoying-page-jumps-chrome/ https://blog.chromium.org/2017/04/scroll-anchoring-for-web-developers.html

https://www.w3.org/TR/css-color-4/#the-hwb-notation

But there's still something missing & with vars now supported, it's more important than ever: calc in rotate/scale/for time vals.

https://developers.google.com/web/updates/2016/05/houdini

At least, Edge should offer the option which ignores 'ime-mode'.

FYI:
CSS Basic User Interface Module Level 3 (CSS3 UI)
W3C Candidate Recommendation, 02 March 2017
https://www.w3.org/TR/css-ui-3/#input-method-editor
> 6.3.2. Obsolete: the ime-mode property
> User agents should not support the ime-mode property.

Couldn't find this anywhere here, so I'll post this feature request.

I'm asking for support of the following notations:

background-color: #12345678;

and

background-color: #1234;

Spec: https://drafts.csswg.org/css-color/#hex-notation

"caret-color" has just been implemented on Chromium and Firefox. It'd be really nice if Edge can support it too.

The spec is CR: https://www.w3.org/TR/css-ui-3/#caret-color

And there are already 21 tests on the W3C csswg-test repo: http://test.csswg.org/shepherd/search/testcase/spec/css-ui-3/section/6.2.1/

The `i` flag is defined in the CSS Selectors module [1] and is supported by all the other major browser engines.

Demo: https://jsbin.com/sonubug/edit?html,css,output

[1]: https://drafts.csswg.org/selectors/#attribute-case

The Writing Mode property has been implemented and updated in the current version of Edge, but it only includes the values of horizontal-tb, vertical-lr and vertical-rl. Two more values provide an easier way for authors to typeset text in a sideways orientation. They are currently implemented in Firefox (since Sept 2015).

https://www.w3.org/TR/css-writing-modes-3/#valdef-writing-mode-sideways-rl

This feature would add support for ::before and ::after pseudo elements in <input> elements. Chrome, Opera, and Safari already support using pseudo elements to embellish inputs without the need for JavaScript and extra divs.

Steps to reproduce the problem:
1. Open the testcase https://bugzilla.mozilla.org/attachment.cgi?id=8443862 in Edge.

What is the expected behavior?
The test should pass.

What went wrong?
The test failed, indicating that Edge does not support the relevant nth-child(An+B of sel) and nth-last-child(An+B of sel) pseudo classes.

Specification: https://drafts.csswg.org/selectors-4/#the-nth-child-pseudo
Chrome Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=304163
Firefox Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=854148
Webkit Status: https://webkit.org/status/#feature-css-selector-:nth-child(an+b-of-selector-list)-and-:nth-last-child(an+b-of-selector-list)
Can I Use: http://caniuse.com/#feat=css-nth-child-of