- Remove checkbox adapter and foundation
- Replace ripple directive with lazy `mwc-ripple`
- Fix Closure Compiler renaming issues
Related #892
Related #894
Related #882
PiperOrigin-RevId: 302740256
`@observer` does not mesh well with strict internal tooling, and should not be necessary for components that do not use MDC Foundations.
Refactor `BaseElement` and `FormElement` to remove exports of `@observer`, and add imports for `@observer` in components that need it.
Related #892
PiperOrigin-RevId: 301450145
Focusing on activation is on by default in MDC, but the Foundation exposes a function to disable this behavior for some applications
Also, remove the styles block from the base element
PiperOrigin-RevId: 300174710
- mwc-ripple is now fully self-contained for styling and DOM manipulation
- Reuse MDCRippleFoundation and MDCRippleAdapter
- consider refactoring into mwc-ripple later
- Remove `active` property
- Add `--mdc-ripple-color`, `--mdc-ripple-fg-opacity` and `--mdc-ripple-hover-opacity` CSS Custom Properties
- Make FormElement and `mwc-formfield` support asynchronous ripple properties
- Add `RippleHandlers` to make integration with ripple containers easier
- Hide ripple when set to `disabled`
- Add `light` property for ripples on dark surfaces
Related #892
Related #894Fixes#247
PiperOrigin-RevId: 297968015
- Make `mdcFoundationClass` and `mdcFoundation` optional
- Make exports from FormElement more explicit
- Replace MDCRippleFoundation type import in FormElement with an explicit RippleInterface
- Clean up CHANGELOG
Related #892Fixes#893
PiperOrigin-RevId: 296509910
- Sass now has "default" imports that should handle `@material/theme` to
mean `@material/theme/_index.scss` that `node-sass-import` did not
understand
Fixes#850
- We no longer trigger an exception in the blocking elements polyfill in some scenarios. This happened when a dialog was opened and then quickly disconnected before the opening animation finished, because we were trying to add a disconnected element to the blocking elements stack. We now close the foundation (or don't open in the first place if we're _really_ early) on disconnect, which cancels the opening timer. This is a scenario that can easily crop up in tests, since tests don't necessarily wait for the opening event before tearing down the test fixture DOM.
- If a dialog is opened, disconnected, and re-connected, we now re-show the opening animation, and correctly put the dialog back onto the blocking elements stack.
PiperOrigin-RevId: 281077807
