605513 - editor's getHTMLEditor fails with XULRunner 2.0

Status: RESOLVED WORKSFORME

(Core :: DOM: Editor, defect)

Description

[Ben Longoria]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.17.8 (KHTML, like Gecko) Version/5.0.1 Safari/533.17.8
Build Identifier: xulrunner-2.0b8pre.en-US.win32.zip

XUL editor element hangs on null reference on line 90.
The this.editingSession.getEditorForWindow(containingWindow) call on line 91 is returning null.

The Error console displays:
Error: editor is null
Source File: chrome://global/content/bindings/editor.xml
Line: 90


Reproducible: Always

Steps to Reproduce:
1. Package a XULRunner app using 2.0 that uses the editor.
2.  Call getHTMLEditor on editor passing a window reference
Actual Results:  
getHTMLEditor throws an exception

Expected Results:  
get an instance of nsIHTMLEditor

Comment 1

[Benjamin Smedberg]

Please file bugs in the appropriate component, Toolkit/XULRunner is seldom correct except for xulrunner-specific packaging or deployment issues.

Comment 2

[(no longer active)]

Is this a new regression?  Can you check what changeset your XULRunner has been built from?

Comment 3

[Ben Longoria]

I've been using pre-built XULRunner 1.9.0.6 binaries and haven't experienced this.
Only once switching to XULRunner 2.0.

I'm using the builds from ftp.mozilla.org:

http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/latest-trunk/xulrunner-2.0b8pre.en-US.win32.zip

Comment 4

[Ben Longoria]

http://atsosxdev.doit.wisc.edu/~blongoria/xulrunner/WinXR20Editor.zip

This is a barebones Windows XULRunner based app using XULRunner 2.0 that demonstrates the bug.

It uses the editor and calls the getHTMLEditor method that is exposing the bug.

I've put a setInterval for about 5 seconds after launch before calling getHTMLEditor to ensure there isn't some funky race condition.

Comment 5

[Ben Longoria]

The latest nightlies aren't exhibiting this bug. It seems to be fixed.