Change Details

This is not really a ResourceLoader bug but serious enough that some workaround is needed and that probably has to be done via RL. Due to jQuery bug #10251 [1] (wontfixed), errors in a jQuery domready handler prevent all subsequently added domready handlers from running. This means that errors in less reliable scripts like gadgets or user scripts can break any production code that is loaded after them and relies on $.ready (which is true for most extensions). [1] http://bugs.jquery.com/ticket/10251 -------------------------- **Version**: 1.24rc **Severity**: normal

This is not really a ResourceLoader bug but serious enough that some workaround is needed and that probably has to be done via RL. Due to jQuery bug #10251 [1] (wontfixed), errors in a jQuery domready handler prevent all subsequently added domready handlers from running. This means that errors in less reliable scripts like gadgets or user scripts can break any production code that is loaded after them and relies on $.ready (which is true for most extensions). [1] http://bugs.jquery.com/ticket/10251

This is not really a ResourceLoader bug but serious enough that some workaround is needed and that probably has to be done via RL. Due to jQuery bug #10251 [1] (wontfixed), errors in a jQuery domready handler prevent all subsequently added domready handlers from running. This means that errors in less reliable scripts like gadgets or user scripts can break any production code that is loaded after them and relies on $.ready (which is true for most extensions). [1] http://bugs.jquery.com/ticket/10251 -------------------------- **Version**: 1.24rc **Severity**: normal