Does anyone know if there is a way around the security feature of FileReference that requires a user event in order to execute FileReference.save?
I have method that is called via a buttons click event, but this original eventhandler function calls three more functions via callLater (passing in the original event as an argument to callLater), but I still get the error telling me that when calling FileReference.save it has to be called because of a user event (gesture). I am I wrong to think that passing the initial click event along with callLater should be enough to pass the security requirement? Thanks, Jason
