Open
Bug 235179
Opened 21 years ago
Updated 17 years ago
compiling without composer support does not remove "New / Composer Page" menu item
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: jwz, Unassigned)
Details
(Keywords: helpwanted)
User-Agent:
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116
I compiled the 1.6 release tarball with these options:
--disable-composer --enable-plaintext-editor-only
My understanding is that this gives me a build that does not include an HTML
editor. However, there is still a "New / Composer Page" menu item. Selecting
that menu item does nothing. So that menu item shouldn't be there at all.
FWIW, the full set of options I used in my attempt to get the
most-stripped-down-possible web-browser-only build was:
./configure \
--disable-mailnews --disable-ldap --disable-postscript \
--disable-xprint --disable-accessibility --disable-composer \
--enable-plaintext-editor-only \
--disable-calendar \
--enable-extensions=default,-irc \
--disable-tests \
--disable-installer \
--disable-logging \
--enable-crypto \
--disable-debug --enable-optimize --enable-strip \
--prefix=/usr/local
Reproducible: Always
Steps to Reproduce:
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 1•20 years ago
|
||
JS Console says:
Error: NewEditorWindow is not defined
Source File: chrome://navigator/content/navigator.xul
Line: 1
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: DUPEME
Updated•20 years ago
|
Keywords: helpwanted
Updated•17 years ago
|
Assignee: composer → nobody
QA Contact: composer
You need to log in
before you can comment on or make changes to this bug.
Description
•