-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Deprecate Component#isVisible #324
Conversation
First, thanks for putting this together! This fixes a few small typos, and rephrases "attribute" to "property", as the first is commonly used when creating HTML nodes. See https://stackoverflow.com/questions/6003819/what-is-the-difference-between-properties-and-attributes-in-html
What would be the suggested way of hiding components from the DOM in Ember as | ||
there are a few options to choose from? | ||
|
||
When will support for the deprecated property end? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is public, so according to SemVer this should be 4.0
f679254
to
cc52c4a
Compare
Updated Support
cc52c4a
to
e9ad244
Compare
As to when the support will end, I think since isVisible is public it will have to be 4.0 |
New Draft Updated the support ending section. |
such as `<div hidden={{boolean}}></div>`(hidden is valid for all elements | ||
and is semantically correct) or wrapping the component in a template | ||
conditional `{{#if}}`statement which do not interfere with | ||
the `StyleBindingReference`. Components `classNames` an `classNameBindings` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/an/and/
If anyone is curious about the accessibility concerns for display:none; - https://webaim.org/techniques/css/invisiblecontent/ |
This RFC came up at the Ember.js Core Team meeting today, and we have decided to move it forward into final comment period... |
We reviewed this again at todays core team meeting, and are all still in favor. Thanks to everyone who participated! |
Rendered