-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "Fixes: Safari's 'double finally on error bug'" #11547
Revert "Fixes: Safari's 'double finally on error bug'" #11547
Conversation
This reverts commit 917da11. iOS 6 makes up less the 4% of the iOS market, and this bug appears to be fixed in iOS 6.1. As such the potentially affected devices is quite small. Finally, the bug only comes into play in very specific failure scenarios which are nearly all already handled in backburner.
+1, please also call out on the 2.0 breaking changes in the blog post |
do we have an issue tracking that? |
No, just the blog post for 2.0-beta |
is there |
Come on man. Here is an issue: emberjs/website#2222 We must document these breaking changes. If you contribute a deprecation or breaking change, it must be documented. |
Thanks, i was merely asking if there was an existing issue that tracked this. |
…inally-on-error Revert "Fixes: Safari's 'double finally on error bug'"
* Update tests to ensure that the global path must not be `undefined` * Fix issue with `Ember._Renderer` export * Remove `Ember.rewatch` export remnants (it was removed in #9323) * Remove `Ember.apply` export remnants (it was removed in #13655) * Remove `Ember.tryCatchFinally` export remnants (it was removed in #11547)
* Update tests to ensure that the global path must not be `undefined` * Fix issue with `Ember._Renderer` export * Remove `Ember.rewatch` export remnants (it was removed in emberjs#9323) * Remove `Ember.apply` export remnants (it was removed in emberjs#13655) * Remove `Ember.tryCatchFinally` export remnants (it was removed in emberjs#11547)
* Update tests to ensure that the global path must not be `undefined` * Fix issue with `Ember._Renderer` export * Remove `Ember.rewatch` export remnants (it was removed in emberjs#9323) * Remove `Ember.apply` export remnants (it was removed in emberjs#13655) * Remove `Ember.tryCatchFinally` export remnants (it was removed in emberjs#11547)
This reverts commit 917da11.
iOS 6 makes up less the 4% of the iOS market, and this bug appears to be
fixed in iOS 6.1. As such the potentially affected devices is quite
small. Finally, the bug only comes into play in very specific failure
scenarios which are nearly all already handled in backburner.