Skip to content

build: add most components to kitchen-sink #4836

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

Merged
merged 2 commits into from
Jun 8, 2017

Conversation

jelbourn
Copy link
Member

Fixes a handful of issues that prevent some components from working.

Checkbox and button-toggles don't work due to an issue in platform-server.

Tabs don't work because they try to set a style property directly on initialization; this will need a more in-depth follow-up (I didn't look into that deeply).

Related to #308

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 26, 2017
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. One minor comment. Also can you fix the CI lint issue?

@@ -48,6 +48,10 @@ export class InteractivityChecker {
* @returns Whether the element is tabbable.
*/
isTabbable(element: HTMLElement): boolean {
// Nothing is tabbable on the the server 😎
Copy link
Member

@devversion devversion May 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need a lint rule for that! 😄 (joke)

this._thumbBarEl = _elementRef.nativeElement.querySelector('.mat-slide-toggle-bar');
constructor(private _elementRef: ElementRef, platform: Platform) {
// We only need to interact with these elements when we're on the browser, so only grab
// the refernece in that case.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo for reference.

Also we are already in the custom renderer? I suppose the whole custom renderer approach will be addressed in the future at some point.

Just thought that we could not create the Renderer if we are not in the browser

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the long-term plan, but that will require the secondary @angular/material/server package

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay sounds good

@jelbourn
Copy link
Member Author

Still trying to fix these test failures, which happen inconsistently locally

@jelbourn jelbourn force-pushed the kitchen-sink branch 2 times, most recently from 31b519e to e641d43 Compare May 31, 2017 23:12
@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label May 31, 2017
@jelbourn
Copy link
Member Author

jelbourn commented May 31, 2017

All failures resolved (the red status is coming from the "Deploy" tasks not running, which is something wrong with our Travis config for PRs at the moment)

@jelbourn jelbourn force-pushed the kitchen-sink branch 3 times, most recently from 9edcd1d to 5ef2422 Compare June 8, 2017 21:53
@andrewseguin andrewseguin merged commit f89c6db into angular:master Jun 8, 2017
DerekLouie pushed a commit to DerekLouie/material2 that referenced this pull request Jun 19, 2017
* build: add most components to kitchen-sink

* debug

Terrible code just exporting for the sake of asking an question to
Andrew
@jelbourn jelbourn deleted the kitchen-sink branch September 13, 2017 04:36
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants