-
Notifications
You must be signed in to change notification settings - Fork 27k
docs: Add support for previous Chrome release #48669
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
Conversation
Previous Chrome stable version should also be supported
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Reviewed-for: global-approvers
|
This PR was merged into the repository by commit 01be0e2. |
Previous Chrome stable version should also be supported PR Close #48669
|
Came across this PR by coincidence. The CLI will need to update it's browserslist configuration to also reflect this change. (Will do a PR tomorrow) |
…lude last 2 Chrome versions angular/angular#48669 added support for the last 2 Chrome versions
…2 Chrome version angular/angular#48669 added support for the last 2 Chrome versions
angular/angular#48669 added support for the last 2 Chrome versions
angular/angular#48669 added support for the last 2 Chrome versions
…lude last 2 Chrome versions angular/angular#48669 added support for the last 2 Chrome versions
…2 Chrome version angular/angular#48669 added support for the last 2 Chrome versions
…lude last 2 Chrome versions angular/angular#48669 added support for the last 2 Chrome versions
…2 Chrome version angular/angular#48669 added support for the last 2 Chrome versions
…lude last 2 Chrome versions angular/angular#48669 added support for the last 2 Chrome versions (cherry picked from commit 97907ad)
…2 Chrome version angular/angular#48669 added support for the last 2 Chrome versions (cherry picked from commit 7b0c1ce)
Previous Chrome stable version should also be supported PR Close angular#48669
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Previous Chrome stable version should also be supported
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information