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

fix tab navigation for external links #4183

Merged
merged 1 commit into from
Mar 16, 2016
Merged

Conversation

sad270
Copy link
Contributor

@sad270 sad270 commented Mar 9, 2016

PR #4177 opening again in mdl-1.1 branch

This code is duplicate of lines 552 to 557 without allowing external links.

This code is duplicate of lines 552 to 557 without allowing external links.
@sad270
Copy link
Contributor Author

sad270 commented Mar 16, 2016

@sgomes i do what you ask to me but I got 'continuous-integration/drone — the build failed', is my PR good ?

@sgomes
Copy link
Contributor

sgomes commented Mar 16, 2016

@sad: Looks like our CI was acting up. I've restarted the build, let's see how it goes.

@sgomes
Copy link
Contributor

sgomes commented Mar 16, 2016

Looks good now, thanks! Merging.

sgomes added a commit that referenced this pull request Mar 16, 2016
fix tab navigation for external links
@sgomes sgomes merged commit 3eff895 into google:mdl-1.1 Mar 16, 2016
@ross-nordstrom
Copy link

This didn't fix the issue for me. I'm hitting this same reference issue in tabs.js.

Should I be using tabs in a different way to benefit from this fix??

What I'm doing

I'm trying to use MDL tabs with ui-sref links (using angular's `ui-router'), so I only render tab content on the page for the selected tab.

Here's a codepen replicating the issue on the latest release (v1.1.3) - simply click other tabs to see it.

While the example doesn't include ui-router, it has the same symptoms that I'm seeing with ui-router.

2016-04-04-133200_1680x853_scrot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants