Skip to content
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

Move autoprefixer browser compatibility info from build.md to browser-support.md #26525

Closed
jenniferfell opened this issue Oct 17, 2018 · 2 comments
Assignees
Labels
feature Issue that requests a new feature freq3: high
Milestone

Comments

@jenniferfell
Copy link
Contributor

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[X ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

https://next.angular.io/guide/build#configuring-browser-compatibility
contains information about using Autoprefixer to ensure compatibility with different browser and browser versions.

Expected behavior

This content makes more sense in Browser Support
https://next.angular.io/guide/browser-support

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Request from @IgorMinar during a doc review.
Easier to find if all browser-specific information is in one location.

Environment


Angular version: X.Y.Z


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

@jenniferfell jenniferfell added feature Issue that requests a new feature comp: docs freq3: high labels Oct 17, 2018
@ngbot ngbot bot added this to the Backlog milestone Oct 17, 2018
@jenniferfell
Copy link
Contributor Author

@IgorMinar Do I recall correctly that you want us to move this content? Thx

@jenniferfell jenniferfell modified the milestones: Backlog, v7.0 Oct 17, 2018
@IgorMinar IgorMinar self-assigned this May 25, 2021
IgorMinar added a commit to IgorMinar/angular that referenced this issue May 25, 2021
…uide

I simplified the content significantly since most of it is not relevant any more.

Fixes angular#26525
@zarend zarend closed this as completed in 40bbcaa May 26, 2021
zarend pushed a commit that referenced this issue May 26, 2021
…uide (#42334)

I simplified the content significantly since most of it is not relevant any more.

Fixes #26525

PR Close #42334
umairhm pushed a commit to umairhm/angular that referenced this issue May 28, 2021
…uide (angular#42334)

I simplified the content significantly since most of it is not relevant any more.

Fixes angular#26525

PR Close angular#42334
iRealNirmal pushed a commit to iRealNirmal/angular that referenced this issue Jun 4, 2021
…uide (angular#42334)

I simplified the content significantly since most of it is not relevant any more.

Fixes angular#26525

PR Close angular#42334
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Issue that requests a new feature freq3: high
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants