| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
PatternFly-React preview: https://patternfly-react-pr-2683.surge.sh |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good! Not sure if this is outside of the scope of this PR, but this is also a problem in the select, dropdown, and options menu. Should we fix those in this PR or is that a separate issue?
Sorry, something went wrong.
Signed-off-by: Boaz Shuster <boaz.shuster.github@gmail.com>
|
fixed merge conflicts |
Sorry, something went wrong.
|
@mcoker I can open up a follow up issue. Just to clarify, For the Select, the <div> containing the <button> should not have the pf-m-disabled modifier applied correct? |
Sorry, something went wrong.
|
Issue #2937 has n=been opened to address the issue with the dropdown |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
@tlabaj Yeah, basically the toggle can either be a <div> or a <button>. When the toggle is a <button>, we should use the disabled attribute to disable it. If the toggle is a <div>, we should use .pf-m-disabled to disable it. |
Sorry, something went wrong.
There was a problem hiding this comment.
excellent!
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Your changes have been released in:
Thanks for your contribution! 🎉 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
What:
closes #2666
If component is not button and isDisabled is true then add pf-m-disabled to class name.
//cc @mcoker