Using system notifications for regular operations would be cumbersome.
Also, it's used like that because they are attached to a window, no to the whole application.

Closing as WONTFIX for now.

Pity.  Why deliberately and obstinately get in the user's way?

The point is that they hide whatever they happen to popup over and prevent access to it for 10-15 seconds.  This is annoying and purposeless. There is no user control over this function:  The 100,000th undo notice a user sees will stay on screen as long as the first notice, always obscuring the same amount of screen territory, 

Effort seems to have been taken in the design of other Gnome notifications to ensure they do not obscure other elements of the display that users need to interact with.  Gnome should not take an opposite, dysfunctional, approach to Nautilus notifications.

(In reply to joncr from comment #2)
> Pity.  Why deliberately and obstinately get in the user's way?

That's an empty statement. Be careful with those, can make the discussion invalid.
You can say that for everything in your screen (and also to the system notifications) and the feedback won't go anywhere.
> 
> The point is that they hide whatever they happen to popup over and prevent
> access to it for 10-15 seconds.  This is annoying and purposeless. There is
> no user control over this function:  The 100,000th undo notice a user sees
> will stay on screen as long as the first notice, always obscuring the same
> amount of screen territory, 
> 
> Effort seems to have been taken in the design of other Gnome notifications
> to ensure they do not obscure other elements of the display that users need
> to interact with.  Gnome should not take an opposite, dysfunctional,
> approach to Nautilus notifications.

In app notifications are used in other projects (gnome photos, gnome-documents, gnome-boxes, etc) for the same purpose than nautilus is using it (I even copied the code! =)).

We will have them in the HIG soon (I hope) as well.

If you want to back up your points I advice you to put use cases, specific problems in those use cases, screenshots, what do you propose and why it is better, how it fixes the problem of that operation being part of the window and not the whole application, mockups, etc.
But we already though about all these points already.

No need for for remarks like "Be careful with those, can make the discussion invalid."  This is not a therapy session.

I am only pointing out that the undo notices in Nautilus prevent a user from acting on the elements they obscure until they go away.

I can't opt in or opt out of these notices.  I can't determine their duration. I can't determine their location. 

If I want to click on a filename or icon that is obscured by a notice, I have two choices:  1) I can take the now necessary extra action to click on the notice's close button, or 2) wait idly until the notice closes on its own.

If a similar approach is taken in other Gnome apps, then this same issue needs to be addressed there:

1.  Notices in apps should never prevent user interaction with other elements.

2.  Notices in apps should never force the user to wait until they disappear.

For myself, I'll add that I don't see a compelling need for notifications that advise of a condition that is always true. 

In this case, if the undo capability will *always* be true, *always* showing an undo notice is redundant. 

Better, perhaps, to show it for some limited number of times after an install and then turn it of.

(In reply to joncr from comment #4)
> No need for for remarks like "Be careful with those, can make the discussion
> invalid."  This is not a therapy session.
> 
I'm not terapying you, I'm advising you to have success here with developers or designers with your wanted change. If you don't appreciate it I can just not answer here and don't spend my time...

> I am only pointing out that the undo notices in Nautilus prevent a user from
> acting on the elements they obscure until they go away.
> 
yes, and is the best solution we found.

> I can't opt in or opt out of these notices.  I can't determine their
> duration. I can't determine their location. 
> 
yes, we don't have options for every part of the application.

> If I want to click on a filename or icon that is obscured by a notice, I
> have two choices:  1) I can take the now necessary extra action to click on
> the notice's close button, or 2) wait idly until the notice closes on its
> own.
> 
> If a similar approach is taken in other Gnome apps, then this same issue
> needs to be addressed there:
> 
> 1.  Notices in apps should never prevent user interaction with other
> elements.
> 
> 2.  Notices in apps should never force the user to wait until they disappear.

As said, it tries to not obscure much content. I can't see a better approach.

(In reply to joncr from comment #5)
> For myself, I'll add that I don't see a compelling need for notifications
> that advise of a condition that is always true. 
> 
I don't understand this sentence.
> In this case, if the undo capability will *always* be true, *always* showing
> an undo notice is redundant. 
> 
Sorry I don't understand, can you rephrase it more direct or something?
> Better, perhaps, to show it for some limited number of times after an
> install and then turn it of.

The intention is not just a n times, but always a user make a risky operation like deleting (the user can hit the delete key and miss his file, with a notification you prevent this)

Isn't it always the case that the undo capability is available? 

If, then, it is felt necessary to always display a notice advising of a condition that is always true, perhaps, in this instance, consider making room for the notification by temporarily relocating the portion of the display it will overlay.  In effect, "pushing down" the icons/text/etc.  that would otherwise be obscured and unavailable during the lifetime of the notice. 

This is very similar to the behavior of the drop down menu that displays the "show hidden files" option.  In 3.16, when a user selects that option, the dropdown remains in place, overlaying and obscuring the refreshed content.

(In reply to joncr from comment #0)
First of all, thanks for the bug report.

I started writing this reply yesterday but didn't finish at the time and a lot has been said in the meantime, but I'll leave here what I had already written anyway.

> The new Undo notifications in Nautilus (1) are not displayed where all other
> Gnome notifications are displayed, and,

Atually, there is a reason for this difference. It is important to make it clear that these Undo notifications are about what is happening in the current window, not about something happening in the background. The system notifications are about what happens in the background and clicking them will open/switch to another application/window. This is not the case of Undo notification, which is part of the nautilus interface.

> (2) overlay and obscure content --
> icons, file listings, etc. -- in Nautilus.

Indeed, the current implementation of "in-app notification" overlays the notifications on the top center of the content view. This partially obscures content. However, it is possible to see what is behind it, because the notification has got some transparency.

Although the notification goes away after a few seconds, a person may want to dismiss it right away, so an "x" button is included.

-> Is any of this not working as described?
-> Is the "x" button had to notice or hard do click?

I personally feel that the close button is a very small target and this makes it frustrating to dismiss a notification manually. Perhaps it should also dismiss if we click anywhere else in the interface (selecting a file, for instance).

But more importanly:

-> In which situations do you find the notification obscuring something you are trying to see/click? Which view (Icon View or List View)? And which zoom level? (Small, Normal or Large)

Personally, only in List View and only in the smalles zoom level do I see a notification completely oscuring the first file. And even then, only if the name of the deleted file is so long that the notification becomes as wide as the file list.

Some people can find the notification useful. Some other people like me don't need it at all, there is the trash to see what you have deleted and that allow to recover some deleted files if needed.

So why not simply add an option to disable it ?

(In reply to António Fernandes from comment #9)
> Although the notification goes away after a few seconds, a person may want
> to dismiss it right away, so an "x" button is included.
> 
> I personally feel that the close button is a very small target and this
> makes it frustrating to dismiss a notification manually. Perhaps it should
> also dismiss if we click anywhere else in the interface (selecting a file,
> for instance).
I agree with that.

> Personally, only in List View and only in the smalles zoom level do I see a
> notification completely oscuring the first file. And even then, only if the
> name of the deleted file is so long that the notification becomes as wide as
> the file list.
For me, that's enough to justify to add an option to disable the notifications. If something can annoy the user it should be optionnal.

Let's take the system notifications, they are configurable, you can choose to use them or not and more you can choose by application!

Can we make the nautilus notifications optional, like the system notifications ?

Carlos can we talk about making the nautilus notifications optional please ?

(In reply to jeremy9856 from comment #12)
> Can we make the nautilus notifications optional, like the system
> notifications ?

No, it's a bigger problem than just Nautilus and making it optional for just Nautilus won't help. This needs design and designers are working on it.

I agree. Is there something planned ?

(In reply to jeremy9856 from comment #15)
> I agree. Is there something planned ?

Designers has some work on it.

Great, do you know if it's something planned for Gnome 3.20 or for much latter or if it's just some kind of mockup with no particular plan for now ?

Design work usually happen in github[0] or in IRC. It's on its early state, so I'm not sure if it is for 3.20, it's a difficult matter.

[0]https://github.com/gnome-design-team/gnome-mockups

Ok, the most important thing is that is some work in progress and not a dead end.
Thank you !

Any news about this ? Thanks !

So no news about this ?

How about reusing the bar that Nautilus displays e.g. in trash? It won't obscure the content (and looks better in my humble opinion).
Examples of this bar to show what I'm talking about:
http://i.stack.imgur.com/DdwZ4.png

https://www.google.pl/imgres?imgurl=https://i2.wp.com/a.pomf.se/izhwch.png&imgrefurl=https://csorianognome.wordpress.com/2015/04/30/nautilus-communicating-changes/&h=609&w=875&tbnid=guwqUfxVuMDtKM:&docid=EDdmcaxJ_4wkgM&itg=1&ei=3y-NVpzoFKGhyAPL-LGYCQ&tbm=isch&ved=0ahUKEwjc0-a9vZXKAhWhEHIKHUt8DJMQMwhXKDEwMQ

Can we have an update for this please ?
Thanks

These notifications are like spam. That is, repeatable unsolicited messages — the messages, you don't want to read. Nobody likes spam, so please, add a dconf entry so that I can “unsubscribe” from it and do stuff without interruptions.

A dconf entry to disable them in the mean time, before they are reworked, will be very great. The idea is good but the way that they are displayed is unfortunately very annoying :(

@jeremy Actually, I don't like the whole idea. Why they didn't create notification about folder creation? Files moving? Location changing? What is so specific in moving files into the trash folder?

I guess that's because when you move a file to the trash you can lost it. I like the fact that if you change your mind or delete a file by mistake you are informed and can undo it quickly with the notification. But they should not interfere with the usability of the app and should have the possibility to be disabled, like the system wide one.

Now you can disagree with what they do but we have to be thankful for their work. If we don't like it, nobody force us to use it and remember that the FREE work of people like you and me that do what THEY like and make it available for anybody that what to use it. They are not accountable to us ;)

@jeremy They could create a hotkey (Ctrl+z) and a context menu entry (“Undo last action”) for that matter. The fact that they inform me about an action I made a second ago brings absolutely no value.

If I do something I realize what I do and at the **most cases** I don't need to undo what I've done. If at rare times I still do a mistake I just need a mean to correct it.

Of course, the system cannot know when my action is mistaken and when it's not, so why then it constantly suggests me to correct what I've done as it was a mistake?

@Hinume we both agree that the notifications should be optional or at least be unobtrusive. No need to argue more ;)

Like Carlos said on comment 14 they know that the notifications are not optimal and they work on it. Now we can just hope that re-work of the app notifications won't take years ;)

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