Results 1 to 6 of 6

Thread: Google Chrome and Safari problems/crashes with NOF 11

  1. #1
    Junior Member Vloggity's Avatar
    Join Date
    Dec 2011
    Posts
    2

    Default Google Chrome and Safari problems/crashes with NOF 11

    Our website works perfectly fine in IE and FireFox. But, does not funtion and/or crashes in Google Chrome and Safari...any suggestions to remedy this would be greatly appreciated! Thanks.

    See for yourself at: www.vloggity.com

  2. #2
    Max
    Guest

    Default Re: Google Chrome and Safari problems/crashes with NOF 11

    Yes, I can see the problem. It's always difficult to spot such problems,
    but my guess would be some problem with the JavaScript - there is a lot
    of it, and FireFox Web Developer Toolbar is indicating that errors are
    being thrown.

    My suggestion would be to save everything as a separate NOF file (so you
    can go back to the current version), then experiment by deleting
    elements of the copy site until it works OK, which will point you
    towards the problem.

    Max

    ----
    Vloggity wrote:
    Our website works perfectly fine in IE and FireFox. But, does
    not funtion and/or crashes in Google Chrome and Safari...any suggestions
    to remedy this would be greatly appreciated! Thanks.

    See for yourself at: 'www.vloggity.com' (http://www.vloggity.com)




  3. #3
    Junior Member Vloggity's Avatar
    Join Date
    Dec 2011
    Posts
    2

    Default

    Thank you Max, I am willing to try anything at this point.

    Trying to gain an understanding, why would a large amount of javascript cause the website not to function in Chrome and Safari? Many other sites I visit contain much, much more javascript and function fine in Chrome and Safari.

  4. #4
    Senior Member
    Join Date
    Oct 2011
    Posts
    169

    Default

    as Max wrote, there are Javascript-errors. now, every Browser works a little different. IE and FF seem to override the problems, while Chrome and Safari insist in showing the errors. sometimes it the other way round.

    there are more problems on the index.html (only page I looked at). FF 8.01 doesn't show all the menu, while Chrome does. what did I say

  5. #5
    Max
    Guest

    Default Re: Google Chrome and Safari problems/crashes with NOF 11

    Chrome and Safari are both based on the WebKit code base so do tend to
    suffer common peculiarities, although I think they do now use different
    javascript engines.

    When writing any computer code, it's very easy to make errors.
    Javascript is also continuing to evolve, and it may be that the code
    incorporates something that has been superseded or is non-standard.
    Consequently my guess is that both browsers may be having difficulty
    interpreting one or more parts of the javascript code on your site and,
    perhaps, failing to do so in similar ways. Of course I could be wrong...

    While javascript does have its uses, there are various reasons to
    minimise its use: there can be conflicts between functions in different
    scripts; javascript doesn't work on many mobile browsers; some people
    disable it for security or other reasons; it's not read reliably by
    search engines; and each script uses increases both download time and
    processing time on the user's PC / smartphone (and you have 22
    javascripts on your home page).

    Max

    ----
    Vloggity wrote:
    Thank you Max, I am willing to try anything at this point.

    Trying to gain an understanding, why would a large amount of javascript
    cause the website not to function in Chrome and Safari? Many other sites
    I visit contain much, much more javascript and function fine in Chrome
    and Safari.




  6. #6
    Junior Member
    Join Date
    Jun 2011
    Posts
    23

    Default

    I loaded your home page in Firefox with FireBug plugin and kicked out three errors all pointing to FaceBook (errors copied below).

    Firefox is able to get past these errors, but Chrome may not. So, I would start with resolving these, or temporarily disabling the Facebook code to see if it will load.

    Alternately you could try to load the Facebook code last so the rest of the page has a chance to load before the error stops it.

    #1
    uncaught exception: Error: Permission denied for <http://www.facebook.com> to get property Proxy.InstallTrigger
    https://plus.google.com/_/apps-stati...iaIHKXKcg/d=1/
    Line 191

    #2
    uncaught exception: Error: Permission denied for <http://www.facebook.com> to get property Proxy.InstallTrigger
    http://widgets.twimg.com/j/2/widget.js
    Line 12

    #3
    uncaught exception: Error: Permission denied for <http://www.facebook.com> to get property Proxy.InstallTrigger

    Line 0

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •