@angular/material 18.0.0-rc.1 → 18.0.0-rc.3

package/core/tokens/m3/mdc/_form-field.scss

@@ -1,25 +0,0 @@
-@use 'sass:map';
-@use '../../token-utils';
-
-// The prefix used to generate the fully qualified name for tokens in this file.
-$prefix: (mdc, form-field);
-
-/// Generates the tokens for MDC form-field
-/// @param {Map} $systems The MDC system tokens
-/// @param {Boolean} $exclude-hardcoded Whether to exclude hardcoded token values
-/// @param {Map} $token-slots Possible token slots
-/// @return {Map} A set of tokens for the MDC form-field
-@function get-tokens($systems, $exclude-hardcoded, $token-slots) {
-  $tokens: (
-    // TODO: MDC currently doesn't provide tokens for the form field so we need to
-    // define them ourselves. Clean this up once b/246297033 is resolved.
-    label-text-color: map.get($systems, md-sys-color, on-surface),
-    label-text-font: map.get($systems, md-sys-typescale, body-medium-font),
-    label-text-line-height: map.get($systems, md-sys-typescale, body-medium-line-height),
-    label-text-size: map.get($systems, md-sys-typescale, body-medium-size),
-    label-text-tracking: map.get($systems, md-sys-typescale, body-medium-tracking),
-    label-text-weight: map.get($systems, md-sys-typescale, body-medium-weight),
-  );
-
-  @return token-utils.namespace-tokens($prefix, $tokens, $token-slots);
-}

package/dialog/_mdc-dialog-structure-overrides.scss

@@ -1,58 +0,0 @@
-// Mixin that can be included to override the default MDC dialog styles to fit
-// our needs. See individual comments for context on why certain styles need to be modified.
-@mixin private-dialog-structure-overrides($content-max-height) {
-  // MDC dialog sets max-height and max-width on the `mdc-dialog__surface` element. This
-  // element is the parent of the portal outlet. This means that the actual user-content
-  // is scrollable, but as per Material Design specification, only the dialog content
-  // (indicated by `matDialogContent`) should be scrollable while title and actions are fixed.
-  // This is not an issue for MDC because they make the assumption that the content, title and
-  // action elements are direct children of the surface element. We work around this by setting
-  // an explicit max-height for the content element, so that the content is scrollable. This
-  // matches the behavior from the non-MDC dialog and is backwards compatible.
-  .mat-mdc-dialog-content {
-    max-height: $content-max-height;
-  }
-
-  .mat-mdc-dialog-container {
-    // MDC by default expands the dialog using a fixed position to the viewport dimensions.
-    // MDC does this because the dialog element contains the backdrop/scrim too. This is not
-    // the case for our implementation of the dialog that uses the CDK overlay backdrop. We
-    // update the dialog to a `static` position and reset the height/width so that the dialog
-    // scales based on the content, respecting the boundaries of the CDK overlay container.
-    // This is necessary to support for custom position strategies in the overlay.
-    position: static;
-    // The MDC dialog is designed to always stay in the DOM. Hence MDC sets `display: none`
-    // when the dialog is closed. Since we only attach the dialog to the DOM when the dialog
-    // should open, and we want to be able to focus the dialog immediately when we attach it,
-    // we override the default `display` so that the dialog is focusable.
-    display: block;
-
-    // MDC sets `min-height`, `max-height`, `min-width` and `max-height` We can't rely on
-    // this for the dialog content scrolling (as explained above), and since we allow for
-    // custom positioning through overlay configuration, we remove the rectangle
-    // restrictions and scale based on the CDK overlay container.
-    &, .mdc-dialog__container, .mdc-dialog__surface {
-      max-height: inherit;
-      min-height: inherit;
-      min-width: inherit;
-      max-width: inherit;
-    }
-
-    .mdc-dialog__surface {
-      width: 100%;
-      height: 100%;
-    }
-  }
-
-  // When a component is passed into the dialog, the host element interrupts
-  // the `display:flex` from affecting the dialog title, content, and
-  // actions. To fix this, we make the component host `display: contents` by
-  // marking its host with the `mat-mdc-dialog-component-host` class.
-  //
-  // Note that this problem does not exist when a template ref is used since
-  // the title, contents, and actions are then nested directly under the
-  // dialog surface.
-  .mat-mdc-dialog-component-host {
-    display: contents;
-  }
-}