244020 - Composer "Enter text to display for the link" is broken.

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Michel Bougon]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040514
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040514

In Composer's
"Link Property" Dialogbox
"Enter text to display for the link"  is broken.
The "OK" button never goes active black.  It remains off in its inactive grey

Reproducible: Always
Steps to Reproduce:
1. Click on the "Link" icon
2. Select an Anchor
3. Enter text under: "Enter text to display for the link"
4. Observe that "OK" remains dead (ie, grey) 

Actual Results:  
4. Observe that "OK" remains dead (ie, grey) 

Expected Results:  
"OK" should turn black and become live.

Comment 1

[Alex Eng]

Reproduced on Mozilla 1.8a2 build 2004052307
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a2) Gecko/20040523

Confirming.

Comment 2

[Mike Cowperthwaite]

xref bug 219662 -- same bug for mail composer, except the OK button will enable 
if the link text is typed first, then the anchor selected.

Comment 3

[Gérard Talbot]

I don't understand. Let's say the Link Text is "foo" and let's say the OK button
is enabled as soon as something is typed in Link Text text input. Now, if the
user does not enter any value for Link Location and if the user clicks the OK
button, then this should be the code added in the source:

<a href="">foo</a>

Do we really want this? We already know that Mozilla handles this type of link
differently from other browsers like MSIE 5+.
Shouldn't Composer prevent this type of markup code?
If Composer does not add <a href="">foo</a>, then what should it add in the
source? And how would such code addition meet the user's expectations?

I'm just asking questions here.

Comment 4

[Michel Bougon]

How would such code addition meet the user's expectations ?

As a long-time heavy user of Named Anchor links in Composer,  my Very Strong
expectation is this--

(1)  If the user highlights "foo bar red" in his/her text, then the default for 
"Enter text to display for the link"
should be "foo bar red" 
(like in Netscape)

And the html code will be --
<a href="....">foo bar red</a>


(2)  If the user does *not* highlight any phrase in his/her text,  and the
anchor selected from the Named Anchor dropdown menu is  #red_barron_fokker
 then the default for 
"Enter text to display for the link"
should be "#red baron fokker" 
and that string will be inserted at the cursor location.
(like in Netscape)

And the html code will be --
<a href="....#red_baron_fokker">#red_baron_fokker</a>
(like in Netscape)

That is, my expectation is to continue to receive the same default as the Very
Convenient default that exists in Netscape since its birth............   

The second case is Extremely Convenient for creating an index list (typically,
at the top of the page) from the Named Anchors (such as, "#red_baron_fokker")
created along the text (typically while reading the text)

I just described the existing Netscape defaults.    Actually, my preference
would be that, in the second case,  the string inserted at the cursor be
stripped of the"#",  and thus the html code would be --
<a href="....#red_barron_fokker">red_barron_fokker</a>

Thanks !
Michel

Comment 5

[Robert Kaiser]

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

Comment 6

[Robert Kaiser]

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