Open
Bug 339762
Opened 18 years ago
Updated 2 years ago
Spellchecking not working for non privileged chrome
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
UNCONFIRMED
People
(Reporter: sylvain.pasche, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier:
Moreover, triggering the context menu generates the error "uncaught exception: Permission denied to create wrapper for
object of class UnnamedClass".
As the binding depends on XPCOM components I guess this is not trivial to fix. The quick workaround would be to disable spell check gracefully in this situation.
Reproducible: Always
Reporter | ||
Updated•18 years ago
|
Blocks: remote-xul
Reporter | ||
Updated•18 years ago
|
Blocks: SpellCheckTracking
Comment 1•18 years ago
|
||
This will proably become moot when bug 336799 is fixed. However, that will probably just disable it for all XUL. Will will probably be adding back this capability in chrome in the future, which should include this bug for unprivledged chrome.
Comment 2•18 years ago
|
||
Cut, copy, paste also doesn't work on the context menu, see bug 321879, that's a related bug.
Depends on: 321879
Updated•18 years ago
|
No longer blocks: SpellCheckTracking
Comment 4•14 years ago
|
||
What is the status of this? Should we close as WFM, WONTFIX?
Comment 5•14 years ago
|
||
Moving to Core :: XUL for a decision. If this is actually a result of _remote_ XUL we might wontfix (since that's off by default now, bug 546857). Maybe we want to be able to support chrome://-but-unprivledged XUL with spellcheck? Probably still low-priority, though.
Component: General → XUL
Product: Firefox → Core
QA Contact: general → xptoolkit.widgets
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•