Is that bootstrap's own thing that he/she/it uses to do something? Or is that an abnormal behavior? I see that in my Inspect Element feature of Google Chrome whereas I didn't wrote it in my markup. See this screenshot:
I believe that little tag is being added by the "Webpage Screenshot" extension.
On my computer, I went to chrome://extensions/ then disabled "Webpage Screenshot Capture" and the data-wssurvey attribute disappeared.
Also, there was a javascript error message appearing in the console for every page I loaded, and that went away after disabling the webpage screenshot capture extension.
Related
Images are loaded on my html pages. But Firebug shows that it failed to load given url when I hover on the element on firebug panel.
That's obviously a bug in Firebug 2.x. I only found the related issue #3540, so you might want to file a new issue for it.
Having said that, Firebug as extension is going away with one of the upcoming versions of Firefox. It is implemented as theme for the Firefox DevTools instead, which don't have this issue. So, I suggest to use those instead.
I've Googled this and nothing comes up. So this is some new DOM warning that I have discovered completely on my own. WTH is this?...
Seems to be related to a recent LastPass update, although that's as much as I know.
If you check in dev tools you'll see that the warning is related to 'onloadwff.js'. If you click on that file reference and hover the tab for that file in the sources panel you'll see that the tooltip shows it is part of a chrome extension. I can confirm that disabling the LastPass extension resolves the warning.
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.
The Chrome GA debugger does not appear to work. I can't find any info about how to fix it either.
There is an icon on the top screen. No window on the bottom, no readout. No feedback.
Compounding the problem is that searching for 'analytics debugger does not work' returns only results about setting up analytics or problems associated with GA or Chrome.
I'm starting this thread because none currently exists.
Anyone had this issue?
Are you sure you understand what it is supposed to be doing?
I just installed it. It adds a browser action button that changes state between off and on when clicked. It also reloads the current tab when clicked, but you have to reload other tabs if you need it to take effect there.
The information that GA module outputs goes to the page's JavaScript console. The extension does not automatically open it. You can open it with Ctrl+Shift+J
I found the answer.
You have to open the Chrome javascript console. I doesn't launch automatically.
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.