Ranter's CornerI hate browsers!

 

Press Ctrl+Enter to quickly submit your post
Quick Reply  
 
 
  
 From:  ANT_THOMAS  
 To:  af (CAER)     
38724.21 In reply to 38724.20 
Ahh, ok, my fault then. It had been there all along though, not sure what made me put it there though.
0/0
 Reply   Quote More 

 From:  ANT_THOMAS  
 To:  af (CAER)     
38724.22 In reply to 38724.20 
Fixed by moving the <script> tags, but I'll download the new version anyway.
0/0
 Reply   Quote More 

 From:  Ken (SHIELDSIT)  
 To:  ANT_THOMAS     
38724.23 In reply to 38724.21 
Is that top secret tin foil?
0/0
 Reply   Quote More 

 From:  Peter (BOUGHTONP)   
 To:  Ken (SHIELDSIT)     
38724.24 In reply to 38724.19 
You can test it when it goes live - I'll need to see how people who can't read react to it. :P
0/0
 Reply   Quote More 

 From:  Ken (SHIELDSIT)  
 To:  Peter (BOUGHTONP)      
38724.25 In reply to 38724.24 
haha whut?
0/0
 Reply   Quote More 

 From:  ANT_THOMAS  
 To:  Ken (SHIELDSIT)     
38724.26 In reply to 38724.23 
Nope!
0/0
 Reply   Quote More 

 From:  Peter (BOUGHTONP)   
 To:  af (CAER)     
38724.27 In reply to 38724.20 
quote:
Also, you should put script tags at the end of the document, just before the closing body tag, as they block page rendering until the files they reference have been loaded and parsed.


Alternatively, you should put script tags in the head of the document because they block page rendering until the files they reference have been loaded and parsed, and that means you don't get a page that has rendered but is buggy and unresponsive because only half the scripts have loaded. :@
0/0
 Reply   Quote More 

 From:  af (CAER)  
 To:  ANT_THOMAS     
38724.28 In reply to 38724.22 
I've also updated it so it will still work even if you put the script tags in the head and use the no_wait option; in such a case it'll just pretend you didn't use no_wait.
0/0
 Reply   Quote More 

 From:  Peter (BOUGHTONP)   
 To:  ANT_THOMAS     
38724.29 In reply to 38724.21 
It's not your fault!

The head is where script files have always been intended to go - the blocking of loading is deliberate. It's a relatively recent fad of "optimising" pages by putting them at the end.

As above, it means that the page can load and look like it's ready before any of the JavaScript is actually executed, which is especially a pain when people use files on a slow CDN, and you have to sit waiting before you can interact with a page.
0/0
 Reply   Quote More 

 From:  af (CAER)  
 To:  Peter (BOUGHTONP)      
38724.30 In reply to 38724.29 
It wouldn't be a problem if document.write() never existed :-/
0/0
 Reply   Quote More 

Reply to All    
 

1–20  21–30

Rate my interest:

Adjust text size : Smaller 10 Larger

Beehive Forum 1.5.2 |  FAQ |  Docs |  Support |  Donate! ©2002 - 2024 Project Beehive Forum

Forum Stats