It's not synchronous if you have an external can.batch.start wrapper, which is why we have the callback to begin with. My issue is occurring in both situations, however. DOM stuff after the synchronous attribute changes do not work nor do they work in the asynchronous callback.
↧