UI-wise I'd prefer it to be actual cancel, rather than introducing a new string for what's a dispreferred action in the first place.

UI-wise I'd prefer it to be actual cancel, rather than introducing a new string for what's a dispreferred action in the first place.

I'm not entirely sure how this would behave on pages like Configuration > Display. Would it close the page and return to the home screen?

I'd remove it altogether, but going back is an option too.

I'd remove it altogether, but going back is an option too.

I agree with removing it altogether, but it seems appropriate to keep it on the “Manage Extensions” page, as it’s quite useful for extensions like UserCSS and UserJS.

Yes, but there it should function as cancel/close (same as pressing escape or clicking next to it) rather than reset. :-)

PS You might potentially want to hold off on implementing my suggestions for a little bit since other people might have different ideas, depending on how involved it is.

I am not sure I understand the problem with Cancel. Can you please explain again @Frenzie ?
And shouldn’t we just rename the key gen.action.cancel to gen.action.reset? No reason to keep the old one, is there?

I am not sure I understand the problem with Cancel. Can you please explain again @Frenzie ?

That depends which problem you mean.

1. The text that says cancel actually does reset.
2. Is there ever anybody who actually wants reset?
3. There are some dialogs you can't exit because of this problem. Making the text say "reset" won't fix this fundamental issue.

In short, I consider cancel the correct text and behavior. It's just that the behavior is currently broken.

And shouldn’t we just rename the key gen.action.cancel to gen.action.reset? No reason to keep the old one, is there?

Extensions would still be using gen.action.cancel in their configure.phtml, until they are updated, so it shouldn't be removed.