Repository navigation
angular.io website fail to search in firefox #26018
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[x] Other... Please describe: website
Current behavior
Fail to search the website with Mozilla Firefox and get protocol error most of the time.
Expected behavior
Search should work and website should not get error.
Minimal reproduction of the problem with instructions
- Open
firefox - Browse
angular.io - ctrl+shift+r to force reload (angular.io gets protocol error)
- Type in the search bar
- loading...
What is the motivation / use case for changing the behavior?
- no protocol error
- search successfully
Environment
Angular version: ?
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [x] Firefox version 62.0
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: v10.10.0
- Platform: Linux
Others:
Activity
gkalpak commentedon Sep 19, 2018
I am not getting any errors 😕
Have you tried clearing the cache? Does next.angular.io work?
pickfire commentedon Sep 20, 2018
It works after I removed everything from storage. @gkalpak Thanks a lot! It might be confusing that people needs to manually delete items from storage though.
gkalpak commentedon Sep 20, 2018
@pickfire, glad you got it working. Manually clearing the cache is not part of the intended workflow, of course. But sometimes things go wrong 😅
Hopefully, once we upgrade to the new SW (see #25997), things will go wrong less often 😁
angular-automatic-lock-bot commentedon Sep 14, 2019
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.