After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 615846 - inline folder rights notifications
inline folder rights notifications
Status: RESOLVED DUPLICATE of bug 164850
Product: nautilus
Classification: Core
Component: Views: All
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-15 13:38 UTC by Hylke Bons
Modified: 2010-07-08 12:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
better inline notification (137.88 KB, image/png)
2010-04-15 13:38 UTC, Hylke Bons
Details

Description Hylke Bons 2010-04-15 13:38:57 UTC
Created attachment 158815 [details]
better inline notification

because every time an unnecessary one pops into my face a kitten dies. :'(
(this will have to be improven in the file chooser as well)
Comment 1 Andreas Nilsson 2010-04-15 14:28:26 UTC
If I recall correctly, Firefox used to pop up a dialog when hitting the wrong url, these days is does a inline error for that. The inline error feels a lot more satisfying and less punishing.
Comment 2 Andreas Nilsson 2010-04-15 14:50:14 UTC
A dialog is also less connected to the area where the error is actually happening. If done inline, it would be specific to the tab or window being open at the time and not as easily confused with other places where this theoretically could show up.
Comment 3 Cosimo Cecchi 2010-04-15 15:45:21 UTC
Very nice idea.
Could it be useful to add a "Go Back" button there as well?
Comment 4 Andreas Nilsson 2010-04-15 15:58:24 UTC
Isn't there a Go Back button in the toolbar already?
Comment 5 Hylke Bons 2010-04-15 16:10:00 UTC
A button hat oculd make sense is 'unlock' or something.
Comment 6 Allan Day 2010-07-08 12:20:06 UTC
This is a dupe! I'll add the mockup to the older bug.

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