231119 - "Replying to a Message" in "Help" gives bad menu path on placement of quotes in replies

Status: VERIFIED FIXED

(Documentation Graveyard :: Help Viewer, defect)

Description

[David Robinson]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Between 1.4 and 1.5, the setting for the position of quotes within reply
messages was moved from (in the browser window) Edit>Preferences>Mail &
Newsgroups>Composition to (in the mailer window) Edit>Preferences>Mail &
Newsgroups Account Settings>[MAIL ACCOUNT NAME]>Composition & Addressing. This
change is not reflected in Help>Using Mail>Sending Messages>Replying to a
Message.  This problem is still present in 1.6.

Reproducible: Always

Steps to Reproduce:
1. Use Help
2.
3.

Actual Results:  
The same, of course.

Expected Results:  
It shou/d have givent he right path to the quote positioning dropdown dialog.

Comment 1

[Stefan Borggraefe]

*** Bug 231419 has been marked as a duplicate of this bug. ***

Comment 2

[Stefan Borggraefe]

Attachment: Patch

This also corrects another small mistake in this section: Not "Start my reply
above the quote" is the default, but "Start my reply below the quote".

Comment 3

[R.J. Keller]

Comment on attachment 139429 [details] [diff] [review]
Patch

> +replying".</li>

You should use &quot; instead of ".

> +<li>Select "below the quote (recommended)" to place 

here too


> +<li>Select "below my reply (above the quote)" to place your signature

and here.

Content looks good! r=[e-mail] with my comments applied.

Comment 4

[Stefan Borggraefe]

Attachment: The same patch with " converted to ".

Now I just need someone to check this in. ;-)

Comment 5

[Stefan Borggraefe]

Comment on attachment 139607 [details] [diff] [review]
The same patch with " converted to ".

Transfering rlk's r+.

Comment 6

[R.J. Keller]

--> borggraefe

Comment 7

[R.J. Keller]

Fix checked in.

Comment 8

[Stefan [:stefanh]]

*** Bug 235331 has been marked as a duplicate of this bug. ***

Comment 9

[Stefan Borggraefe]

*** Bug 250886 has been marked as a duplicate of this bug. ***