New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add display:contents #608

Closed
aldendaniels opened this Issue May 31, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@aldendaniels
Copy link

aldendaniels commented May 31, 2018

Chrome and Firefox both now support CSS display: content - a feature that is becoming important in frameworks like React where wrapper components may want to listen to browser events without affecting DOM layout. https://caniuse.com/#feat=css-display-contents It would be great to track progress towards this on the edge status dashboard.

@FremyCompany

This comment has been minimized.

Copy link
Contributor

FremyCompany commented Jun 4, 2018

The feature was implemented poorly in the other browsers and has accessibility issues, so it is unlikely we would want to add support in Edge right now.

If we were to add the feature on the status, it would be as "Not currently planned".

To prioritize this, I would urge Chrome to fix its accessibility issues. When they do, maybe we can reconsider the feature.

molant added a commit that referenced this issue Jun 5, 2018

@molant

This comment has been minimized.

Copy link
Member

molant commented Jun 5, 2018

@aldendaniels there's a PR for this right now: #609

@alrra alrra closed this in 4dd96ae Jun 5, 2018

@aldendaniels

This comment has been minimized.

Copy link
Author

aldendaniels commented Jun 5, 2018

Thanks! I appreciate the quick follow up. FWIW, I think there are high-value use-cases for this feature that don't break accessibility - I'd be happy to elaborate if that would be useful and you can point me to an appropriate forum.

@HM100

This comment has been minimized.

Copy link

HM100 commented Aug 31, 2018

Firefox has fixed this in M62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment