www.webdeveloper.com
Results 1 to 5 of 5

Thread: Unknown error ...

  1. #1
    Join Date
    Dec 2005
    Location
    FL
    Posts
    7,364

    Question Unknown error ...

    I'm getting an error message in the error console using the FF browser.
    Error: uncaught exception: [Exception... "Cannot modify properties of a WrappedNative" nsresult: "0x80570034 (NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN)" location: "JS frame :: chrome://global/content/bindings/autocomplete.xml :: onxblpopuphiding :: line 825" data: no]
    Where do I look to find out what this error means?
    It does not point me to a line number in the HTML that I'm using (it only has 609 lines).

    Obviously I can ignore the error by not looking at the error console
    and it does not seem to be effecting the operation of the code
    as all other actions seem to be working fine, but it's starting to bug me
    and I don't like unknown bugs or "exceptions".

    Has anyone received this type of error before and what did you do about it?

  2. #2
    Join Date
    Jan 2009
    Posts
    3,346
    I found a posting where you can reproduce the error in a couple lines of code (see answer 3 I think it was): http://stackoverflow.com/questions/1...t-seem-to-work

  3. #3
    Join Date
    Dec 2005
    Location
    FL
    Posts
    7,364

    Exclamation

    Quote Originally Posted by criterion9 View Post
    I found a posting where you can reproduce the error in a couple lines of code (see answer 3 I think it was): http://stackoverflow.com/questions/1...t-seem-to-work

    That's an interesting site, but I think I'll need some time to know if it applied to me.
    Did not know I was "aliasing". And I'm not sure what to change at this time, but I'll check it out.

    Thanks! (I think )

  4. #4
    Join Date
    Jan 2009
    Posts
    3,346
    I couple of other things that came up in my quick search seemed to have to do with either popups (either blocker add-ins or in browser blockers) or some sort of native library being called from within the browser. Seems there was also a bug a number of years ago for the engine used in FF that would throw that error if the DOM hadn't been built in a child window before running DOM methods (such as using innerHTML to populate a div and then using child collections on the div later). Don't know if that might give you a starting point to find where your error might be. Another thought is to check another install of FF (without any add-ons if possible) since the error might be something completely unrelated to your actual code.

  5. #5
    Join Date
    Dec 2005
    Location
    FL
    Posts
    7,364

    Talking

    Quote Originally Posted by criterion9 View Post
    I couple of other things that came up in my quick search seemed to have to do with either popups (either blocker add-ins or in browser blockers) or some sort of native library being called from within the browser. Seems there was also a bug a number of years ago for the engine used in FF that would throw that error if the DOM hadn't been built in a child window before running DOM methods (such as using innerHTML to populate a div and then using child collections on the div later). Don't know if that might give you a starting point to find where your error might be. Another thought is to check another install of FF (without any add-ons if possible) since the error might be something completely unrelated to your actual code.
    Thanks again. At least I can check out the items you noted above.
    I understand where to check if a popup, innerHTML population of a div, etc.
    are being used in my script.
    Your answer is more on my level of understanding than the original suggested post.

    Appreciate the additional information.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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



Recent Articles