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
13.3.0
<style scoped> >>> .foo { font-weight: bold; } </style>
is compiled to:
[data-v-5026efab] .foo { font-weight: bold; }
BUT
<style scoped> /deep/ .foo { font-weight: bold; } </style>
[data-v-5026efab].foo { font-weight: bold; }
Exact same compilation.
Note the removed space during the /deep/ compilation.
/deep/
For me, it comes from theses lines:
vue-loader/lib/style-compiler/plugins/scope-id.js
Lines 33 to 35 in 5673319
I don't understand why we should remove the space after just in this case. If it's done on purpose this should be documented:
https://vue-loader.vuejs.org/en/features/scoped-css.html In those cases you can use the /deep/ combinator instead - it's an alias for >>> and works exactly the same.
I can make a PR if you want.
The text was updated successfully, but these errors were encountered:
c303312
Thanks @yyx990803!
Sorry, something went wrong.
fix: avoid removing space after /deep/ when used directly (close vuej…
aabe3fe
…s#1035)
No branches or pull requests
Version
13.3.0
Steps to reproduce
is compiled to:
BUT
is compiled to:
What is expected?
Exact same compilation.
What is actually happening?
Note the removed space during the
/deep/
compilation.For me, it comes from theses lines:
vue-loader/lib/style-compiler/plugins/scope-id.js
Lines 33 to 35 in 5673319
I don't understand why we should remove the space after just in this case. If it's done on purpose this should be documented:
I can make a PR if you want.
The text was updated successfully, but these errors were encountered: