Link properties dialog doesn't display named anchors in other web pages

NEW
Unassigned

Status

18 years ago
6 years ago

People

(Reporter: sborusu, Unassigned)

Tracking

({helpwanted})

Trunk
helpwanted

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
BuildID:    Netscape 6 (Mozilla/5.0 20001108)

I created one document with one named anchor (target) and saved it.While 
creating link in another new document in composer, I choose the previous 
document as Link location and that dialog didn't show any named anchors in 
previous document.

Reproducible: Always
Steps to Reproduce:
1. Create two new documents using composer and save the first one as Doc1.HTML, 
the other one as Doc2.HTML.
2. Open the Doc1 page in composer, type "This is Doc1" and create a target and 
name it as Doc1 and Click on save button. 
3. Open the Doc2 page in composer, type some text, "Go to Doc1" and select the 
text and click on Link button on the composition toolbar. 
4. In the resulting Link Properties dialog, Click on "Choose File" button and 
select the local file to be linked as "Doc1.HTML" 



Actual Results:  Select a Named Anchor List box showed "No named anchors in 
this page"

(Click on More properties to See this Textbox)

Expected Results:  Select a Named Anchor List box should show up the target you 
created in Doc1.

Comment 1

18 years ago
I also see this on Mozilla build 2000112304 win32. Confirming. I couldn't find
any dup for this, although it would be surprising that nobody has seen it
before. If it's not a dup, then it is a regression.
Fabian.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

18 years ago
yes, this should display the named anchors, assigning to cmanske
Assignee: beppe → cmanske
Target Milestone: --- → mozilla0.9

Comment 3

18 years ago
We simply didn't support grovelling for the named anchors in another page.
This requires somehow loading any abritrary page (the file used for the link
SRC) and parsing it to find all its anchors. Obviously not as hard to do for
local files, but difficult when link is remote, so we didn't implement showing
named anchors to pages other than the one being edited.
I doubt if we have time to address this for mozilla0.9 target, but will keep
that milestone just in case we do.
Status: NEW → ASSIGNED

Comment 4

18 years ago
No time this round.
Target Milestone: mozilla0.9 → Future

Comment 5

18 years ago
Added "in other web pages" to summary.
Summary: Link properties dialog doesn't display named anchors → Link properties dialog doesn't display named anchors in other web pages

Comment 6

17 years ago
spam composer change
Component: Editor: Core → Editor: Composer
*** Bug 154347 has been marked as a duplicate of this bug. ***

Comment 8

16 years ago
*** Bug 154577 has been marked as a duplicate of this bug. ***

Comment 9

16 years ago
Isn't this OS=All ? (this bug has been quiet a while, is CManske still at netscape?)
*** Bug 212476 has been marked as a duplicate of this bug. ***

Updated

15 years ago
Keywords: helpwanted
OS: Windows NT → All
Hardware: PC → All
Product: Browser → Seamonkey

Comment 11

14 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050313

When I edit <http://thecia.com.au/star-trek/place-r.shtml> in Composer, the Link
Properties dialog shows the text from <h1>, <h2>... in reverse alphabetical
order from the bottom of the page.
Assignee: cmanske → nobody
Status: ASSIGNED → NEW
Priority: P3 → --
QA Contact: sujay → composer
Target Milestone: Future → ---

Comment 12

6 years ago
Just to update : I checked, and this has not been implemented in V2.15.
If implementation is difficult, at least, when choosing to link to a different file, then the pop-up list should be cleaned and not showing any more the anchors of the current file, as this can be confusing, especially if by change you have the same anchor names in the current file and in the file you want to link to.
You need to log in before you can comment on or make changes to this bug.