Nate Bosch ca03588d2b Run extension handlers in the registering zone ... Towards https://github.com/flutter/flutter/issues/93676 Flutter uses an extension for hot reloads, and the app ends up running in the root zone after a hot reload because that is the zone that the handler gets called in. Always run extension handler callbacks in the zone from which they were registered for more predictable behavior. Change-Id: Ia921489a6ada802c8e53a0ccc650a8bce218ba01 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/275842 Commit-Queue: Ben Konyi <bkonyi@google.com> Auto-Submit: Nate Bosch <nbosch@google.com> Reviewed-by: Ben Konyi <bkonyi@google.com>		2022-12-15 15:05:17 +00:00
..
bin	[3.0 alpha][VM/Runtime] - Flip flag to make strong null safety the default.	2022-12-06 04:04:23 +00:00
lib	Run extension handlers in the registering zone	2022-12-15 15:05:17 +00:00
.gitignore	[sdk] Generate a version file for the unpatched SDK	2022-05-05 10:36:05 +00:00
api_readme.md	Update the API docs readme	2020-01-16 21:23:09 +00:00
BUILD.gn	Revert "[VM/CLI] Remove dartdev.dill"	2022-12-13 15:28:19 +00:00
OWNERS	[infra] Add OWNERS to the Dart SDK	2022-02-14 14:06:34 +00:00