id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
10832	Too easy to delete layers using the delete key	sanderd17	team	"IMO, it's too easy to delete layers by using the delete key.

I often press delete in order to delete a node or a way, but because I switched layers as the last action, a layer is deleted instead. This is certainly an issue when I'm editing layers which have the upload=""no"" flag set. Then an important data layer can be deleted without notice. There are multiple solutions possible:

* Don't let delete remove layers. IMO, removing layers isn't a common action (not nearly as common as removing nodes or ways, and also less common as removing tags). There's still the trash-button that can be used. I think, this is the best solution

* Warn when you delete data layers, even when upload=""no"" is set: upload=""no"" doesn't mean you can't edit data, and you should be warned when you remove manually edited data without saving or uploading. In this case, only the save action could be proposed.

* Implementing an undo action for the deletion of layers: This might solve the problems, but it might also cause other problems. F.e. someone might want to delete a layer because it uses too much memory, but when you can undo a deletion, the memory won't be freed (most likely).

All implementations could be combined, and when implemented, they will save work in some different cases.

Thanks for considering this request."	enhancement	closed	normal		Core		worksforme