Did a rebase to latest main, files changed tab now looks correct.

Did a rebase to latest main, files changed tab looks correct.

Will refrain from further rebases (unless stated to be required) since there is 1 approval and a few pending reviewers.

Here is a StackBlitz to test scoping of the CSS scope at-rule:
https://stackblitz.com/edit/stackblitz-starters-yucdgc?file=src%2Fmain.ts

You can run the above example using Chrome with the Experimental Web Platform features flag enabled in chrome://flags/.

On Angular 16.1.4 styles applied to my-app leak into app-hello.

This pull request should fix the style leak issue for the scope at-rule.

Looks like support was pushed to Chrome 118 [1] instead of Chrome 117.

Global Presubmit (internal-only link).

Caretaker note: TGP is "green", this PR is ready for merge.

This PR was merged into the repository by commit c27a1e6.

Here is a StackBlitz to test scoping of the CSS scope at-rule with Angular 16.2.0-next.2:
https://stackblitz.com/edit/stackblitz-starters-vcbqhb?file=src%2Fmain.ts

You can run the above example using Chrome with the Experimental Web Platform features flag enabled in chrome://flags/.

I tested with: Version 117.0.5886.0 (Official Build) canary (64-bit)

Styles are now correctly scoped.

@scope ([data-scope='main-component']) to ([data-scope]) {
  p[_ngcontent-ng-c3427923494] {
      color: red;
  }

  section[_ngcontent-ng-c3427923494] {
      background: snow;
  }
}

@scope ([data-scope='sub-component']) to ([data-scope]) {
  p[_ngcontent-ng-c3427923494] {
      color: blue;
  }

  section[_ngcontent-ng-c3427923494] {
      color: ghostwhite;
  }
}

Thank you for merging this feature.

@puckowski thank you for contributing this feature and improving Angular 👍

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}