Skip to content

Always open new tab, when updating in Plunker #11630

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

Closed
DineshChopra opened this issue Sep 15, 2016 · 6 comments
Closed

Always open new tab, when updating in Plunker #11630

DineshChopra opened this issue Sep 15, 2016 · 6 comments

Comments

@DineshChopra
Copy link

Hi,

When I am going to update anything in Plunker then new tab will opens and updates shown in new tab.

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Expected behavior

Reproduction of the problem

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

  • Angular version: 2.0.0-rc.X

  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

  • Language: [all | TypeScript X.X | ES6/7 | ES5]

  • Node (for AoT issues): node --version =

@pkozlowski-opensource
Copy link
Member

Huh? Sounds like sth plunker-related... or not clear what you are asking... Going to close this one as it doesn't sound like the angular-specific issue...

@DzmitryShylovich
Copy link
Contributor

You can "fix" it by disabling auto refresh http://prntscr.com/ciazer

@DineshChopra
Copy link
Author

Open angular docs QuickStart (https://angular.io/docs/ts/latest/quickstart.html)
Click on live example, When we are going to update anything here it always opens a new tab. I think there is some problem, but not sure what is the exact problem. So may be needs someone help to fix it.

@zoechi
Copy link
Contributor

zoechi commented Sep 15, 2016

I also have this and had it already occasionally a few months ago. No idea what causes it though.

@neeklamy
Copy link

I just came across the same problem with an Angular tutorial hosted on Plunker, this was caused by angular/zone.js#456.

I can confirm switching to a more recent Zone.js works:

The bug has since been fixed in more recent zone.js releases but the Angular team still needs to reflect those new versions in their docs and plunk seeds.

To fix this locally, just change the version of zone.js referenced in your plunk to 0.6.24 or 0.6.25.

Geoff Goodman on the Plunker Google Group

@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 10, 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

5 participants