angular / components

Component infrastructure and Material Design components for Angular
https://material.angular.io
MIT License
24.34k stars 6.74k forks source link

Datepicker uses md-" (edited with real issue) #7302

Closed bradtaniguchi closed 7 years ago

bradtaniguchi commented 7 years ago

"Edit: Not sure why or how my empty template was submitted, didn't even write anything yet :/"

Bug, feature request, or proposal:

Bug

What is the expected behavior?

Angular2 Material with angular-material-prefix-updater renders the mat-datepicker component correctly.

What is the current behavior?

having the mat-datepicker component on the page produces an error image when using the angular-material-prefix-updater compatibility provider.

What are the steps to reproduce?

Place the mat-datepicker component onto the page and use the compatibility provider.

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular: 4.4.3 Material: 2.0.0-beta.11 OS: Ubuntu 16.04.3 LTS Typescript: 2.5.2

Is there anything else we should know?

After browsing through the code, it appears that the datepicker's internal component use the "md-" prefix. See here and here

josephperrott commented 7 years ago

Marking as closed as you should already be able to use mat prefixes in your templates.

bradtaniguchi commented 7 years ago

@josephperrott Sorry the issue was somehow submitted before I could write anything, updated with the actual issue.

willshowell commented 7 years ago

@bradtaniguchi is this with material2-builds?

bradtaniguchi commented 7 years ago

@willshowell No it is not

willshowell commented 7 years ago

Here is a plunker of it working with beta.11

https://plnkr.co/edit/UPwyLI0uG0EPpA8AercK?p=preview

bradtaniguchi commented 7 years ago

I found the issue, the mdSuffix wasn't changed to matSuffix, once that was changed everything was working normally again.

Thank you

angular-automatic-lock-bot[bot] commented 5 years ago

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.