Insert link to anchor is broken (OK button is grayed out) in Seamonkey Composer and Mail



12 years ago
7 years ago


(Reporter: Vito Tuxedo, Unassigned)



SeaMonkey 1.1 Branch

Firefox Tracking Flags

(Not tracked)





12 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv: Gecko/20060405 SeaMonkey/1.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv: Gecko/20060405 SeaMonkey/1.0.1

In attempting to create a link to an anchor in a Composer page (or Mail composer page), the drop-down dialog box's "OK" button is grayed out. It's initially grayed out when the dialog box appears, but even after selecting the desired anchor from the drop-down selector within the dialog box, the "OK" button still remains grayed out. There is no way to set the link. This bug occurs regardless of whether you use the toolbar button or the "Insert:Link..." menu command.

This is definitely a regression relative to Mozilla 1.7.12, which did not have this bug.

Reproducible: Always

Steps to Reproduce:
1. Insert an anchor on the page at the point to which you want a link to connect. You can do this either by using the toolbar's Anchor button, or by selecting "Named Anchor..." from the "Insert" menu. A drop-down text box appears with its "OK" button grayed out. Type the name of the anchor into the text box. The "OK" is no longer grayed out. Click on "OK" and the drop-down text box rolls up. The anchor is now set at the insertion point you selected.
2. Select the text you want to use to define the link by highlighting it.
3. Click on the "Link" button in the toolbar or by selecting "Link..." from the "Insert" menu. A drop-down dialog box appears. In the "Link Text" section of the dialog box, the selected text for the link is displayed. In the "Link Location" section of the dialog box, a drop-down selector is displayed.
4. Click on the expansion arrow at the right-hand side of the drop-down selector. The selector expands to list all the named anchors. Select the named anchor you want to use. When you release the mouse button, the selected anchor's name appears in the selector.
Actual Results:  
At the conclusion of Step 4 (above), the "OK" button remains grayed out. (So does the "Advanced Edit" button.) There is no way to set the link.

Expected Results:  
At the conclusion of Step 4 (above), the "OK" button should change from grayed out (inactive) to black (active), which allows the user to set the link.

The only other available options within the "Insert:Link..." dialog box are "Help", "Cancel", and "Choose File...". 
"Help" doesn't set the link, and "Cancel" cancels the action. 
The "Choose File..." option does work properly, but that's of no use in setting the link.
I tried precisely the same steps in Mozilla Application Suite 1.7.12 (both Composer and Mail), and the bug does not exist there; there's no problem inserting links to named anchors. As far as I can tell, this is a regression that appears in SeaMonkey.

Comment 1

12 years ago
Just to point out that this also occurs in Windows.
It has been observed with Win2K & XP.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20060404 SeaMonkey/1.0.1

In the Insert Link dialog box, if you choose something from the popup list of anchors, the OK button remains greyed out. You can work around it by adding a character then deleting it.


12 years ago
OS: Mac OS X 10.2 → Mac OS X 10.3

Comment 2

12 years ago
Confirm for Seamonkey 1.0.2 on Linux

Workaround: Select the required target in the drop-down list. Then make some
trivial edit with the keyboard, e.g. add a trailing space, and undo it.
The OK box will become active

Comment 3

12 years ago
*** This bug has been confirmed by popular vote. ***
Ever confirmed: true

Comment 4

12 years ago
This bug makes Seamonkey composer useless, or with the workaround.. very annoying.
I have watched it exist in version 1.03 and 1.04.
I am sticking with Mozilla Composer until this is fixed.

Comment 5

11 years ago
Always Happens/Easily Reproduced:
This also happens to me running SeaMonkey 1.0.6 for Windows (not just a Mac problem:  [Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20061030 SeaMonkey/1.0.6)]  I'm running XP Home SP2.  I am making pages with links at the top to anchors below in the same page.  I did not know about's workaround presented here (slightly editing the anchor name and then fixing it).  I just go to Choose File, pick any file, then replace the chosen file name with one of my named anchors, and that has been working great.  The OK button is enabled once you go through the Choose File procedure, so you can pick your named anchor then.

Comment 6

11 years ago
Bug is still there in SeaMonkey 1.1.4.  (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20070802 SeaMonkey/1.1.4).  I am also finding that, even after using the workaround, the link does not display as underlined in the Normal or Preview modes.


11 years ago
OS: Mac OS X → All
Hardware: Macintosh → All
Assignee: composer → nobody
Keywords: regression
QA Contact: composer
Version: unspecified → SeaMonkey 1.1 Branch

Comment 7

10 years ago
The bug is fixed in SeaMonkey 1.1.9 [Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv: Gecko/20080313 SeaMonkey/1.1.9], so I'm marking it FIXED.

However, the bug described by Aaron Leonard is not fixed. That is, the workaround is no longer necessary; the OK button ungrays itself as soon as any existing named anchor is selected from the drop-down selector, but after clicking OK, the link does not show as underlined blue (#0000ff) text. The link is there, as can be verified by double-clicking on  the affected text or object, which opens the Insert link dialog showing the correct item in the Link Location text box. But there's no way to tell that the link is there just by viewing the displayed content. This condition exists in Composer app and also in the mail composer. It affects only links to named anchors. It does not affect links to external referents.

I have reported the "link doesn't display" bug as Bug 437793.

Last Resolved: 10 years ago
Resolution: --- → FIXED

Comment 8

10 years ago
No bug / patch referenced as the code fix for QA.



7 years ago
Duplicate of this bug: 369122
You need to log in before you can comment on or make changes to this bug.