Fixes that even though we weren't rendering the deferred block the server, we were still triggering the timeout which can delay the response.

Fixes #55475.

PR Close #55605

PR Close #55611

preview is hidding was responsible for hidding the content.

fixes #55583

PR Close #55584

See associated pull request for more information.

PR Close #55537

This can replace CUSTOM_EVENT_SUPPORT by allowing users to bootstrap
custom event support separately from the `EventContract`.

PR Close #55603

This define has been removed at head, and now legacy stop propagation
behavior can be opted into at the LegacyDispatcher level, if necessary.

PR Close #55582

This refactor will enable moving this functionality into the dispatcher.

PR Close #55523

PR Close #55521

PR Close #55545

This commit ensures we flush animations by calling renderFactory
begin/end in cases where the ApplicationRef._tick happens in a mode that
skips straight to the render hooks.

PR Close #55564

These lines were not tree shakable by Closure Compiler because `.toString()` is special cased as a "pure" function eligible to eliminated if it's return value is unused. However `.toString.call` circumvents this and makes Closure Compiler think the function may have side effects. Switching to `.toString()` should be fine here as `process.toString()` in Node outputs `[object process]` so this should be safe. Presumably the original motivation for this roundabout approach was for type safety reasons which no longer apply as `_global` is `any`.

PR Close #55412

PR Close #55578

See associated pull request for more information.

PR Close #55575

The docs-viewer loads asynchronously and can happen after the scroll
event has happened and the Router has attempted to scroll to the
requested position/anchor. This commit saves the scroll event and
handles it again if the cards are loaded after scrolling happens.

PR Close #55566

PR Close #55275

PR Close #53471

PR Close #55599

Currently whenever a compliance test case TS file is modified, all
compliance tests in repository are rebuilt in partial compilation mode.
This is inefficient and also slows down local development where one may
use a wildcard to run all test targets inside `/test/compliance/...`.

This commit fixes this.

PR Close #55594

This commit adds detailed description for the errors NG0955 and NG0956.
Those errors correspond to the check introduced in the built-in for loop.

PR Close #55591

See associated pull request for more information.

PR Close #55589

Using `setTimeout` to delay scrolling can result in scrolling in the
next frame and cause noticeable flicker. This commit scrolls as soon as
the next render happens (or in `setTimeout` if a render does not happen
before then).

fixes #53985

PR Close #55105

Format the remaining unformatted files in the repository

PR Close #55580

Any filename but the main.ts is now editable.

PR Close #54989

fixes #53911

PR Close #55551

PR Close #55547

Co-authored-by: Sonu Kapoor <sonukapoor@users.noreply.github.com>

PR Close #55209

PR Close #53819

This allows tracking of which tools generated which XMB files and helps attribute Angular usage.

PR Close #54865

Migrate formatting to prettier for compiler-cli from clang-format

PR Close #55485

Migrate formatting to prettier for zone.js from clang-format

PR Close #55427

Migrate formatting to prettier for core from clang-format

PR Close #55488

The caveat here is that this needs to be done before creating the
fixture. There are some technical issues to overcome with disabling it
after it was already enabled, related to detaching from `ApplicationRef`
without other side effects.

PR Close #55494

Fixes several issues with the `HttpClient` migration that showed up after I tried updating the Material docs site to the latest v18 release. Includes:
* The migration was assuming that all Angular decorators have at least one argument. This led to a null pointer error that broke the v18 update process when I was testing it.
* The migration incorrectly reimplemented the detection of classes with Angular decorators. This can cause code to be migrated incorrectly and doesn't handle cases like import aliases. I've switched it to use the existing tooling for detecting decorated classes.
* The migration was trying to migrate directives, even though they don't support the `imports` field.
* The migration was detecting `TestBed.configureTestingModule` calls using a raw string match which is very fragile and can be broken by the user's formatting.
* There were syntax errors in the unit tests.
* There were type checking errors in the unit tests, for example none of them were importing the Angular decorators that they were migrating.

There's more room for improvement, but this should resolve the most glaring issues without having to rewrite too much.

PR Close #55557

fixes #54227
fixes #50943

PR Close #55553

fixes #49566

PR Close #55553

The image was replaced by the following mermaid chart.

PR Close #55553

fixes #55507

PR Close #55550