You can clone with
HTTPS or Subversion.
The changes you've made should be canceled, and the the plugin editor should probably disappear.
It's a submit button, so it triggers full validation, and if successful, saves whatever you've cancelled back to the database.
I think the the comment from @calinf on October 28, 2011, in ticket #861 may be piggybacking that issue to describe this issue, and proposes a potential fix (which, FWIW, I don't like, as it's a different intention), but that ticket is tagged for 2.3, and I think given it's a potentially destructive feature in 2.2.0/develop, it ought to be pushed to 2.2.1. For our purposes, we've hidden the cancel button entirely in the admin, to side-step it.
Final note: the buttons are in different positions in the frontend vs backend. Minor niggle.
Addendum: It'd be nice if the cancel input had an ID or class, too so it can be easily targeted via CSS. At the moment, to hide it, I've got something like (LESS):
which nets me:
which just hides the cancel button altogether.
fixes issue #1124 - now integration branch is develop-2.2.1
This issue has been addressed with #1251; if #1251 is OK, then this is closed!
deleting a plugin if it gets cancelled without an instance being crea…
…ted. fixes #1124