Hide Forgot
Description of problem: While uploading a problem report, I was directed to review the highlighted tabs, but none were a different colour. They were all black. But upon closer inspection, IE my eyeball near the screen I could see some were red. As it happens, I am red/green colour blind and the shade of red chosen is one that I am unable to see correctly. I would like to ask that you not only highlight in colour the tabs, but underline the titles also for accessibility reasons. How reproducible: Always (but you need to be colourblind to see the issue)
Thank you for the report! I've submitted a patch fixing this issue for review: https://lists.fedorahosted.org/pipermail/crash-catcher/2013-September/005480.html
Fixed in upstream git: commit 7f6e6be73306baa6dc0642c4c0c1cff4814b7c7a Author: Jakub Filak <jfilak> Date: Mon Sep 16 09:48:42 2013 +0200 reprot-gtk: underline tab titles with sensitive information Closes rhbz#1008125 Signed-off-by: Jakub Filak <jfilak> Signed-off-by: Jiri Moskovcak <jmoskovc>
gnome-abrt-0.3.2-1.fc19,abrt-2.1.8-1.fc19,libreport-2.1.8-1.fc19,satyr-0.10-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gnome-abrt-0.3.2-1.fc19,abrt-2.1.8-1.fc19,libreport-2.1.8-1.fc19,satyr-0.10-1.fc19
Package gnome-abrt-0.3.2-1.fc19, abrt-2.1.8-1.fc19, libreport-2.1.8-1.fc19, satyr-0.10-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.2-1.fc19 abrt-2.1.8-1.fc19 libreport-2.1.8-1.fc19 satyr-0.10-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18924/gnome-abrt-0.3.2-1.fc19,abrt-2.1.8-1.fc19,libreport-2.1.8-1.fc19,satyr-0.10-1.fc19 then log in and leave karma (feedback).
gnome-abrt-0.3.2-1.fc19, abrt-2.1.8-1.fc19, libreport-2.1.8-1.fc19, satyr-0.10-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.