Context Navigation

Changes between Initial Version and Version 1 of Ticket #22736, comment 2

initial	v1
1	1	Yes, I customized it to achieve this behavior. It makes more sense in my use case than returning to the change list (or closing the popup right away after saving). I thought it would be nice if the popup context remained in that scenario as well.
	2
	3	-- Edit --
	4	A bit more about the use case. I have a change list that amongst other data displays a thumbnail of an extended file object. The change list itself is connected to another content type than this particular file object, but still it is very convenient to be able to edit the file's metadata (only 3 text inputs) without having to leave the context of that change list.
	5
	6	So I tried to open the edit page for the file inside a popup. In this use case it puzzles the user (just admins, but this change list is used a lot) to be returned to the change list page of the file objects after hitting save in the popup), because it isn't accessed in this context. Closing the popup right away isn't convenient either, because many users prefer to take a glance after saving and then closing manually (especially because the changed values are nowhere to be seen on the change list page that opens the popup, so closing it right away causes uncertainty about the correctness of the saved values)