Bug 312991

Summary: Alert bar for "file or folder does not exist" has confusing UI
Product: [Applications] dolphin Reporter: Elliott Eggleston <ejeggleston>
Component: bars: locationAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: minor CC: rishubhkde
Priority: NOR    
Version: 2.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Illustration

Description Elliott Eggleston 2013-01-10 03:42:26 UTC
Type a bad path into the location bar.  A red bar appears below informing you that "The file or folder /blah/blah/blah does not exist."  There is a red square to the left of the message with a white X on it.  There is a red circle to the right of the message with a white X on it.  Clicking on the circle dismisses the alert.  Clicking on the square does nothing.

Suggestion: either use no icon to the left, or use an icon that does not suggest a clickable action, such as a yellow exclamation point.

Reproducible: Always

Steps to Reproduce:
1. Type a bad path into the location bar. 
2. A red bar appears below informing you that "The file or folder /blah/blah/blah does not exist."  There is a red square to the left of the message with a white X on it.  There is a red circle to the right of the message with a white X on it. 
3. Click on the square with the X
Actual Results:  
nothing

Expected Results:  
square with red X looks like dismiss/close button, expected alert message to disappear
Comment 1 Elliott Eggleston 2013-01-10 03:44:25 UTC
Created attachment 76357 [details]
Illustration
Comment 2 Rishubh Jain 2013-01-10 04:42:09 UTC
Bug 312991 is a unique bug and i have confirmed it by reproducing it(in the same version)...change the status to confirmed
Comment 3 Rishubh Jain 2013-01-10 04:42:52 UTC
Bug 312991 is a unique bug and i have confirmed it by reproducing it(in the same version)...change the status to confirmed
Comment 4 Frank Reininghaus 2013-01-10 07:27:28 UTC

*** This bug has been marked as a duplicate of bug 304775 ***