For some reason, my pages continue to load forever even though it appears it is done. How do I look to see what resource is being "waited upon"?
This page is one with the problem.
http://www.cadwolf.com/Documents/Documentation/Users_Guide_-_Tables
The page loads fine for me as well, but if you want to see what is being loaded or if there are errors you can check your developers tool. (Press f12 in google chrome). From there you can click on the network tab or the console tab.
Editing here cause I can't comment yet: In the network tab you can see everything that's being loaded for your page. So in the status column, it should say 200 OK to show your resources are loading properly. Here, you can see if something is being held up and what it is.
Related
I recently blocked quite a lot of ads across my entire network using AdGuard. Unfortunately, AdGuard does not prevent pop-up windows from opening. Although the advertising page is not called up, I get a popup which tells me that the requested page cannot be reached.
That's why I wanted to write a chrome extension that closes these popups automatically. Unfortunately, I fail to save the value of a checkbox in chrome.storage that is supposed to activate / deactivate the extension.
could someone help me here?
:EDIT
Okay i managed to store my value but now i'm running into the problem that i need to run a script when a page can't be loaded and i got no idea how i can do that. :S
Any Ideas? Is that even possible?
Upon switching to Chrome's Manifest 3 format (and per its requirements, using a service worker if that's somehow relevant), my options page shows up like this:
Only upon moving away from the tab and reentering it, do I get my options to show up:
It doesn't matter if I trigger the options page via the toolbar or via its extensions entry.
I do have the options page in the manifest file, so I wouldn't think the change to a service worker has relevance. I don't have any listeners for the page visibility API.
Even when I blank out my options code with a minimum of content and update the unpacked extension, I still experience this behavior.
Any configuration or behaviors that could be triggering this (and how to overcome)?
It seems that whatever the cause of this behavior, that it only occurs when loading an unpacked extension. When I use web-ext to build a zip file and open that in Chrome, I don't see this problem.
Not ideal, but a bug I can at least live with.
I have a Chrome Extension (page action). The extension is loaded in developer mode (not from the store).
The extension is used in two sites, both of which URLs are in the manifest.
When I go to one of the sites, the page icon is enabled and when I click it, it runs fine.
When I go to the other site, the extension icon is also enabled but when I click on the extension, instead of running the action, the extension menu appears (as if I had right-clicked the icon instead of clicked it).
When I hover the page action icon, in both sites I get the text "Has access to this site".
Which are possible causes for this behavior?
Something definitely changed with the manifest.json handling of the most recent Chrome update. (In my case, "Version 72.0.3626.96 (Official Build) (64-bit)" on Windows.) My extension stopped working in a way similar to what you describe.
The solution to my problem was to remove the specific url permissions I had specified in the "permissions" section, and replace them with <all_urls>. I tried tightening them back up again, but the only other thing that worked for me was https://*/*.
I tested this on several machines that had the previous version of Chrome and they had the same behavior... successful operation before the Chrome update, no response after. The icon displayed properly and showed "Has access to this site", but my background page refused to run.
Good luck! Hopefully this helps!
I am trying to manually add glimpse to an existing WebForms site.
I added Glimpse.Core.dll to the bin directory and edited my web.config as described here.
When I go to http://localhost/Glimpse.axd, I see the Glimpse config page and everything seems OK. When I click "Turn Glimpse On", a banner is added to the top of the page telling me that "Glimpse is now ON". Everything looks great so far.
When I go back to my site, the page loads, the glimpse icon pops up in the lower right corner, and then the page refreshes. Then the process starts over again. If I go back and turn off glimpse, the refresh loop stops.
I've looked at the refresh loop using fiddler, but nothing looks out of place. I've tried to use Firebug or the Chrome developer tools to see what's going on, but the page refreshes to fast for me to see anything.
I'm using glimpse 0.86 and .NET 4.0 on IIS 7 .5 (Windows 7).
Any clues?
Try making sure that you have properly closed any script tags or other markup on your page.
The only time I've seen reports of this behavior was when a page's markup was malformed, and the inclusion of a new/unexpected script caused the page's own javascript to execute.
The Glimpse client, to the best of my knowledge, does not actually have redirect code in it.
I have developed a chrome extension. The extension itself works fine and fast.
But when I start the browser and click on the toolbar icon of my extension it takes about 2 seconds for the popup to appear and to show its content (this happens anytime the browser is restarted).
Any idea what causes this and how to fix that?
Tip 1:
Use your popup page for rendering exclusively. It should be as light as possible. All the heavy loading/processing (localStorage, XMLHttpRequests, blocking javascript) must be done in the background page.
The background page is loaded when Google Chrome starts. Basically, it allows you to execute code and keep a page always running (although the popup is not present). For instance, streaming audio in a html5 tag with no popup.
Note: If you are not using a background page yet, you should be taking a look to message passing first.
Tip 2: Warning: This could fail
I haven't tested this yet, but maybe using the HTML5 manifest.cache can help you preventing loading again resources stored locally. But beware, this is HTML5 and is prone to changes and unstability across versions. (also, I am not completely sure that the cached resources will be loaded in memory before the popup is opened)
Hope it helps!