fix(weex): stop trim css units in richtext component #6927
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
+ Remove the `trimCSSUnit` method. + Modify the test cases to support css units. + Add flow type annotations.
erweixin
pushed a commit
to erweixin/vue
that referenced
this pull request
Dec 15, 2017
+ Remove the `trimCSSUnit` method. + Modify the test cases to support css units. + Add flow type annotations.
lovelope
pushed a commit
to lovelope/vue
that referenced
this pull request
Feb 1, 2018
+ Remove the `trimCSSUnit` method. + Modify the test cases to support css units. + Add flow type annotations.
This was referenced Mar 14, 2018
f2009
pushed a commit
to f2009/vue
that referenced
this pull request
Jan 25, 2019
+ Remove the `trimCSSUnit` method. + Modify the test cases to support css units. + Add flow type annotations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
The PR fulfills these requirements:
devbranch for v2.x (or to a previous version branch), not themasterbranchOther information:
The native render engine of Weex supports the
pxunit, and recommend writing CSS units.trimCSSUnitmethod.