Editing JavaScript action steps in a second window is available, but for me is not at present a very useful feature. The reason is that the Save button (top left) does not seem to have immediate effect. Therefore after I edit the script, I have to use the Save and Exit button (top right) before the editing modification takes effect.
So in a test/edit cycle, running the tests in the first window and editing in the second, the time-saving benefit of the second window is wasted, because after each edit, a Save and Exit is required, and then the action has to be re-opened for editing, the JavaScript step selected, and the Edit button has to be clicked. This is laborious and repetitive!
Am I missing something? If not, could the Save button be altered to take immediate full effect?
iPadOS 26.1, Drafts 48.3 (674).
I don’t think that is likely to change. It would be bad form to be constantly saving changes in the background when the vast majority of the time editing a script it is in an invalid state and the user should have to confirm in some form that they are at a point that should be saved. This is equivalent to almost any script editing workflow where you are editing files and need to save the file before you can test changes.
But I do confirm that the script is at a point which should be saved, by pressing the Save button. I just don’t want to have to press the Save and Exit button as well, as that requires several subsequent steps to get back to editing.
Re “constantly saving changes”, is there also a timed autosave? A solution would be to have an option to turn that off, and instead to do a full save when the Save button is pressed.