Closed
Bug 196892
Opened 23 years ago
Closed 23 years ago
nsIEditor has XPCom method do, which is forbidden in javascript
Categories
(Core :: DOM: Editor, defect)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
People
(Reporter: oct, Assigned: mozeditor)
Details
(Keywords: topembed-)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021226 Debian/1.2.1-9
nsIEditor.idl describes a do() method which cannot actually be used in javascript.
do() is a reserved keyword (see http://bugzilla.mozilla.org/show_bug.cgi?id=196836)
Reproducible: Always
Steps to Reproduce:
Expected Results:
rename the do() in doTransaction() probably.
Comment 1•23 years ago
|
||
Um.. Editor bug. ;)
This is blocking use of nsIEditor outside of C++.
Assignee: dougt → jfrancis
Severity: normal → critical
Status: UNCONFIRMED → NEW
Component: XPCOM → Editor: Core
Ever confirmed: true
Keywords: topembed
QA Contact: scc → sairuh
| Reporter | ||
Comment 2•23 years ago
|
||
It's not really blocking:
You can use the "transactionManager" attribute of the Editor and call
doTransaction on this object to get (i guess) the same result.
Comment 3•23 years ago
|
||
180 /** do() fires a transaction.
181 * It is provided here so clients can create their own transactions.
182 * If a transaction manager is present, it is used.
183 * Otherwise, the transaction is just executed directly.
184 *
185 * @param aTxn the transaction to execute
186 */
So you may not have a transaction manager....
Comment 4•23 years ago
|
||
minusing topembed as no known current embeddors are JS'ing nsIEditor. please
re-nominate if mistaken.
Comment 5•23 years ago
|
||
Well, they _can't_ very well JS using editor, since they would be unable to do
transactions.
Pierre, think you can write a patch for this? ;)
| Assignee | ||
Comment 6•23 years ago
|
||
uh, Kin changed Do() to DoTransaction() some time ago, ya? This is fixed already.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Comment 7•23 years ago
|
||
Um, yes. It was fixed two months ago, a month after this bug was filed. The
patch was on bug 192569.
Reopening to give this the right resolution...
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 8•23 years ago
|
||
FIXED.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•