Skip to content
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

problem with sidenav component with webpack + ts-loader #539

Closed
vladimir-ivanov opened this issue May 26, 2016 · 2 comments
Closed

problem with sidenav component with webpack + ts-loader #539

vladimir-ivanov opened this issue May 26, 2016 · 2 comments

Comments

@vladimir-ivanov
Copy link

vladimir-ivanov commented May 26, 2016

Bug, feature request, or proposal:

Bug

What is the expected behavior?

the sidenav to open when clicking on the button

<button md-button="" (click)="start.open()">open</button>
<md-sidenav-layout>
    <md-sidenav #start [opened]="true" (open)="mybutton.focus()">
        Start Sidenav.
        <br>
        <button md-button #mybutton (click)="start.close()">Close</button>
    </md-sidenav>
    <md-sidenav #end align="end">
        End Sidenav.
        <button md-button (click)="end.close()">Close</button>
    </md-sidenav>

    My regular content. This will be moved into the proper DOM at runtime.
</md-sidenav-layout>

What is the current behavior?

getting an error when clicking on the button:

vendors.js:24394 TypeError: self._el_5.open is not a function
at DebugAppView._View_HomePageComponent0._handle_click_0_0 (HomePageComponent.template.js:171)
at vendors.js:12859
at vendors.js:25924
at vendors.js:26655
at ZoneDelegate.invoke (vendors.js:54344)
at Object.onInvoke (vendors.js:8927)
at ZoneDelegate.invoke (vendors.js:54343)
at Zone.runGuarded (vendors.js:54251)
at NgZoneImpl.runInnerGuarded (vendors.js:8960)
at NgZone.runGuarded (vendors.js:7461)

What are the steps to reproduce?

Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, browsers are affected?

Is there anything else we should know?

@vladimir-ivanov
Copy link
Author

fixed by including
import '@angular2-material/core';
import '@angular2-material/button';
import '@angular2-material/card';
import '@angular2-material/checkbox';
import '@angular2-material/sidenav';
import '@angular2-material/input';
import '@angular2-material/list';
import '@angular2-material/radio';
import '@angular2-material/progress-bar';
import '@angular2-material/progress-circle';
import '@angular2-material/toolbar';

@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 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant