when you aree using parameters with settimeout, it works a whole lot better when you feed the parameters using tyhe parameters provision. https://developer.mozilla.org/en-US/docs/Web/API/Window.setTimeout var tid=window.setTimeout(PlaceImageBackground,1000,'header','./images/header.jpg'); add the mdn (mozilla developer's network) search to your list of search engines, or get the javscript bible 7th ed. by danny goodman.
>________________________________ > From: Sebastian Zartner <[email protected]> >To: [email protected] >Sent: Friday, January 24, 2014 3:59 AM >Subject: Re: [firebug] Re: What does aborted mean in Firebug? > > > >Firebug does not display the images called by setTimeout, interestingly (?) >Firebug or Firefox? > >Any chance you can provide a URL, so I can try that out myself? > >Sebastian > >On Wednesday, January 22, 2014 2:20:54 PM UTC+1, Szoghy, Bertrand wrote: >Hello, >> >>I’ve worked around our embedded web server issue by staggering the image >>requests from the web page via JavaScript setTimeout calls with intervals >>separated by 100 ms. We get no more “aborted” files. The web server has a >>performance limitation, it is simply unable to handle a burst of HTTP >>requests all at the same time. >> >>Firebug does not display the images called by setTimeout, interestingly (?) >> >>At the bottom of the web page I call the function: >> >>setTimeout(" PlaceImageBackground('header', './images/header.jpg')",1000); >> >>And the function is: >> >>function PlaceImageBackground(DivName, ImageUrl) >>{ >> document.getElementById( DivName).style.backgroundImage = >>'url(' + ImageUrl + ')'; >>} >> >>I am using Windows 7 64 bit, Firefox 26.0 and Firebug 1.13.0a7. >> >>Cheers! >> >>Bertrand >> >>De :[email protected] [mailto:fir...@googlegroups. com] De la part de >>Sebastian Zartner >>Envoyé : lundi 20 janvier 2014 05:29 >>À : [email protected] >>Objet : [firebug] Re: What does aborted mean in Firebug? >> >>I couldn't find a clear definition of what it means in Firefox, though the >>general answer to this is that the client stopped the request. As a document >>related to HttpWatch describes for IE this can have several reasons (copied >>from there): >> 1. If you click on a link or bookmark while a page is downloading, or >> click on IE’s Stop button, you will see that IE cancels any requests which >> are still active and HttpWatch shows the (Aborted) result. >> 2. A CSS rollover image on a page will start a request when the mouse >> pointer is moved into its active area. If the mouse pointer quickly moves >> away again, IE may abort the request if it has not already completed. >> 3. Sometimes javascript is used to fire off requests for background >> tasks or to gather statistics on a page. Often this can lead to aborted >> results if the javascript does not wait for the response to be received from >> the server. >>As these points say they apply to Internet Explorer. Though I assume the same >>counts for Firefox. >>Our network guru Honza might have a better explanation for this. >> >>Sebastian >> >> >>On Wednesday, January 15, 2014 7:29:04 PM UTC+1, [email protected] >>wrote: >>Hello, >> >>We are debugging an embedded web server, and some standard page elements for >>our web pages like the stylesheet or images are not showing up. Using >>Firebug, we can see they are "Aborted" in about 100 ms. That seems "too >>impatient" to be a timeout. >> >>So, is it aborted by the server? If so, it would be nice to know what error >>code "aborted" corresponds to? I have downloaded the Firebug code, can anyone >>point me to where I should add an "alert" ? >> >>Or is it aborted by the browser? Is there a setting in Firefox' about:config >>that would shed light on this? >> >>Thank in advance, >>Bert >> >> >>-- >>You received this message because you are subscribed to the Google Groups >>"Firebug" group. >>To unsubscribe from this group and stop receiving emails from it, send an >>email to firebug+u...@ googlegroups.com. >>To post to this group, send email to [email protected]. >>Visit this group at http://groups.google.com/ group/firebug. >>To view this discussion on the web visit https://groups.google.com/d/ >>msgid/firebug/aa62b823-3f34- 4a9c-8d6f-b1b436f87c4e% 40googlegroups.com. >>For more options, visit https://groups.google.com/ groups/opt_out. >>Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment. -- >You received this message because you are subscribed to the Google Groups >"Firebug" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to [email protected]. >To post to this group, send email to [email protected]. >Visit this group at http://groups.google.com/group/firebug. >To view this discussion on the web visit >https://groups.google.com/d/msgid/firebug/60bd39af-cb80-4da8-98da-11cc569527d4%40googlegroups.com. > >For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/1390626380.92290.YahooMailNeo%40web161503.mail.bf1.yahoo.com. For more options, visit https://groups.google.com/groups/opt_out.
