Closed
Bug 134231
Opened 23 years ago
Closed 15 years ago
Composer retains hyperlink qualities of initial hyperlink unless "format|discontinue links" is selected
Categories
(SeaMonkey :: Composer, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: TucsonTester1, Unassigned)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9+)
Gecko/20020329 Netscape6/6.2.1+
BuildID: 2002032903
This is in reference to previous bug #133982. Although this seems to be WAD,
this issue has changed in this build. If link from the toolbar is initially
selected and a hyperlinked created, Composer does NOT retain hyperlink
qualities. If, however, normal text is typed and then that text is highlighted
and hyperlinked, the hyperlink qualities are retained.
Reproducible: Always
Steps to Reproduce:
1.Launch NS 6.2.1+ build 200203290.
2.Launch new, blank Composer window.
3.Type some text.
4.Highlight text.
5.Click link icon on toolbar.
6.Enter info for hyperlink, click ok.
7.Hit enter key to advance down Composer page.
8.Enter more text.
Actual Results: The text on the next line is linked to the original hyperlink.
Link qualities must be removed by selecting format|discontinue link.
Expected Results: I would expect only original text to be linked.
The need for the user to select Format|Discontinue link for this seems
cumbersome. Also, it's somewhat inconsistent since it only occurs if the link
is the first item created on the page, and does not happen if the original text
is manipulated (i.e. centered).
Comment 2•23 years ago
|
||
I explained why we don't want to discontinue links with Enter keypress in
bug 133982. The reason why it appears to be true only when it's the "first item
created on the page" is because other tags such as centering isolate the style
from continuing after Enter is pressed.
I'm still not sure this is a good thing to do.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•17 years ago
|
Assignee: cmanske → nobody
Status: ASSIGNED → NEW
QA Contact: sujay → composer
Target Milestone: Future → ---
Comment 3•16 years ago
|
||
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
Status: NEW → UNCONFIRMED
Comment 4•15 years ago
|
||
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
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•