-
Notifications
You must be signed in to change notification settings - Fork 239
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
fix(pagination): minor css for react-bootstrap pagination dropdown #910
Conversation
0036820
to
3c4f132
Compare
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.
Hi @priley86 Although I don't see a technical problem to merge this, it leads me to think how much we should clutter patternfly's core code base for the sake of one JS framework implementation.
If we start treating PF core as a dump site to all possible implementations, then everyone loses. any patternfly user that is not using our React implementation will ship more useless code if we merge this PR.
@jeff-phillips-18 I'll let you decide on this.
Hi @andresgalante, @priley86, yeah, it's a balancing act. I think in general we are trying to avoid whenever possible adding less/css to the js framework repos so that patternfly core is the main/single place for Patternlfy less/scss/css. This angular-patternfly issue/epic is an attempt to move less to core where ever possible. |
@andresgalante i don't see why pf-core should be scoping css specifically for jquery extensions at this point. Is there anything here that is really pf-react specific though? 🙋♂️ |
@andresgalante Is the specificity that is there now required for patternfly? |
I see that we do need to provide the original level of specificity in order to override the bootstrap setting. I'm OK with this change since it is really just providing an alternative to using the jquery bootstrap-select. |
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.
The selector addition and minor resets look easy enough. Curious how an inherited float was influencing a flex layout... overall lgtm.
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
The css comes from patternfly/patternfly#910, wrapped in a `.miq-v2v` so that we can be sure this only affects v2v screeens. Unfortunately dialogs get opened directly under body, so any such class needs to live on body. (Fortunately there are no cross-controller ajax transitions in gaprindashvili.)
Description
This PR attempts to address a minor issue using the React Bootstrap DropdownButton instead of bootstrap-select. The DOM rendered is a tad bit different from bootstrap-select and customizing this via a few minor CSS tweaks seems to be the easier option.
Link to OSUX story:
https://patternfly.atlassian.net/browse/OSUX-339
PF-React PR:
patternfly/patternfly-react#143
Link to React Storybook
Note: I am ignoring the bootstrap-select paddings added to the
dropdown-toggle
and would prefer to just leave it atmin-width:auto
as to not introduce more CSS.Changes
btn-group
selector as to ensure React Bootstrap button-group is styled closely w/o thebootstrap-select
classmin-width:auto
Link to rawgit and/or image
For example: Here is a link to Alerts on rawgit
This is an image:
PR checklist (if relevant)