* No longer runs e2e tests inside of Saucelabs because Chrome is also installed on Travis CI and we should keep Saucelabs available for other browsers that don't run inside of Dockers or Travis.
* No longer just runs the tests against the first browser of a test platform (travis, saucelabs, browserstack)
* Stability is more valuable than speed (runs sequentially on CI now)
* Update Saucelabs Connect
* Remove unused spec reporter
* Update from Edge 14 to Edge 17
* Fix pixel deviations in Edge 17
* A `index.ts` file for the Material package has been added at some point. To be consistent, we switch away from `public-api.ts` to `index.ts` for the output of the individual packages.
* feat(virtual-scroll): fixed size virtual scroll (#9316)
* feat(virtual-scroll): fixed size virtual scroll
* address some comments
* change VirtualScrollStrategy interface a bit
* address some more comments
* fix lint & build
* chore: move virtual-scroll to cdk-experimental (#9974)
* virtual-scroll: simplify scroll listener logic (#10102)
* virtual-scroll: only move views that need to be moved (#10099)
* virtual-scroll: only move views that need to be moved
* address comments
* virtual-scroll: switch `throttleTime` to `sampleTime` (#10179)
* virtual-scroll: switch throttleTime to sampleTime
* add comment
* virtual-scroll: allow user to pass `Observable<T[]>` (#10158)
* virtual-scroll: rename `Range` to `ListRange` to avoid confusion with native `Range` (#10220)
* virtual-scroll: add autosize scroll strategy (#10219)
* rename fixed size virtual scroll directive
* add autosize virtual scroll strategy
* add item size estimator class
* add logic for jumping rendered content based on scroll position
* address comments
* virtual-scroll: add `onContentRendered` hook to `VirtualScrollStrategy` (#10290)
* virtual-scroll: add `onContentRendered` hook to `VirtualScrollStrategy`
* address comemnts
* virtual-scroll: add incremental scroll logic in `AutosizeVirtualScrollStrategy` (#10504)
* virtual-scroll: add incremental scroll logic in `AutosizeVirtualScrollStrategy`.
This still has a couple issues that need to be ironed out and it doesn't
have the code for correcting the error between the predicted and actual
scroll position. (See various TODOs for additional things that need
work).
* fix lint
* address comments
* address comments
* fix bazel
* fix devapp
* fix lint
* cleanup
* virtual-scroll: rewrite offset in terms of "to-top" and fix a bug where items were removed too soon (#10986)
* rewrite offsets to the end of the rendered content as offsets to the
start
* add some more autosize demos for testing
* make sure not to remove too many items
* address comments
* virtual-scroll: address amcdnl's feedback (#10988)
* rewrite offsets to the end of the rendered content as offsets to the
start
* add some more autosize demos for testing
* make sure not to remove too many items
* virtual-scroll: address amcdnl's feedback
* virtual-scroll: fix updating when data changes and add trackBy demos (#11085)
* virtual-scroll: add logic to correct the scroll position as user move… (#11137)
* virtual-scroll: add logic to correct the scroll position as user moves toward the top
* address comments
* fix(scrolling): adds right to fix pushed content (#11192)
* fix(scrolling): adds right to fix pushed content
* chore: address feedback
* chore: address pr feedback
* virtual-scroll: add tests for fixed size items (#11255)
* virtual-scroll: add tests for fixed size items
* address comments
* fix bug in fixed size strategy
* fix bazel build
* virtual-scroll: add tests for `cdkVirtualFor` logic (#11275)
* merge fixed size test components into one
* add tests for cdkVirtualFor logic
* allow undefined to be explicitly passed as trackBy
* fix bazel build
* address comments
* add some basic tests (#11295)
* fix lint
* virtual-scroll: add e2e tests for autosize scroll strategy (#11345)
* set up virtual scroll page in e2e app
* add gulp task for e2e:watch
* add e2e tests for autosize
* address comments
* address comments
* fix lint and tests
* fix bad rebase
* fix(scrolling): scrollbar jump when data change on scroll (#11193)
* fix(scrolling): data change not updating size
* chore: remove todo
* chore: more performant fix for jump
* move autofill to cdk
* move textarea autosize into cdk
* fix bazel build
* rename input to text-field
* set resize back to none for autosize in input css
* fix tsconfig
Currently if something throws an error right after Karma has initialized, the log will look something like the following:
```
HeadlessChrome 0.0.0 (Windows 10 0.0.0) ERROR
{
"originalErr": {},
"__zone_symbol__currentTask": {
"type": "microTask",
"state": "notScheduled",
"source": "Promise.then",
"zone": "<root>",
"cancelFn": null,
"runCount": 0
}
}
```
These changes log out the stack trace explicitly so we have some more info to work with if it happens.
This adds bazel test rules for everything under cdk/ and sets CircleCI Overlay tests don't work because there's not yet a way to pass through flags to the browser. These issues will be addressed in a follow-up PR.
* Adds an initial implementation of the new `MatBottomSheet` service that allows users to display component-based or template-based bottom sheets.
* Sets up the various boilerplate and infrastructure necessary for a new component.
Note: this is an initial implementation that has the necessary functionality, styles and accessibility. More docs, examples and touch gestures will be added in a follow-up.
In order to align with the `angular/angular` setup, we also remove the temporary Chrome Headless Sandbox workaround in favor of faster Travis CI containers. To be able to still use headless chrome, we specify the `no-sandbox` flag.
Reference https://github.com/angular/angular/pull/21641
Runs local tests in Chrome Headless. This speeds up the tests and also ensures more test stability. On Windows there are a lot of pixel deviation failures because the tests seemed to be affected by the screen resolution or window frame.
By running the tests headless, the Chrome launcher has more control about the rendering and pixel deviations like before won't happen anymore. It's still the same Chrome that runs, just that the screen is kind of emulated like in XVFB.
* No longer explicitly specifies the Chrome Driver version for the e2e tests. The chrome driver associated with the latest Chrome version will be used now.
After the switch to lettable operators, we had started importing all operators via `rxjs/operators`. These changes switch us back to only importing the individual ones and add some linting so it doesn't happen in the future.
Bumps the required RxJS version to 5.5.0 and gets rid of our RxChain in favor of using the lettable Rx operators. Refactors all the usages and updates the configs.
Fixes#7275.
Refactors all of the usages of the deprecated `Http` by replacing them with the `HttpClient`.
BREAKING CHANGE: Material now requires `@angular/common` instead of `@angular/http` and uses `HttpClient` instead of `Http`.
* No longer creates the coverage reports inside of Browserstack. The reports can be generated inside of Chrome Headless that doesn't run remotely on BrowserStack or Saucelabs.
* Move UniqueSelectionDispatcher to CDK.
BREAKING CHANGE: UniqueSelectionDispatcher, UniqueSelectionDispatcherListener and UNIQUE_SELECTION_DISPATCHER_PROVIDER are no longer
available from @angular/material and instead must be imported from @angular/cdk/collections
* Move UniqueSelectionDispatcher to CDK.
BREAKING CHANGE: UniqueSelectionDispatcher, UniqueSelectionDispatcherListener and UNIQUE_SELECTION_DISPATCHER_PROVIDER are no longer
available from @angular/material and instead must be imported from @angular/cdk/collections
* Move CdkAccordion to @angular/cdk/accordion
BREAKING CHANGE:
- CdkAccordion is now in @angular/cdk/accordion
- AccordionChild is renamed to CdkAccordionChild
- CdkAccordion no longer has displayMode and hideToggle @Inputs
- CdkAccordionItem is now a @Directive
- CdkAccordion is now exportedAs CdkAccordion for template referencing
- CdkAccordionItem is now exported as CdkAccordionItem for template referencing
Before this change, all of `@angular/material` was bundled into a
single, flat JS file.
After this change, each top-level component (i.e., each directory under
`src/lib`) will be have its own JS file (and d.ts and metadata.json).
The benefit of this change is that current versions of webpack will be
able to do a much better job of only including the code an app is using.
It also allows (but does not require) people to explicitly import from specific components,
e.g.
```
import {MdButtonModule} from '@angular/material/button';
``
For development _within Angular Material itself_ we have to use these
deeper imports because the root `@angular/material` doesn't exist until
we build the relase package.
Additionally, this PR adds a `tsconfig.json` for each dir under `src/`
with the correct path mappings for that directory, so that IDEs will
correctly generate imports.
Closure Compiler CI check is also disabled by this PR; it cannot work
with the new package structure until a release with
https://github.com/google/closure-compiler/pull/2600 is made available.
* create moment adapter
* add Moment to karma.conf.js
* use MAT_DATE_LOCALE
* tests are now running
* add in tests
* WIP: demo
* add synthetic default imports for moment
* add locale switching to demo
* fix moment import issues with tests
* fix aot
* address comments
* fix closure issue
* add additional explanation of rollup issue
* remove moment adapter demo since it is preventing sync into g3 (will add
back as a docs example in future PR).
* fix bad rebase
Paul Gschwendtner