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.
Related
Quick one from me - is Firefox's spellcheck functionality (I am running ver 37.0.1) disabled when editing websites and apps locally. Words spelled incorrectly are underlined in Chrome and Safari but not Firefox.
I have added spellcheck="true" to a field but still no luck.
Everything seems to be working correctly on the pages that are already online.
Has anyone experienced a similar issue?
Thank you!
Fixed - Firefox needs a dictionary to be downloaded to spellcheck things.https://addons.mozilla.org/en-US/firefox/language-tools/
After update to chrome 35, autocomplete in dev tools doesn't work. Is it only my issue?
Checked windows and mac, all works..
I've got some similar problems, but just on Styles panel on Elements tab. Here, I've opened an issue just to this case:
https://code.google.com/p/chromium/issues/detail?id=376763&thanks=376763&ts=1400852713
I know it's not a solution, but it's the best we can do. We have to wait for someone at google (or that's involved with chromium project) fix it, and then release a new version patching it.
An alternative is using Chromium from ubuntu Software Center for now (it's still at version 34, so the autocomplete works): https://apps.ubuntu.com/cat/applications/chromium-browser/
UPDATE
This bug has been fixed on version 36
The issue has been fixed in the beta version.
(works in the current version: 36.0.1985.49 beta)
Can be download from http://www.google.com/intl/en/chrome/browser/beta.html
edit:
Considering the initial message, I assumed the problem was to pop the autocomplete box in the source files search as i enter in this issue. If the problem ain't relative to this, sorry.
In the last version the auto-completion menu in dev tools doesn't appears automatically anymore, u need to press cmd+P or cmd+O (mac) to open it.
I've got the same problem. It's really annoying.
Besides, on the Elements tab, when you double click the attribute of an arbitrary tag, the attribute is automatically emptied, which, i think, is not really expected.
Hope these issues get solved as quickly as possible.
I got a really strange problem, and after so much tries and research I can't get out of it.
I have a website, but SOME (just 5% of visitors) people with the SAME version of chrome, see the text flowing out of divs and text overlapping. It's very strange because I tested the website on all chrome browsers using browser testers, without any problem. And in internet explorer or firefox this problem never happens...
A page is located here
And here are some screenshots of what SOME people see (maybe you won't see this in chrome)
click here
Maybe it is because of the font face I am using? Or maybe some bad coded CSS?
Please help me out of this!
Thanks a lot!
I see you use .svg font. Recently I was hunting some Chrome font rendering bugs and saw this:
http://code.google.com/p/chromium/issues/detail?id=95102
This seem very similar to issues you are having. You could try to serve some other font type to Chrome and if this would fix that.
If you don't want or can't serve some other font type to Chrome, the only thing you can do is wait until Chrome version 24 is out to all users which should be soon (I can't find any announcement)
I tested it in
Chrome 23.0.1271.97 m
Chrome 26.0.1371.0 canary
Chromium 25.0.1334.0 (169326)
# Windows 7 x64 and your page seems fine for me.
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)
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.