Open Bug 101374 Opened 23 years ago Updated 3 years ago

Remove Link works inconsistently when only removing part of a link

Categories

(Core :: DOM: Editor, defect, P5)

x86
All
defect

Tracking

()

mozilla1.4beta

People

(Reporter: TucsonTester2, Unassigned)

Details

(Whiteboard: 1 day)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4)
Gecko/20010913 Netscape6/6.2
BuildID:    2001091303

If you create a link in text, but then decide you wish to un-link a portion of
the text, you have to select remove link twice to remove text from the end of
the link. The first time you select remove link, it breaks the link at that
point, leaving you with two separate sections of linked text.  Then you have to
select remove link again to actually remove the link.  However, if you remove
the link from a portion of the text that doesn't include the end of the link,
then the selected text is removed from the link with the first selection of
remove link.

Reproducible: Always
Steps to Reproduce:
1.Open a new composer page
2.Type in "This link is a test"
3.Highlight the text entered and click on the link button
4.Enter location to link to and click ok
5.Highlight "is a test" and right click on it (or use format, remove link)
6.Click on Remove Link

Actual Results:  The text "is a test" will still be a link, but if you check the
show all tags view, it will show up as a separate link.  If you wish to remvove
the link from it, you must select Remove Link a second time.  If you select a
portion of text that does not include the end of the link (in this example
select "is a" instead of "is a test" and then select remove link, the link is
removed the first time.  In this example, leaving you with 2 links, "This link"
and "test"

Expected Results:  Selecting a portion of text that is linked and then selecting
remove link, I would expect the link to be removed from the selected text.  I
would also expect it to work the same way regardless of whether or not the
portion of the link selected included the end of the link.

While this is very eaxy to work around, I would think it would be frustrating
for someone who is creating a text document with multiple links (if they wish to
make alterations).
-->cmanske
Assignee: syd → cmanske
I only see this problem when you make a link that goes to the end of the document,
and the portion you select also goes to the end of the document.
The problem must be in the "rules code"; removing a link enters editor core
code at nsHTMLTextEditor::RemoveInlineProperty()
Assignee: cmanske → jfrancis
forgot to change component to Editor:core
Component: Editor: Composer → Editor: Core
096
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Whiteboard: EDITORBASE; 1 day
Target Milestone: --- → mozilla0.9.6
Target Milestone: mozilla0.9.6 → mozilla0.9.7
098
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Spock says "what it is doing is logical" 
Whiteboard: EDITORBASE; 1 day → 1 day
pushing off 098 to 099
Target Milestone: mozilla0.9.8 → mozilla0.9.9
the swami says: things that will not land in 099!
Target Milestone: mozilla0.9.9 → mozilla1.0
Moving bugs to Mozilla1.1 that are not EDITORBASE+.
Target Milestone: mozilla1.0 → mozilla1.1
The trunk is the wave of the future!
Target Milestone: mozilla1.1alpha → mozilla1.1beta
The days of having a half dozen milestones out in front of us to divide bugs 
between seem to be gone, though I dont know why.  Lumping everything together as 
far out as I can.  I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.1beta → mozilla1.2beta
migrating milestones now that there are more available.  i'll pull these back as
I work on them
Target Milestone: mozilla1.2beta → mozilla1.4beta
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: ASSIGNED → NEW

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: minor → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.