-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Support devices which need a css prefix for flex/transform/... #4385
Comments
I just saw that the project uses autoprefixer. Does it mean it should already apply all the prefixes? |
thx @kara for merging angular/flex-layout#276! |
For Angular Material, our official browser support policy is "last two major versions of each browser" plus IE11. For Safari, this means we only support 9 and 10. |
@jelbourn The latest version of UC Browser (~10% share WW) uses the older |
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. |
Bug, feature request, or proposal:
Proposal
For our application (https://app.feedbackr.io) we need a solution which works on all (almost all) currently used mobile devices. According to http://caniuse.com/#feat=flexbox adding css prefixes adds support for many devices.
I have prepared changes in the SCSS files and the layout already looks ok. Styles which are added within templates or by typescript are not considered yet.
master...karlhaas:add-flex-prefixes
What is the expected behavior?
All devices which just need a css prefix should be supported.
What is the current behavior?
e.g. iOS8 is not supported.
What are the steps to reproduce?
use old device
What is the use-case or motivation for changing an existing behavior?
Without the support we have to use another technology for an important part of our application.
Which versions of Angular, Material, OS, browsers are affected?
latest
Is there anything else we should know?
I'm also providing changes for flex layout angular/flex-layout#276
The text was updated successfully, but these errors were encountered: