-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(autofill): use static queries to read values used in ngOnInit #15515
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
fix(autofill): use static queries to read values used in ngOnInit #15515
Conversation
See scripts/ivy/README.md for instructions.
This makes the unit tests runnable on the ivy-2019 branch by making the following changes: * Use the unminified umd bundles. The minified bundles fail due to some yet indeterminate bug. * Update the install script to be platform independent (formerly only worked on macOS) * Skip the tree tests. Something about the tree tests crashes the test runner.
This is necessary to run `bazel` on Angular's CI
This should fix the tests for AriaDescriber, AutofillMonitor, Portal, BottomSheet, Autocomplete, and Drawer.
Reworks a test that depends on static queries and fails under Ivy.
* Fixes one unit test that was depending on static queries. * Fixes the remaining 16 failures that were due to some code that was commented out while waiting for a task which was resolved.
This makes the test pass in ivy (as well as ViewEngine) since attribute bindings are set during creating mode in ivy.
This makes a test pass both with ivy and ViewEngine
…inserting (#15359) * fix(virtual-scroll): move views that are already attached instead of inserting * fix: add more static queries for cdk virtual scroll * refactor(button): use [attr.disabled] host binding in MatButton With ivy, MatAnchor will inherit the host bindings of MatButton. The `[disabled]` binding would then be an error since HTMLAnchorElement does not have a `disabled` property. To work around this, we can simply use the `disabled` attribute instead, which will always be reflected back into the property when it exists. Also add a missing `fixture.detectChanges()` to a test.
Fixes the chip list tests that are failing under Ivy due to a known breaking change.
7 tests are impacted
In Ivy inheriting `host` bindings works correctly by merging the two declarations, whereas in ViewEngine the bindings aren't inherited at all. This means that with our current setup the `click` listener on the buttons will be invoked twice with Ivy. These changes rework the buttons so that they work both with Ivy and ViewEngine.
…tor (#15468) Due to changes in Angular it's not logical to change style values directly within a constructor. This should be done instead within the ngOnInit lifecycle hook. This patch changes this behavior for the `ToolTip` component.
Fixes the stepper's content not being shown on the first render with Ivy, because we assume that the template with be present on init.
src/material-examples/text-field-autofill-monitor/text-field-autofill-monitor-example.ts
Outdated
Show resolved
Hide resolved
kara
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
crisbeto
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@pkozlowski-opensource I think this needs to be rebased |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |


No description provided.