Is anyone else aware of the fact that Internet Explorer (at least version 8) keeps downloading a file even if the close() method is called on an URLStream instance?
Heck, it even keeps downloading if you close the tab displaying the site which called the load()/close() methods on an URLStream instance.
Does anyone know of a solution to overcome this problem?
More details:
My preloader is loading a dozen of files and immediately closing the download streams with the purpose of checking each resource's file size. In Mozilla Firefox all goes well, exactly as expected, but Internet Explorer keeps downloading the resource even if the stream has been interrupted by the action script close() method.
It seems that IE doesn't always do that, so there can't be a solution to this question.
Related
If I visit a site, I want to close the Chrome Web Browser. Is it possible to write such a program?
Under normal operation, this should not be possible. However, there have been cases where browsers have had well known bugs that could be exploited. To be clear though, I'm referring to crashing the browser. There is no supported API or method of asking the browser to close.
For instance, a simple line of CSS could crash Internet Explorer 6. Something like this on Chrome would probably not work anyways, since Chrome runs each tab in its own process.
There is a way to close a browser window (tab) via script if your script opened the window, simply by calling window.close() (where window is the child window). Please see https://developer.mozilla.org/en-US/docs/Web/API/Window/close for more information.
I am building a simple webpage (http://www.riffomonas.org/reproducible_research/) using Jekyll that is taking a long time to load on Safari. On Firefox and Chrome it loads instantly. In Safari, when I go in to the Web Inspector, it has two errors. The first...
Failed to load resource: The request timed out
The resource it was trying to get is http://api.pubpeer.com/v2/pubposts?filter=doi&devkey=PubMedSafari.
The second...
TimeoutError (DOM Exception 23): The operation timed out.
It's indicating that it was trying to access PP.js
The weird thing to me is that neither the API link or the Javascript are referenced in the code or the rendered HTML.
Any suggestions?
It turns out that the problem was the PubPeer Safari extension, which they are no longer supporting. Once I removed the extension everything worked great.
Years ago, I created a swf that upon init, loads an external swf. It worked reliably for years. Now, it's been brought back, but no longer loads the swf in more modern browsers, like in its heyday. It now fails in Chrome 57 and IE11, but worked around IE8 and Chrome 20ish. I'm thinking this might be a security issue. I tried setting compatibility mode in IE but that didn't help. Am I missing a security setting somewhere?
Crossdomain only matters between servers. If its not accessing the internet from hard drive then it cannot be any security issue...
Since it will run offline why involve browsers?
Just use the standalone Flash Player (see this other Answer for any useful hints).
If you have original source codes then just compile output as .exe instead of an .swf.
The same application that I am developing works fine on Firefox but not on Chrome.
My application a day ago printed some things on the console, but I removed them today, which means that the actualized version of the application does not print anything on the console.
On Firefox it works, everything renders and there is not prints on the console.
However on Chrome, the app still prints on the console. It means that it is retaining some old state for some reason.
Does that even make sense? The code is already gone (erased), so the only way Chrome is printing the old state on the console is if he is storing it.
On Chrome I also get errors of undefined functions, but they are defined. On Firefox that does not happen.
Have you tried reloading the page? Another thing to try to really get rid of the state that the browser is obviously holding onto is to clear the browser cache.
I have a problem with HTML5 appCache on Firefox and IE10.
I have build a minimal test case available on: https://docs.google.com/file/d/0B7CVmRJOMgTNZUxkLWRDNmhtVU0/edit?usp=sharing
Accessing the page at "applicationCache/test.html" the browser will look for the correct manifest and will start to download all the content from the files in its list.
The problem occurs when I put in the list a .php file handling COOKIES; for example I have added a .php file which will call the php function "session_start()".
Chrome and Safari can handle correctly such file during the application cache download.
Firefox and IE10 share the behaviour: they halt and signal a generic error.
During a long search I found out this ticket on bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=722683
Is there anyone who can give me a hint to handle correctly the COOKIES during applicationCache download event, without getting an error ?
Am I doing something wrong or against the standard ?
Thank you for your assistance!
I am not sure but can you make use of the localStorage instead of cookies?