-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
MatFormField documentation should prefer outline/fill style #14792
Comments
Do you mean the legacy and standard options are no longer supported? I am interested in taking up this as my first issue. |
This issue is just about the documentation preferring one setting over the other. Feel free to send a PR! |
Will do |
I found the link to the doc if it can help : https://material.io/design/components/text-fields.html#usage I think this default affectation of appearance in the |
I am providing an example for both in the overview (basic) example, then using mainly outline over filled, assuming once you see the overview example you get the basic idea. The material spec isn't clear on which is the default appearance of a text field. I will send a PR tonight. |
Hi jelbourn, It would be helpful if you provide the default appearance so that we can avoid further changes in the future. |
@mmalerba do you have any input on this? |
Yeah, we should update the docs to show outline or fill form-fields, unless the example is specifically trying to demonstrate something about one of the other appearances. If people are looking to change the default in their app, they can do that with this injection token: https://github.com/angular/material2/blob/master/src/lib/form-field/form-field.ts#L93 |
@mmalerba if the other two appearances (legacy and standard) have been dropped shouldn't they be omitted from the documentation all together? |
I think unless they are deprecated and removed they should stay in the documentation. |
So is that the final decision to keep the "standard" and "legacy" style in the doc ? And if that's the case is there any point in keeping the issue open :) ? |
@Orodan yes there is still a point as the examples need to be updated to use filled or outline by default. The legacy/standard should only be used in the section describing the 4 different appearances. Currently only the appearance example includes fill or outline appearances. All other examples use legacy and need to be updated to fill or outline. @mmalerba what will be the default in the future (maybe v10?) fill? |
I'm fine with either fill or outline being the new default. I don't think its important which one, but its nice to have the concept of a default since that can be overridden globally with a provider to change the whole app at once. |
- stop using the soon to be deprecated legacy appearance by default Fixes #14792
- stop using the soon to be deprecated legacy appearance by default Fixes #14792
) - stop using the soon to be deprecated legacy appearance by default Fixes #14792
…nce by default - stop using the soon to be deprecated legacy appearance by default Relates to angular#14792
|
…nce by default - stop using the soon to be deprecated legacy appearance by default - fix issues where labels were specified in the `placeholder` attribute - instead of a `mat-label` Relates to angular#14792
…nce by default - stop using the soon to be deprecated legacy appearance by default - fix issues where labels were specified in the `placeholder` attribute - instead of a `mat-label` Relates to angular#14792
…ular#18222) - stop using the soon to be deprecated legacy appearance by default Fixes angular#14792
…nce by default (angular#18252) - stop using the soon to be deprecated legacy appearance by default - fix issues where labels were specified in the `placeholder` attribute - instead of a `mat-label` Relates to angular#14792
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
In the most recent Material Design update, the "standard" / "legacy" style is now omitted from the spec with only the outline and fill styles remaining. We should update our own documentation and examples to reflect this update.
The text was updated successfully, but these errors were encountered: