-
Bug
-
Resolution: Done
-
Minor
-
None
-
False
-
False
-
0
-
Undefined
-
Not Supported
-
-
ODC Sprint 203
-
Low
Description of problem:
The monitoring custom time range dialog text fields are not sized correctly (doesn't have a similar height) IF the topology was opened earlier.
It looks like that the affinity-expression-row.scss file from the kubevirt plugin is loaded in the topology which changes the PatternFly typeahead style globally.
Prerequisites (if any, like setup, operators/versions):
A cluster with monitoring
Steps to Reproduce
- Test case 1:
- Open developer perspective
- Open Topology and switch to Monitoring
- Open time range dropdown and select "Custom time range"
- Test case 2:
- Open developer perspective
- Open Monitoring and reload your browser tab (to ensure other css rules are not loaded)
- Open time range dropdown and select "Custom time range"
Actual results:
Custom time range modal looks different in both test cases.
Expected results:
Custom time range modal should look similar on both cases and the text fields should have the same height.
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
4.9
Additional info:
- We should check if the .pf-m-typeahead rule is necessary. If yes we should ensure that it doesn't effect other components by adding a restrictive parent rule or something.
- Maybe it's possible to check if we have similar issues in our code?