Yes, we will try to address this problem in a future version. It isn't really possible to do directly, but we have a few tricks and ideas we can try to get around the problem.... most likely we would have you open up the theme design page, and then give you a floating interface to load pages into it and allow you to edit them in context this way... however that is easier said than done and may not even be possible.If that doesn't work we will experiment with other ways that it could be possible, but because of the difficulty it won't likely show up until a full version update and not a bug fix dot release which could fix the auto update issue.
Maybe load the template values into the page until "save". Then remove on save to set the proper streamlined values. OR give us the means to set template code back into the themed page until we manually Update Current Page.
I know that working with this as a bug finds real appreciation of the bug while designing. Then Update Template, we can only deal with the literal content which changes your perspective as a designer. If we have to switch between an actual browser view and the code view, it sets a speed bump in place.
Maybe you should not even fix this bug if there is not a reasonable alternative.
Workflow is important to designers and not fighting apps is key.
Additionally the CCS Menu extension is a nightmare based on it rarely updating the changes made by the user. Usually it takes 3 or more attempts before it properly updates and is written to file. Very frustrating. While I'm on roll the Security Extension is additionally a exercise in frustration getting additional validation fields to load (User and Password for instance). Try once, fail, try again, accept only one value, save, try again, restart DW.... Arrr :) NOTE: I run all the latest version Extensions, DW and OS (Mac) finding the same problem on my new Laptop and 2 year old workstation.
