-
Notifications
You must be signed in to change notification settings - Fork 43
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
TACKLE-671: Application form - Packaging Popover #300
Conversation
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.
@ibolton336, the related issue (TACKLE-671) clearly lacks requirements. |
No problem. Lets wait for the UXD input before moving forward just so we have something to go off of for future tooltips. |
@ibolton336, thank you for the follow-up with UXD, I have replaced |
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.
Something isn't looking quite right here with the spacing and icon size.
Also, I think I remember the popover on MTC having a black background? I could be wrong there but seems like the popover is hard to read against the form background. I wonder why the tooltip has a black background and the popover does not.
@ibolton336, please re-review with dark popover in place. |
I think the form spacing may be the culprit here, but the label seems cramped underneath the above input box. Also, the icon size still doesn't seem to be scaled correctly. Would love to nail this so we can reuse across the app. Maybe even create a label with popover icon local component if that makes sense? |
@ibolton336, I updated it wrapping Icon with span and css properties and also replaced Icon with |
Match MTC popover icon styling
@ibolton336, I don't know why we have to go all the way to define CSS at top level as we didn't need such approach with tackle. Anyway it looks much better. Thanks |
Global CSS is useful if we have modifier classes that are available across widely used components. That way we don't have to import the css again in each file. Is there another approach you had in mind? |
@ibolton336, I understand the global vs local approach, but that's the thing, in forklift, I don't think we're changing anything locally but as you mentioned we might be using a different PF version. |
https://issues.redhat.com/browse/TACKLE-671