-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Popup: button class applied to Popup #1703
Comments
Don't worry about the positioning of the |
action
prop of an Inputaction
prop of an Input
action
prop of an Input
Adding more context here, all input actions require the Input.js const actionElement = Button.create(action, { defaultProps: { className: 'button' } }) The intent here was to ensure that all actions had the required <Input action={<Button />} />
<Input action={<Dropdown button />} /> This would allow the Popup to render without a Breaking ChangeThis would be a breaking change in that we'd now require Dropdown actions to explicitly define the Before<Input action={<Dropdown />} /> After<Input action={<Dropdown button />} /> |
@levithomason As I understood the author suggests that the popup should not inherit the "button" class? Therefore is the solution above able to fix this? The change seems too big. |
Yes, the solution will fix the the bug. It is a minimal change and inline with the direction of library, that is, less magic and more explicit props. Note that the breaking change will only affect cases where the |
Steps
When creating a popup from a button with as an
action
prop from anInput
, the.button
class is being passed to the Popup which is giving it the text-align and hover styles of a button.Expected Result
There should be no
.button
class on the.ui.popup
that is being rendered.Actual Result
A
.button
class is present on the rendered.ui.popup
Version
0.68.3
Testcase
http://codepen.io/anon/pen/BRbpWw
The text was updated successfully, but these errors were encountered: