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

Support auto-prefixed style value as array (client/ssr) #5460

Merged
merged 2 commits into from Apr 17, 2017
Merged

Support auto-prefixed style value as array (client/ssr) #5460

merged 2 commits into from Apr 17, 2017

Conversation

fnlctrl
Copy link
Member

@fnlctrl fnlctrl commented Apr 17, 2017

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

When exploring css-in-js solutions for vue, I came across the fact that some auto prefixed style objects (for example, by postcss-js) cannot be directly used as style option on elements, when they have an array as value, e.g.

{ display: ['-webkit-box', '-webkit-flex', '-ms-flexbox', 'flex'] }

...which happens when a rule value needs to be prefixed, other examples:

{ backgroundImage: ['radial-gradient(...)', '-webkit-radial-gradient(...)']
{ cursor: ['-webkit-grab','grab'] }

This PR adds support for directly consuming such objects as style option.

@yyx990803 yyx990803 merged commit 38810d8 into vuejs:dev Apr 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants