MySQL Bugs: #113948: export bar color on error change color to red

Bug #113948	export bar color on error change color to red
Submitted:	9 Feb 2024 18:00	Modified:	12 Mar 2024 12:50
Reporter:	Tomás Félix	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
The progress bar remains green throughout the export process, even when encountering errors that prevent successful export. This lack of color change fails to provide users with immediate visual feedback regarding the failure of the export operation. 

Serval time I made an export I thought it was successful and not having a backup.

By adhering to the universally recognized color associations of green for success and red for failure, users can intuitively understand the outcome of their actions. This enhancement will enhance usability and reduce the likelihood of confusion or oversight, ensuring users are promptly informed when operations encounter issues.

How to repeat:
make an export that is not successful and not read the text. Then tray to find if it was successful.

Suggested fix:
Progress Bar Color Change: Modify the progress bar color to red when an operation fails, providing immediate visual feedback without the need for additional user interaction.
OR
Red Error Indicator: Introduce a prominent red indicator, such as an exclamation mark or error icon, alongside the progress bar to signal operation failure, catering to users with color vision deficiencies or in situations where color perception may be compromised.

erro green

Attachment: Screenshot 2024-02-09 180133.png (image/png, text), 31.83 KiB.

Hello Tomás Félix,

Thank you for the bug report.
Could you please provide tables/objects failing to export(please make it as private if you prefer) to reproduce this issue at our end?

Regards,
Ashwini Patil

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".