109307 - Link bar not dynamically updated

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Robert Crews]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.5+) Gecko/20011022
BuildID:    2001102203

I'm excited about the links bar so I wrote a JavaScript function that
dynamically builds links from the headings in my page. Unfortunately, the links
bar appears to not dynamically update. My attachment shows the problem.
Ironically, note how the script verifies that the link created with the
JavaScript is in the DOM before the link bar appears (appears without the
dynamically added component).

Reproducible: Always
Steps to Reproduce:
1. Write JavaScript that appends link elements to the head element.
2. Load the page.
3. Note how the dynamically added elements are not available from the links bar.

Actual Results:  Expected available items are not available.

Expected Results:  Newly added items available to be clicked.

Comment 1

[Robert Crews]

Attachment: HTML file with JavaScript that dynamically adds a link element

The file contains a link (rel="Copyright") to assure the link bar appears. (I
have mine set to only appear when needed.) It also contains JavaScript that
dynamically adds a link (rel="Start") that should make the Top button active.

Comment 2

[Christopher Hoess (gone)]

This should work after XBLification using hyatt's C++ events. cc'ing hyatt to 
remind him that we also need C++ events for when an existing <link> element has 
its rel or rev attributes created, changed, or destroyed.

Comment 3

[Christopher Hoess (gone)]

oops, should have been Platform->All

Comment 4

[Stuart Ballard]

Hyatt's events are now used, and this should now work for *adding* link
elements, but not for when they are changed or removed. Obviously this is a
problem :)

Note particularly that the "decorators" used in the current design have a
fundamental flaw in that they don't even honor cases where the href changes,
which shouldn't require an event at all. We might also need code to make the
tooltip dynamically populate itself when it shows, to avoid requiring an event
when the TITLE changes. rel and rev changes, though, really do require events
(firing DOMLinkRemoved followed by DOMLinkAdded would work, probably).

As part of the XBLification, I hope to change the data structure used so that it
will be possible to track DOMLinkRemoved events and map them efficiently to the
appropriate toolbar item to remove it. I don't fully understand the current data
structure, but I don't see an easy way to implement removal correctly with it.

Comment 5

[Christopher Hoess (gone)]

*** Bug 140083 has been marked as a duplicate of this bug. ***

Comment 6

[josh]

I'd really like to see this change happen too.

If a CGI's output is targeted to a frame, it's currently not possible to update
the site navigation bar.  Fixing this bug would change that.

An alternative that would work just as well, would be to allow onclick events
for the link bar to call JS functions, but maybe that doesn't meet W3C specs.

Comment 7

[Robert Kaiser]

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 8

[Robert Kaiser]

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 9

[Robert Kaiser]

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 10

[Robert Kaiser]

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 11

[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