We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
2.5.22
https://codesandbox.io/s/rm36pyr37q
Given a very simple component:
<template> <div v-bind:style="styleObject">This div should have a large z-index</div> </template> <script> export default { name: "HelloWorld", data() { return { styleObject: { maxWidth: "400px", minWidth: "auto", opacity: 1, padding: "5px", position: "fixed", right: "10px", top: "10px", zIndex: "100 !important" // this doesn't work // "z-index": "100 !important" // this works } }; } }; </script>
zIndex is not bound to style
zIndex
Binding zIndex does not get kebab-cased like maxWidth and minWidth. I expected it to work the same way. Passing z-index works as expected.
maxWidth
minWidth
z-index
The zIndex variable is ignored entirely.
I was creating an alert-style box that needs a high z-index to appear "on top" of other elements on the page.
The text was updated successfully, but these errors were encountered:
FYI this is not specific to zIndex. It's caused by camelCase names not converted to kebab-case when the value contains !important.
!important
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Version
2.5.22
Reproduction link
https://codesandbox.io/s/rm36pyr37q
Steps to reproduce
Given a very simple component:
zIndex
is not bound to styleWhat is expected?
Binding
zIndex
does not get kebab-cased likemaxWidth
andminWidth
. I expected it to work the same way. Passingz-index
works as expected.What is actually happening?
The
zIndex
variable is ignored entirely.I was creating an alert-style box that needs a high z-index to appear "on top" of other elements on the page.
The text was updated successfully, but these errors were encountered: