Project import generated by Copybara.

PiperOrigin-RevId: 292612246

Author: material-web-copybara

docs/open_source/rotation.md

@@ -0,0 +1,111 @@
+# Rotation
+
+[TOC]
+
+This page outlines responsibilities for the oncall rotation and issue triaging
+of MDC Web.
+
+## Before you start
+
+*   Complete MDC Web [onboarding](http://go/mdc-web-onboard) process.
+*   Join
+    [MDC Web rotation](https://rotations.corp.google.com/rotation/5708184800985088)
+    calendar.
+*   Add "Material Web Triage" meeting to your calendar.
+*   Go to
+    [MDC Web ZenHub Dashboard](https://goto.google.com/mdc-web-triage-bugs) to
+    see Untriaged issues. (Sort Untriaged pipeline
+    [by New](https://screenshot.googleplex.com/r90Yeco4ebw.png))
+*   Set up notifications of your GitHub profile to receive emails for any
+    activity on MDC Web
+    [GitHub repository](https://github.com/material-components/material-components-web)
+    when you're on-call.
+
+## Rotation
+
+Responsibilities of rotation on-call include:
+
+*   Responding to GitHub
+    [issues](https://github.com/material-components/material-components-web/issues)
+*   Code reviewing external / internal GitHub
+    [pull requests](https://github.com/material-components/material-components-web/pulls)
+    (PR's)
+*   Importing external GitHub PR's when they're ready to merge. See
+    go/mdc-web-g3sync
+
+### Issues
+
+Being on-call does not mean you have be the one to actually fix issues, we
+simply triage. Issues may fall in one of the following categories.
+
+#### Feature Requests
+
+First, check if this request is in the [spec](https://material.io/guidelines).
+If you're not sure, reach out to Material System UX on-call - go/system-team or
+open a thread in Material System chat room:
+
+*   If it is not in spec, respond on the PR that we do not accept feature
+    requests for components that are not in our spec, and close it.
+*   If it is in the spec, discuss in triage meeting and move it to backlog.
+
+#### Bugs
+
+When a bug is reported, first ensure it has clear reproducible steps with
+sufficient information. If not, point them to our
+[bug template](https://github.com/material-components/material-components-web/issues/new?assignees=&labels=bug&template=--bug-report.md&title=%5BComponentName%5D+title)
+and ask for more information.
+
+If you're able to reproduce the bug and it is a legitimate bug in MDC Web,
+respond that you were able to reproduce the bug and move it to backlog. If
+you're not able to reproduce the bug, ask for more information.
+
+If the bug is small, encourage them to open a PR before moving it to backlog.
+
+#### Other issues
+
+There are other issues outside of FR's or bugs, although try not to spend too
+much time investigating issues that are out of scope for MDC Web. Issues can be
+closed if you think they are out of scope.
+
+*   There are a few **installation problems** that we can help with, such as,
+    installing MDC Web components and usage. However, it's best if the answer to
+    this question is a link to documentation. If it is out of scope, tell the
+    reporter we do not have the expertise to help them with this question,
+    suggest they ask on Stack Overflow for better results, and close the issue.
+*   Respond to any **general questions** and see if we're missing any
+    documentation. Encourage them to post on Stack Overflow instead and close
+    it.
+
+### Pull requests
+
+Any external contributions received via GitHub
+[pull requests](https://github.com/material-components/material-components-web/pulls)
+on MDC Web repo needs to be reviewed or needs attention. Googlers should always
+send CLs.
+
+Follow these steps to address any external contributions:
+
+*   When you're reviewing code, identify if PR contains any breaking change. If
+    it is a huge breaking change, ask the author to revert any breaking changes
+    or close the PR.
+*   Follow go/mdc-web-g3sync to import a PR into google3/. (You may need to add
+    additional changes in google3, such as updating BUILD rules.)
+*   PR can't be merged without importing it into google3.
+*   Always run a TGP (go/tgp) on the imported CL.
+
+## Triage meeting
+
+Triage meeting happens every Friday. If you're on-call that week, attendance is
+mandatory.
+
+On-call primary drives this meeting. Triaging involves the following steps:
+
+*   Open [MDC Web ZenHub Dashboard](https://goto.google.com/mdc-web-triage-bugs)
+    and present it to everyone.
+*   Sort "Untriaged" pipeline by "New" (any new issues that are opened
+    automatically appear here).
+*   Go through issues that you think that needs team discussion.
+
+In most of the cases, the oncall should have already gone through all new issues
+and have a good understanding of the issue. This makes the triage meeting
+smoother to discuss.

docs/open_source/triage.md

@@ -95,16 +95,13 @@
   .mdc-text-field__input {
     // Exclude setting line-height to keep caret (text cursor) same height as the input text in iOS browser.
     @include typography-mixins.typography(subtitle1, $exclude-props: (line-height), $query: $query);
+    @include input-padding_($query: $query);
 
     @include feature-targeting-mixins.targets($feat-structure) {
       align-self: flex-end;
       box-sizing: border-box;
       width: 100%;
       height: 100%;
-      padding:
-        variables.$input-padding-top
-        variables.$input-padding
-        variables.$input-padding-bottom + variables.$input-border-bottom;
       border: none;
       border-radius: 0;
       background: none;
@@ -162,10 +159,7 @@
 
     // Vertically center aligns the text input placeholder and value for only filled variant.
     .mdc-text-field--no-label:not(.mdc-text-field--outlined):not(.mdc-text-field--textarea) & {
-      @include feature-targeting-mixins.targets($feat-structure) {
-        padding-top: 16px;
-        padding-bottom: 16px + variables.$input-border-bottom;
-      }
+      @include input-no-label-padding_($query: $query);
     }
   }
 
@@ -445,20 +439,18 @@
     height: $height;
   }
 
-  // Target only dense text field.
-  @if $height <= 40px {
-    // Target only IE 11.
-    @media all and (-ms-high-contrast: none), (-ms-high-contrast: active) {
-      .mdc-text-field__input {
-        @include feature-targeting-mixins.targets($feat-structure) {
-          // Set line-height to the height of input element excluding padding & border.
-          line-height:
-            $height
-            - variables.$input-padding-top
-            - variables.$input-padding-bottom
-            - variables.$input-border-bottom;
+  @if $height < variables.$minimum-height-for-filled-label {
+    // Filled text fields must be tall enough to display a label
+    &:not(.mdc-text-field--outlined):not(.mdc-text-field--textarea) {
+      @include feature-targeting-mixins.targets($feat-structure) {
+        .mdc-floating-label {
+          display: none;
         }
       }
+
+      .mdc-text-field__input {
+        @include input-no-label-padding_($query: $query);
+      }
     }
   }
 }
@@ -741,6 +733,26 @@
 
 // Baseline
 
+@mixin input-padding_($query: feature-targeting-functions.all()) {
+  $feat-structure: feature-targeting-functions.create-target($query, structure);
+
+  @include feature-targeting-mixins.targets($feat-structure) {
+    padding:
+      variables.$input-padding-top
+      variables.$input-padding
+      variables.$input-padding-bottom + variables.$input-border-bottom;
+  }
+}
+
+@mixin input-no-label-padding_($query: feature-targeting-functions.all()) {
+  $feat-structure: feature-targeting-functions.create-target($query, structure);
+
+  @include feature-targeting-mixins.targets($feat-structure) {
+    padding-top: 0;
+    padding-bottom: variables.$input-border-bottom;
+  }
+}
+
 @mixin disabled_($query: feature-targeting-functions.all()) {
   $feat-structure: feature-targeting-functions.create-target($query, structure);
 
@@ -1006,9 +1018,9 @@
   }
 
   .mdc-text-field__input {
+    @include outlined-input-padding_($query: $query);
     @include feature-targeting-mixins.targets($feat-structure) {
       display: flex;
-      padding: 12px 16px 14px;
       border: none !important; // FF adds unwanted border in HC mode on windows.
       background-color: transparent;
       z-index: 1;
@@ -1026,6 +1038,14 @@
   }
 }
 
+@mixin outlined-input-padding_($query: feature-targeting-functions.all()) {
+  $feat-structure: feature-targeting-functions.create-target($query, structure);
+
+  @include feature-targeting-mixins.targets($feat-structure) {
+    padding: 12px 16px 14px;
+  }
+}
+
 @mixin hover-outline-color_($color, $query: feature-targeting-functions.all()) {
   &:not(.mdc-text-field--focused):hover {
     .mdc-notched-outline {

packages/mdc-textfield/_mixins.scss

@@ -73,6 +73,7 @@ $textarea-disabled-background: rgba(249, 249, 249, 1) !default;
 $outlined-stroke-width: 2px !default;
 $height: 56px !default;
 $minimum-height: 40px !default;
+$minimum-height-for-filled-label: 52px !default;
 $maximum-height: $height !default;
 $density-scale: density-variables.$default-scale !default;
 $density-config: (