Skip to content
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

Closed
jelbourn opened this issue Jan 10, 2019 · 15 comments · Fixed by #18222
Closed

MatFormField documentation should prefer outline/fill style #14792

jelbourn opened this issue Jan 10, 2019 · 15 comments · Fixed by #18222
Assignees
Labels
docs This issue is related to documentation material spec Issue related to the Material Design spec https://material.io/design/ P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@jelbourn
Copy link
Member

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.

@jelbourn jelbourn added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent docs This issue is related to documentation help wanted The team would appreciate a PR from the community to address this issue good first issue This issue is a good place to start for first time contributors to the project labels Jan 10, 2019
@mainawycliffe
Copy link

mainawycliffe commented Jan 15, 2019

Do you mean the legacy and standard options are no longer supported? I am interested in taking up this as my first issue.

@jelbourn
Copy link
Member Author

This issue is just about the documentation preferring one setting over the other. Feel free to send a PR!

@mainawycliffe
Copy link

Will do

@karismann
Copy link

I found the link to the doc if it can help : https://material.io/design/components/text-fields.html#usage
What's the default appearance for the form-field now ? outline or filled ?

I think this default affectation of appearance in the MatFormField class is also impacted, am I right ?

@mainawycliffe
Copy link

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.

@Suresh918
Copy link
Contributor

Hi jelbourn, It would be helpful if you provide the default appearance so that we can avoid further changes in the future.

@jelbourn
Copy link
Member Author

@mmalerba do you have any input on this?

@mmalerba
Copy link
Contributor

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

@mainawycliffe
Copy link

mainawycliffe commented Jan 19, 2019

@mmalerba if the other two appearances (legacy and standard) have been dropped shouldn't they be omitted from the documentation all together?

@manklu
Copy link

manklu commented Jan 19, 2019

@mainawycliffe

I think unless they are deprecated and removed they should stay in the documentation.

@Orodan
Copy link

Orodan commented May 3, 2019

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 :) ?

@Splaktar Splaktar added the material spec Issue related to the Material Design spec https://material.io/design/ label Jan 6, 2020
@Splaktar
Copy link
Member

Splaktar commented Jan 6, 2020

@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?

@mmalerba
Copy link
Contributor

mmalerba commented Jan 6, 2020

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.

Splaktar added a commit that referenced this issue Jan 20, 2020
- stop using the soon to be deprecated legacy appearance by default

Fixes #14792
@Splaktar Splaktar added has pr and removed good first issue This issue is a good place to start for first time contributors to the project help wanted The team would appreciate a PR from the community to address this issue labels Jan 20, 2020
@Splaktar Splaktar self-assigned this Jan 20, 2020
Splaktar added a commit that referenced this issue Jan 21, 2020
- stop using the soon to be deprecated legacy appearance by default

Fixes #14792
jelbourn pushed a commit that referenced this issue Jan 22, 2020
)

- stop using the soon to be deprecated legacy appearance by default

Fixes #14792
jelbourn pushed a commit that referenced this issue Jan 22, 2020
)

- stop using the soon to be deprecated legacy appearance by default

Fixes #14792

(cherry picked from commit 3168e94)
Splaktar added a commit to DevIntent/components that referenced this issue Jan 22, 2020
…nce by default

- stop using the soon to be deprecated legacy appearance by default

Relates to angular#14792
@Splaktar
Copy link
Member

Splaktar added a commit to DevIntent/components that referenced this issue Jan 22, 2020
…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
Splaktar added a commit to DevIntent/components that referenced this issue Jan 23, 2020
…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
jelbourn pushed a commit that referenced this issue Jan 26, 2020
…nce by default (#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 #14792
jelbourn pushed a commit that referenced this issue Jan 26, 2020
…nce by default (#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 #14792

(cherry picked from commit 0e30214)
yifange pushed a commit to yifange/components that referenced this issue Jan 30, 2020
…ular#18222)

- stop using the soon to be deprecated legacy appearance by default

Fixes angular#14792
yifange pushed a commit to yifange/components that referenced this issue Jan 30, 2020
…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
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
docs This issue is related to documentation material spec Issue related to the Material Design spec https://material.io/design/ P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants