301818 - 'Spellcheck as you type' has disappeared

Status: VERIFIED INVALID

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Michael Graubart]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716

In Mail -> Compose, 'Spellcheck as you type' seems to have vanished from
'Options'. If this is deliberate, I wonder why? If not, it was really useful
(once one got used to it), so please reintroduce.

Reproducible: Always

Steps to Reproduce:
1. In Mail -> Compose, type a message and misspell a word.
2.
3.

Actual Results:  
Nothing.

Expected Results:  
It should have been possible to choose 'Spellcheck as you type', and in that
case the misspelt word should have been underlined in red.

Comment 1

[Stefan [:stefanh]]

Michael, are you reporting this as a bug in the Mozilla 1.7.10 release? The
"spellcheck as you type" feature was introduced in the suite by bug 291799 and
was never checked in to the 1.7 branch. So, you'll need a Mozilla/SeaMonkey
trunk build newer than 2005-05-13...

Comment 2

[Michael Graubart]

Stefan, I assumed that since v.1.7.10 had been released on 21/7/2005, it would have incorporated 
things like 'Spellcheck as you type'. I also have the 2/7/2005 trunk build — but the 'latest nightly build' 
directory has been stuck at 2/7/2005 for several weeks, presumably because attention has been 
focussed on eliminating the scroll-bar bug in time for the release of 1.7.10. When will there be a new 
trunk build to download?

Comment 3

[Stefan [:stefanh]]

(In reply to comment #2)
> Stefan, I assumed that since v.1.7.10 had been released on 21/7/2005, it would
have incorporated 
> things like 'Spellcheck as you type'.

The 1.7.x branch doesn't really incorporate new features, it's a stable branch
maintained by Mozilla Foundation - you'll normally only see security fixes
incorporated in the 1.7.x releases. Note that a "trunk" build is based on code
from a separate branch - the development branch. 

> I also have the 2/7/2005 trunk build — but the 'latest nightly build' 
> directory has been stuck at 2/7/2005 for several weeks, presumably because
attention has been 
> focussed on eliminating the scroll-bar bug in time for the release of 1.7.10.
When will there be a new 
> trunk build to download?

The reason for the nigtlies being "stuck" at 2/7 is that the directory has
changed ;) The directory you refer to is obsolete, new trunk builds can be
downloaded at http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-trunk/

At the moment, the mac build machine is down, so the latest nightly you'll see
is from 2005-07-22.

FYI, the Mozilla Application Suite is now known as SeaMonkey. The project of
developing the suite has been taken over by a independent group. Read more at
http://wiki.mozilla.org/SeaMonkey:Home_Page

See also http://www.mozilla.org/projects/seamonkey/

Comment 4

[OstGote!]

Mozilla 1.7.x does not contain this. Never. Please use Seamonkey 1.0a builds
(formerly known as Mozilla trunk builds).

Comment 5

[Michael Graubart]

Stefan and Ostgote: thank you very much indeed for all this information; I had
no idea about the move to an independent organization. And I have now downloaded
and am using SeaMonkey 2005072214. I am not a programmer, but I have been quite
actively involved (as a user) with the Mozilla Suite by regularly reporting bugs
ever since about v. 1.1 or thereabouts � I think, for instance, that I was the
one who started the recent 'scroll-bar' hare running � so I am glad to be able
to keep in touch.

I have four questions that I have not been able to resolve by following and
reading all the links you, Stefan, have provided:

1. Does the SeaMonkey team still want users to report bugs in nightly builds?

2. If so, does one still report them via Bugzilla, or has SeaMonkey now got its
own reporting website?

3. Will the spelling dictionaries that one downloads from
<http://dictionaries.mozdev.org/installation.html> work in future nightlies or
stable releases of SeaMonkey and be downloadable from the same URL?

4. What will happen to bugs previously reported to Bugzilla which have not been
listed in the two short lists of approved and not yet approved bugs on the
SeaMonkey pages? (E.g. the hoary old one about'Find' in 'Manage Bookmarks' not
showing where a bookmark is, or the one about 'Forward', unlike 'Reply', not
preserving the character coding of a received message.)

Comment 6

[Stefan [:stefanh]]

Verified invalid.

Michael,

If you have any more questions or if you feel that my answers need further
explanation, feel free to e-mail me. Ideally, we should keep the bug reports as
clean as possible and discuss things not relevant to the bug somewhere else.

(In reply to comment #5)

> 1. Does the SeaMonkey team still want users to report bugs in nightly builds?

Yes, they do! Reporting bugs in nightly builds is very important. It's really
essential!

> 2. If so, does one still report them via Bugzilla, or has SeaMonkey now got its
> own reporting website?

You just report them via Bugzilla, bugs for SeaMonkey goes for the moment in the
"Mozilla Application Suite" product. In the future the product will be "SeaMonkey".

> 
> 3. Will the spelling dictionaries that one downloads from
> <http://dictionaries.mozdev.org/installation.html> work in future nightlies or
> stable releases of SeaMonkey and be downloadable from the same URL?

Yes. There are no plans (that I know of) of stop using MySpell. Of course I
can't say anything about the URL, since providing/hosting the dictionaries is a
separate project. So, if the people that provides the dictionaries decides to
stop the  project the URL will be gone...
> 
> 4. What will happen to bugs previously reported to Bugzilla which have not been
> listed in the two short lists of approved and not yet approved bugs on the
> SeaMonkey pages? (E.g. the hoary old one about'Find' in 'Manage Bookmarks' not
> showing where a bookmark is, or the one about 'Forward', unlike 'Reply', not
> preserving the character coding of a received message.)

Do you mean bugs blocking the SeaMonkey 1.0 release? Setting bugs to blockers
is, basically, just a way for the release engineers to make sure the bugs are
fixed before the release. Ideally, all bugs should be  fixed, but in a
non-perfect  world you have to prioritize ;)

Comment 7

[Stefan [:stefanh]]

Oops...