I also get these errors when I try to create some DOM objects like
----------------------
var deleteButton = $('<tr><td></td><td><button class="delete"
type="submit"><span><em>'+ settings.remove_text +'</em></
span><button></td></tr>');
----------------------
the message is
[Exception... "Component returned failure code: 0x80004003
(NS_ERROR_INVALID_POINTER) [nsIDOMNSHTMLElement.innerHTML]" nsresult:
"0x80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame ::
http://concatenated_js_file_here :: anonymous :: line 12" data: no]
On Jun 22, 2:05 am, "Sebastián V. Würtz" <[EMAIL PROTECTED]>
wrote:
> im getting some errors since i change to ff3
>
> [Exception... "Component returned failure code: 0x805e000a
> [nsIXMLHttpRequest.open]" nsresult: "0x805e000a (<unknown>)" location:
> "JS frame :: /js/jquery-1.2.1.pack.js :: anonymous :: line 28" data: no]
> xhr.open(type,s.url,s.async);try{if(s.da...[s.url]=modRes;if(!jsonp)success();}else
>
> and
>
> "El uso de getBoxObjectFor() está obsoleto. Intente usar
> element.getBoundingClientRect() si es posible."
>
> getBoxObjectFor() obsolet, try use element.getBoundingClientRect()
>
> David Webster escribió:
>
>
>
> > Hi all,
>
> > I'm having a few issues using jQuery in Firefox 3 and was wondering if
> > anyone else has had similar problems. The problem, as far as I can
> > tell, stems from what appears to be an early execution of the
> > document.ready function - in this case before an external stylesheet
> > has been loaded - making width(), height() and any css() method
> > unpredictable.
>
> > I've put together a test case
> > here:http://dev.cognite.net/sandbox/jquery.html
> > That's basically a wrapper that contains two iframes, both with
> > exactly the same code, one with an embedded css and one with external
> > css. The results I'm getting are that the two iframes report different
> > values for the height, width and colour of elements, but only under
> > Firefox 3. This is an intermittent problem - sometimes it doesn't show
> > up, but most of the time it does, on both Mac and PC.
>
> > Is this the correct behaviour? If so, is there a call I can use
> > instead of document.ready to trigger the code once the CSS has loaded?
>
> > If this is a bug, has it been reported already and is there a known
> > work around - my googling hasn't thrown up anything on this topic.
>
> > Thanks,
> > David.
> > --
> > Kayak Travel:http://www.travellingkayak.com
>
> > __________ NOD32 3205 (20080621) Information __________
>
> > This message was checked by NOD32 antivirus system.
> >http://www.eset.com
