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

Progress-bar example on material.angular.io is broken #8497

Closed
jelbourn opened this issue Nov 16, 2017 · 9 comments
Closed

Progress-bar example on material.angular.io is broken #8497

jelbourn opened this issue Nov 16, 2017 · 9 comments
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Comments

@jelbourn
Copy link
Member

https://material.angular.io/components/progress-bar/overview

@amcdnl could you take a look?

@jelbourn jelbourn added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Nov 16, 2017
@ghost
Copy link

ghost commented Nov 17, 2017

@jelbourn Which example exactly do you mean, because I can't spot any broken one!?

@bardiel
Copy link

bardiel commented Nov 17, 2017

Also, could it be a cache problem in the browser?
When I access the link I see:
2017-11-17-102219_811x256_scrot

But CTRL-SHIFT-R and everything works...

@bardiel
Copy link

bardiel commented Nov 17, 2017

If so, @jelbourn, I believe it may actually be what you said here: #8175 (comment)

@jelbourn
Copy link
Member Author

So it is- it threw me off that the rest of the demos worked; usually they'd all been broken.

@bardiel
Copy link

bardiel commented Nov 17, 2017

Weird magic these service workers. =P

@merobal
Copy link

merobal commented Nov 17, 2017

Well, for me the demo here is still not working (even after CTRL+SHIFT R), the code tabs are empty, and the plunker example shows strange files.
image
image

@jelbourn
Copy link
Member Author

jelbourn commented Nov 17, 2017

Visit chrome://serviceworker-internals/ and unregister the worker for material.angular.io

@merobal
Copy link

merobal commented Nov 17, 2017

Thanks, now it works well.

@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
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Development

No branches or pull requests

4 participants