I've just updated Chrome from 17 to 18.0.1025.142 and got all the ExtJS charts crashed in the web-site. The same issue reproduces on the Sencha example. Try clicking "Reload data". Any ideas?
I've come across the same problem. It looks like it's a bug in that version of chrome as the dev stream (v19) fixes the problem. It's a total PITA, but hopefully v18 won't be the current version for long. We just disabled the charts for that browser until it's sorted.
Here is an issue opened with chromium. Log in and star the issue so that it goes up in priority for chrome developers.
Also look at this thread for a workaround. Didn't work in my scenario but it might help you.
http://www.sencha.com/forum/showthread.php?192175-4.0.7-Line-Charts-Broken-in-Chrome-18-Mac-(and-also-it-appears-windows)
Related
We are seeing a really weird issue with our production site where after 30 seconds it appears that the session is invalidated in the Chrome and Edge browsers. We don't see any errors in the chrome inspect console.
We saw this behavior on 25MAY2022 right around when chrome 102 got pushed to the browsers at 5pm. IF we use inspect and turn off the cache then we don't see any issues with loading the site and everything operates fine.
FireFox works fine.
I'm using chrome 101.0.4951.61 against the same site on my android 11 phone and I cannot reproduce the issue.
Are there any new features in 102 we could turn off to see if a specific new security check might be at play?
My team is experiencing a similar issue when calling our API. If you go to chrome://flags/#private-network-access-send-preflights, and disable it, does that resolve your issue? If it does, then adding this header to your site may resolve the issue:
Access-Control-Request-Private-Network: true
We are currently doing pre-prod testing which is so far promising.
https://developer.chrome.com/blog/private-network-access-preflight/
Chrome ERROR_TIMED_OUT in latest version
today my chrome is gone to v50 and I noticed a dramatic slowing when trying to open request/response headers detail in the devtools.
Am I the only one?
I am having the exact same problem after I upgrade to build 50.0.2661.xxx, and I don't use any theme. For now I just have to downgrade it to build 49.0.2623.xxx.
Google Chrome v51 fix this issue
Edit. It seems not
The bug report is available here on the chromium tracker.
According to the comment, the issue is fixed for v52.
I have been having the same issue over the last week. Finally figured out it was a dark theme extension I was using for my dev tools. (DevTools Theme: Zero Dark Matrix) Removing it fixed the issue.
I also noticed the same behaviour in v50. Updating to V51 fixes the issue.
Recently updated my Google Chrome to version 32.0.1700.76 m and it looks like tooltips have stopped appearing over html elements with the 'title' attribute set.
<span alt="Testing" title="Testing">hhh</span>
Here is an example jsFiddle:
http://jsfiddle.net/ricksuggs/cDhEL/
I thought it was an HTML standard, it is still working in Firefox, anyone else experiencing the issue?
Version 32.0.1700.76 m works fine for me. Have you tried just clearing your Chrome browser cache to make sure it's not a caching issue?
Unfortunately, this is an old bug that have pop with version 32.0.1700 and is still present in v55 on some system such as mine too.
If you encounter this bug. Please go to http://download1.srware.net/old/iron/win/portable to test version 31 then 32. If you find out it works with v31 but it doesn't with v32, please report it in the chromium bug tracker issue. Specify your setup sharing a link provided by DriversCloud.com to help dev to fix it. They need feedback and details.
I'm working on a project using KineticJS version 4.6 (currently the latest version), and since last night's Chrome update to Chrome 29, the Kinetic canvas is completely blank. While using the console, I am still able to detemine that the created objects, such as the Kinetic.Stage and Kinetic.Layer, still exist and are filled with correct data.
Afterwards, I tried loading the same page in Internet Explorer and Firefox, and they still work as intended, showing the canvas with the correct elements.
I have tried searching for people with similar issues, but I guess Chrome's update is too recent to show any results. Does anyone perhaps know if there is a way to fix it or if I should simply wait for either a KineticJS or a Chrome update?
EDIT: And now it suddenly works again after restarting Chrome. Hotfixed?
EDIT2: After a while it broke again, but restarting the browser seems to work
EDIT3: It is a bug in Chrome, acknowledged by the Chromium team in this thread. The thread states that the bug is definitely fixed in version 30, which is currently in beta. This fix may be merged in version 29 soon, but there is no definitive timetable for this.
We have the same problem in Chrome 29.
In some cases a workaround is to tell your users to use Chrome Incognito mode to fix this issue.
A test to replicate the issue consistently is posted here:
https://github.com/ericdrowell/KineticJS/issues/585
At present, the bug is not present in Chrome 30. (8/27/2013)
You should star this chromium issue:
https://code.google.com/p/chromium/issues/detail?id=280153
I'm using Chrome-compatible SRWare Iron 5.0.381 on XP, and was checking out what Chrome has to offer to developers, EG inspecting the contents of the DOM of a currently-loaded web page.
But when I hit CtrlShiftI, the bar is totally empty:
Does someone why this is? Do I need an add-on? Are there other Chrome-compatible tools I should know about?
It appears you’ve found a bug in that fork of Chromium. The inspector works just fine with Google.fr in the latest Google Chrome and Chromium builds. Why don’t you use one of these browsers.
Usually the reason of that is some problem in DevTools JS code.
It is a chance that problem will be solved by chrome restart.
Such kind of problems can happen when chrome is upgrading at background.
The other reason of that can be some changes which you made in DevTools.js.
Of cause if you have done some changes :)
You can troubleshoot such problem by another instance of DevTools.
As example you can try to load DevTools.html page into Safari, open WebInspector for it and check console messages.