Not signed in (Sign In)

Vanilla 1.0.3 is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthormaxcase
    • CommentTimeMay 14th 2007
     
    Hi

    was getting Security error code: 1000 being thrown by FF (2.0.0.3/mac) in my firebug console. In the FF error console,
    i would get this (which helped a bit more)
    Error: uncaught exception: [Exception... "Security error" code: "1000" nsresult: "0x805303e8 (NS_ERROR_DOM_SECURITY_ERR)" location: "path_to_script/_javascript/swfobject_source.js Line: 190"]

    Same page was working fine in safari.

    Jumping to line 190 i really couldn't tell what was causing the security error. I can tell what the function is for [thats straight-forward enough from the code-comment), but not what could be the source of the error. Anyhow, just having that function return ""; got it working again.

    I know I've probably broken some sort of functionality, but it seems to be working for our needs.

    Just posting in the hopes that
    a) this helps someone else stuck like me, and
    b) that this can be fixed, or worked around properly, without losing any functionality.

    Thanks,
    M.
    • CommentAuthorAran
    • CommentTimeMay 14th 2007
     
    There was another post a short time ago which concluded that the Firebug extension actually causes some errors which don't appear without it installed. Try temporarily uninstalling the extension, and see if you still get any js errors.
    • CommentAuthormaxcase
    • CommentTimeMay 15th 2007
     
    Hi Aran,

    Thanks.
    Tried the same page on colleagues machine, firefox2.0.3, as well as on another machine with FF1.5, no firebug.
    Both throw the same error.

    m.
    • CommentAuthorAran
    • CommentTimeMay 15th 2007
     
    Can you post the page?
    • CommentAuthormaxcase
    • CommentTimeMay 17th 2007
     
    Hi Aran,

    I can't post the page just yet, but I will look to reproduce it on an exmple page later and post a link to that.
    • CommentAuthormaxcase
    • CommentTimeMay 24th 2007
     
    Hi Aran,
    I haven't been able to reproduce it on an example page (weird,i know).

    A bit more info though:
    looking at the DOM for the affected page, it seems document is no where to be found.
    so changing

    var q = document.location.search || document.location.hash;

    to

    var q = window.location.search || window.location.hash;

    in getRequestParameter seems to fix it.
  1.  
    I can duplicate it, but it may be a different scenario. I had the -exact- same error in Firefox 2.0.0.6 today. I was doing data validation in a submission form, and one of the things I do is strip leading and trailing whitespace from form fields.

    Turns out that if you modify an <input type="file"> element's contents, it throws this error as a security error. This is sensible, since if you were allowed to arbitrarily alter the contents of said widget, you could basically request any file from the user's hard drive that you wanted.

    That's one thing that generates this error.
    • CommentAuthorzhangsisi
    • CommentTimeOct 1st 2007
     
    find love best www.ConnectAsia.info/en/lang104082about_sisi11 welcome you