mirror of
https://github.com/jgthms/bulma
synced 2026-03-15 02:04:29 -07:00
5048a0d7fb
* <!-- PLEASE READ THE FOLLOWING INSTRUCTIONS --> <!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR --> <!-- Choose one of the following: --> This is a bugfix <!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. --> <!-- Improvement? Explain how and why. --> <!-- Bugfix? Reference that issue as well. --> If a form field is disabled and that form field uses has add-on element ( has-addons ), hover state is overlapping to add-on element. ### Proposed solution <!-- Which specific problem does this PR solve and how? --> <!-- If it fixes a particular Issue, add "Fixes #ISSUE_NUMBER" in your title --> This solution excludes disabled form elements hover state which is used within has-addons fields wrapper. Fixes #1992 ### Tradeoffs <!-- What are the drawbacks of this solution? Are there alternative ones? --> <!-- Think of performance, build time, usability, complexity, coupling…) --> No tradeoffs. ### Testing Done I checkout out master and changed the lines. * Disabled form elements hover state is overlapping, if control has add-ons elements If a form field is disabled and that form field uses has add-on element ( has-addons ), hover state is overlapping to add-on element. * Disabled form elements hover state is overlapping, if control has add-ons elements If a form field is disabled and that form field uses has add-on element ( has-addons ), hover state is overlapping to add-on element.