The application is a form based application. The form elements are arranged in Grids. Each of the Grids encapsulate related set of fields. Now the question is related to cancel buttons. There are about 100 editable elements in a single form. The user makes some changes to the screen and these changes are maintained in the browser session and persisted only when the user clicks on the save button.
The Usability expert in our team insists on having atomized cancel buttons. That is each of the grids can have its own independent cancel button. The problem is bad as is if this is a single form, but the application can contain multiple tabbed forms. So we need to write a lot of logic to maintain atomic states and track each changes individually; I wanted to know if any of you have any opinion on working with a requirement like this. Is this requirement justifiable? or does it contribute to good usability.