docs-bug(INPUT): matNativeControl vs matInput input disambiguation

Open Beginner friendly
#28,501 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
angular
Domain
documentation

Research direction

Read the Input overview documentation at material.angular.io/components/input/overview, including the Input and FormField pages and the existing matNativeControl and matInput examples. Clarify what matNativeControl is, how it differs from matInput, and when to use it; done means the selector's purpose and choice are apparent before the example appears.

Written by the indexing model from the issue text.

Description

docs P4
Documentation Feedback

It's not apparent what a matNativeControl is, what the differences to matInput are, or what problem it solves.
The documentation for with matNativeControl is thrown in with matInput on one page without ever mentioning why to use one over the other.
It comes out of nowhere after showing a matInput in your example, first thing on the page.
Please amend the Input/FormField pages to clarify this selector.

Affected documentation page

https://material.angular.io/components/input/overview

Dominant language
TypeScript
Stars
25k
Forks
6.8k
Avg merge
1d 2h
Merged PRs (30d)
81

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/components

All issues in angular/components

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.