I was following the "Get started with ASP.NET Core Blazor" example but I get the following error when using the Chrome Browser:
An unhandled error has occurred.
When using the Edge everything was ok.
Why this is happening?
Problem resolved possibly by Chrome actualization.
Now I am using the 79.0.3945.88 version, everything seems ok.
Related
I'm not sure what changed in Chrome but the Graphiql GUI tool is not loading.
In Firefox and Safari it works just fine. I have disabled all Chrome extensions, restarted Chrome, and restarted my Mac. The error persists. How do I debug this?
In graphql-workspace.min.js it errors on:
this.state.config.state.proxy || this.state.config.state.headers.forEach(function(e) {
Error:
graphiql-workspace.min.js:1 Uncaught TypeError: Cannot read property 'forEach' of undefined
at t.value (graphiql-workspace.min.js:1)
at t.value (graphiql-workspace.min.js:1)
at t.value (graphiql-workspace.min.js:1)
at t.value (graphiql-workspace.min.js:1)
at performInitialMount (react-dom.min.js:13)
at p.mountComponent (react-dom.min.js:13)
at Object.mountComponent (react-dom.min.js:14)
at mountChildren (react-dom.min.js:14)
at m._createInitialChildren (react-dom.min.js:13)
at mountComponent (react-dom.min.js:13)
Here is a picture of it working in Firefox:
Not sure why headers is undefined.
I am using:
Elixir, Phoenix, Absinthe, Absinth-Plug, Vue, Vue-Apollo, apollo-boost, graphql,
Since the GUI appears to be loading from a CDN I'm wondering if that's a direction I should explore. However the network tab in chrome shows no failures.
It seems that much of the activity/history of using Graphiql is saved to localStorage. I'm not sure what broke the history but I inspected the broken config in the console with a few breakpoints. This lead me to discover that localStorage was being used. I then cleared a lot of key/values in there and my Graphiql rendered successfully.
Some characters are not showing when opening digitalocean.com happening both Chrome and Firefox.
Check the Screenshots below..
I am using ubuntu 14.04
Start with checking the console errors:
https://www.googleadservices.com/pagead/conversion_async.js Failed to load resource: net::ERR_BLOCKED_BY_CLIENT
/assets/fonts/appicons-c630ae11.woff2?lujp4j:1 GET https://www.digitalocean.com/assets/fonts/appicons-c630ae11.woff2?lujp4j
It works fine in Chrome / Firefox here..
I have not changed anything on my website and all of a sudden the front page slider is not working.
http://solutionsfortravel.com/
Can someone please give an recs as to why?
Thanks
You have a lot of errors in the console - you can use Google Chrome's developer tools to look for missing files and Javascript errors.
https://developer.chrome.com/devtools
You can also get similar tools in Firefox, Opera and Internet Explorer (other browsers are available)
A quick look at the console shows this error, which is to do with some kind of slider library judging by it's name.
jquery.nivo.slider.pack.js?ver=3.3.5:12 Uncaught TypeError: d is not a function
You should really try and fix all the errors you're getting though
In Google Chrome developers, console part shows the error:
Uncaught TypeError: $(...).datepicker is not a function
Try to resolve this problem with datepicker
I have made a webpage using Polymer. The webpage doesn't open on Google Chrome (both Windows and Android). When I try to open the page, Chrome shows "He's Dead, Jim!" message on Windows and "Aw, Snap!" message on Android. I have reset the settings and reinstalled Chrome but the problem still continues. Can anyone tell me how to solve this problem or the reason behind it?
https://www.googledrive.com/host/0B2Zii8voDW6QcGduNnl1cFBReXc/fold/
maybe you can check if there is any error in your page, which stop polymer initialization:
https://www.polymer-project.org/docs/polymer/debugging.html#unregistered-element-bookmarklet
Btw, did you try the official demo page with your browsers? If they work, then it's your code problem.
Chrome console tells you what line in the parsed file JavaScript syntax errors are located. Every once in a while, when I click on the link to take me to see the actual code of where the error is, I get a blank screen in the console. If I open up the same page inside Firefox with Firebug, I can see the error code without any issues.
Is this a known error in Chrome? If so, are there any ways to remedy it?
Here is an official list of known issues with Google Chrome. It doesn't seem like that is one of the known issues. I would try again and see if it happens again.