GitHub user MrRaindrop opened a pull request:
https://github.com/apache/incubator-weex/pull/219
chang viewport adapting algorithm.
# intro
Request to enable viewport adapting algorithm changing for weex-vue-render.
The previous way to adapt different screens is by setting viewport meta in the
head. The compatibility in some devices is un-tested and the implementation for
this meta in some browsers is not so reliable. What's more, some user-defined
components in this changed viewport environment is not working correctly, since
those components assume current viewport is a more common value, like
device-width, and they draw UI depending on this.
So this pr solved this problem by introducing realtime recalculation for
component's styles, which are scaled-up/down value to adapt current
device-width, to enable the consistency in all the devices with varies of
screens. This pr also solve the problem that the scale values used in
`dom.scrollToElement` and `animation.transition` wouldn't adapt to different
screens.
This pr also enable runtime autoprefix for styles, which means users don't
have to put `$processStyle` or `autoprefixer` in their vue-loader config. The
render will do this for users automatically and they don't have to worry about
it.
# changelog:
* change viewport adapting algorithm by recalculating styles during runtime.
* discard $processStyle and autoprefixer config for vue-loader.
* add test cases.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MrRaindrop/incubator-weex 0.11-dev
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-weex/pull/219.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #219
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
