bug(mat-form-field): input placeholder overlapping input text, SASS depreciation warning
See original GitHub issueReproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/fork/components-issue
Steps to reproduce:
- Create a form using <mat-form-field appearance="outline">
- Compare local build versus production build
Expected Behavior
What behavior were you expecting to see?
Actual Behavior
What behavior did you actually see?
After building my project with ng build --prod --configuration=production --aot
, my input fields look like this:

DEPRECATION WARNING: As of Dart Sass 2.0.0, !global assignments won't be able to
declare new variables. Consider adding `$mat-form-field-outline-dedupe: null` at the root of the
stylesheet.
╷
4645 │ $mat-form-field-outline-dedupe: $mat-form-field-outline-dedupe + 0.00001 !global;
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
node_modules/@angular/material/_theming.scss 4645:3 -mat-form-field-outline-label-floating()
node_modules/@angular/material/_theming.scss 4682:9 mat-form-field-outline-typography()
node_modules/@angular/material/_theming.scss 4951:3 mat-form-field-typography()
node_modules/@angular/material/_theming.scss 5005:3 angular-material-typography()
node_modules/@angular/material/_theming.scss 5033:3 mat-core()
src/assets/styles/modules/_nav-search.scss 2:1 @import
src/assets/styles/partials/_theme.scss 2:9 @import
src/assets/styles/_partials.scss 2:13 @import
stdin 1:9 root stylesheet
Environment
OS: macOS Catalina 10.15.4 Browser: Chrome 81.0.4044.113
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 9.1.1
Node: 13.11.0
OS: darwin x64
Angular: 9.1.2
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker
Ivy Workspace: Yes
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.901.1
@angular-devkit/build-angular 0.901.1
@angular-devkit/build-optimizer 0.901.1
@angular-devkit/build-webpack 0.901.1
@angular-devkit/core 9.1.1
@angular-devkit/schematics 9.1.1
@angular/cdk 9.2.1
@angular/cli 9.1.1
@angular/flex-layout 9.0.0-beta.29
@angular/material 9.2.1
@ngtools/webpack 9.1.1
@schematics/angular 9.1.1
@schematics/update 0.901.1
rxjs 6.5.5
typescript 3.7.5
webpack 4.42.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Mat input field placeholder overlap issue - Stack Overflow
I have a mat input field with a placeholder.I am binding data to that input field with an array coming from a service...
Read more >mat-form-field overlapping into button below : r/Angular2
i have a problem with a mat-form-field overlapping into a button. Making it so only the lower half is clickable.
Read more >Form field - Angular Material
<mat-form-field> is a component used to wrap several Angular Material components and apply common Text field styles such as the underline, floating label, ......
Read more >CHANGELOG_ARCHIVE.md - components - Fossies
cdk-text-field: prevent keyframes from getting stripped by LibSass (#12567) ... dynamic chip input placeholder changes not being propagated to form field ...
Read more >Default Theme Changelog - KendoReact - Telerik
actionsheet: use subtle text variable for description styling ... input: allow placeholder text color customization on generic input ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@crisbeto Yes, that seemed to work. The warnings are gone AND the fields are fixed.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.