Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #22101 > unrolled thread

Why is Chrome on Mac so NOT reliable as other browsers?

Started byfabriziovsm@gmail.com
First post2013-11-21 10:40 -0800
Last post2013-11-21 23:22 +0100
Articles 3 — 3 participants

Back to article view | Back to comp.lang.javascript


Contents

  Why is Chrome on Mac so NOT reliable as other browsers? fabriziovsm@gmail.com - 2013-11-21 10:40 -0800
    Re: Why is Chrome on Mac so NOT reliable as other browsers? "Evertjan." <exjxw.hannivoort@interxnl.net> - 2013-11-21 19:52 +0000
    Re: Why is Chrome on Mac so NOT reliable as other browsers? Christoph Michael Becker <cmbecker69@arcor.de> - 2013-11-21 23:22 +0100

#22101 — Why is Chrome on Mac so NOT reliable as other browsers?

Fromfabriziovsm@gmail.com
Date2013-11-21 10:40 -0800
SubjectWhy is Chrome on Mac so NOT reliable as other browsers?
Message-ID<a5e1299e-d758-469f-a32b-d26731bde043@googlegroups.com>
Hello here,
I am having an hard time on Chrome for Mac to understand why it is giving me back random Javascript errors if I try to load the following page:

http://www.virtualsheetmusic.com/score/Moonlight.html


All other browsers on any platform works (including Chrome on Windows), but Chrome on Mac gives me random errors! Any ideas?

Just to give you more info about that page, I think what may cause the problem is the deferred load of Javascript you can see at around the top of the page where the first line starts with "// Add a script element as a child of the body".

I have just implemented what Google suggests to do to increase webpage load speed here below:

https://developers.google.com/speed/docs/insights/BlockingJS


Any ideas and thoughts are very welcome!

Thank you in advance.

Best,
Fab.

[toc] | [next] | [standalone]


#22103

From"Evertjan." <exjxw.hannivoort@interxnl.net>
Date2013-11-21 19:52 +0000
Message-ID<XnsA27FD4641F9Deejj99@194.109.133.246>
In reply to#22101
Fab. wrote on 21 nov 2013 in comp.lang.javascript:

> subject: Why is Chrome on Mac so NOT reliable as other browsers?

> I am having an hard time on Chrome for Mac to understand why it is
> giving me back random Javascript errors if I try to load the following
> page: xxxxx ...

Why would NOT giving errors being a sign of reliability?

How do you determine they are random?

If the errors were realy random. they would not stem from the programme or 
from the javascript engine, far more probably from a lose connection on the 
motherboard?

-- 
Evertjan.

[toc] | [prev] | [next] | [standalone]


#22108

FromChristoph Michael Becker <cmbecker69@arcor.de>
Date2013-11-21 23:22 +0100
Message-ID<528e8784$0$6628$9b4e6d93@newsspool2.arcor-online.net>
In reply to#22101
fabriziovsm@gmail.com wrote:

> Hello here, I am having an hard time on Chrome for Mac to understand
> why it is giving me back random Javascript errors if I try to load
> the following page:
> 
> http://www.virtualsheetmusic.com/score/Moonlight.html
> 
> 
> All other browsers on any platform works (including Chrome on
> Windows), but Chrome on Mac gives me random errors! Any ideas?

I get several "Uncaught ReferenceError: jQuery is not defined" errors on
first visit resp. when I disable caching in Chrome 31.0.1650.57 m on
Windows.

> Just to give you more info about that page, I think what may cause
> the problem is the deferred load of Javascript you can see at around
> the top of the page where the first line starts with "// Add a script
> element as a child of the body".
> 
> I have just implemented what Google suggests to do to increase
> webpage load speed here below:
> 
> https://developers.google.com/speed/docs/insights/BlockingJS
> 
> 
> Any ideas and thoughts are very welcome!

Um, just a guess (and I may be terribly wrong): some of the required
initialization of the jQuery scripts may be done on "DOM ready", which
may not be triggered when you add the script elements in the onload
event -- or maybe the "DOM ready" is triggered multiple times then.

Anyway, to speed up the site you may want to have a look at YSlow[1].

[1] <http://yslow.org/>.

-- 
Christoph M. Becker

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.javascript


csiph-web