You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched the issue queue to verify this is not a duplicate bug report.
I've included steps to reproduce the bug.
I've pasted the output of kargo version.
I've pasted logs, if applicable.
Description
When Warehouse couldn't discover one of freight, it shows an error inside tooltip in the UI. However the error is not readable directly, needs to scroll. Also there seems 2 scrollbars and redundant icons.
Screenshots
Steps to Reproduce
Create invalid freight
Version
dev
Logs
Paste any relevant application logs here.
The text was updated successfully, but these errors were encountered:
To fix the scrolling problem with error tooltips, I’m thinking of modifying the tooltip’s design. This could involve adjusting the tooltip’s max-height and setting overflow properties to ensure all content is visible without scrolling. Alternatively, we could explore truncating the message with an option to expand for more details.
Note that if you try to copy it so you can paste it somewhere, it will open Freight detail if you click on it. Imho it should not open details page if you click on tooltip.
The tooltip is nice and all and I wouldn't suggest we remove it, and I do believe it can be improved, but I think displaying error messages clearly in the Warehouse details view would probably make it quite a bit easier for people to read and copy if necessary.
For reference, Promotions currently do this. The prominently display whatever error prevented them from succeeding in the details view.
Checklist
kargo version
.Description
When Warehouse couldn't discover one of freight, it shows an error inside tooltip in the UI. However the error is not readable directly, needs to scroll. Also there seems 2 scrollbars and redundant icons.
Screenshots
Steps to Reproduce
Create invalid freight
Version
Logs
The text was updated successfully, but these errors were encountered: