Confirming that this is 4xp. I prefer the method in bug 97284, allowing the page to make an element in the page editable.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This specific request will never be implemented. Mozilla does not come with Java and therefore I can't see anyone paying someone to implement 4.x-compatible java composer plugin support -- which were pretty obscure to begin with. plugins in a generic sense, maybe. I saw a bug that implied something like this might be necessary for PGP support, for example, so there may be enough interest to do something about it someday (am I non-committal enough for you?). An XPCOM-based plugin mechanism could get some support.
... will never be implemented ... That are hard words. But where is the problem? We have a package with a browser, a editor, a mail-client ... We can open the mail-client out of the browser (mailto:..) Why can't we open the composer in the same way??? Why???????
reassign to new account
Assignee: syd → composer
Status: ASSIGNED → NEW
I liked the idea of opening an url in the composer by setting a link to composer://www.mysite.com/myfile.html, the same way we use mailto:... As for the comment on "mailto:... -We don't have JAVA..." how does Mozilla open a new Mail window (i.e. mailto:firstname.lastname@example.org) ?? Is there no way to accomplish this the same way for the composer???
Assignee: composer → nobody
QA Contact: sujay → composer
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.