Changes between Initial Version and Version 5 of Ticket #16617


Ignore:
Timestamp:
Jan 29, 2013, 11:54:43 PM (8 years ago)
Author:
bill
Comment:

I see. Although I worry that adding the catch(e) workaround will make debugging harder on other platforms, especially when "pause on uncaught exceptions" (only) is set, because then won't chrome only stop on the second throw, rather than the original one?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16617

    • Property Owner set to Nathaniel Mills
    • Property Component changed from General to Core
  • Ticket #16617 – Description

    initial v5  
    11The release notes in 1.8.1 talk about IE8 compatibility, but my application breaks as soon as dojo.js is loaded because it has a try / finally without a catch in the guardCheckComplete method. The fix is simply to add an empty catch as shown below highlighted by add --> bold:
     2
     3{{{
    24                guardCheckComplete = function(proc){
    35                        try{
     
    1214                        }
    1315                },
     16}}}
    1417I looked in the 1.8.3 and latest dojo.js source and it also has this problem.