Invoking abort_page seems to cause the ErrorScript to run.  I don't think it 
used to work this way because we did not consider abort_page to actually be an 
error -- we used the error / catch mechanism to break out of the call stack but 
we prevented the error script from running if abort page was invoked.

I think I can fix this for FlightAware by using that –aborting switch to see if 
abort_page is running in the error script, but it seems a bit off to me — 
abort_page is not, in my opinion, an error and should not, therefore, trigger 
the running of the ErrorScript.

Does this seem correct or have I someone misinterpreted what I'm seeing?




Reply via email to