Open
Bug 359190
Opened 18 years ago
Updated 2 years ago
With JavaScript added anchors to an dynamic created iFrame force reload of the IFrame when clicked on the anchor link.
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
NEW
People
(Reporter: TinoButz, Unassigned, NeedInfo)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
When I add with JavaScript an anchor to an dynamic created iFrame, the link refering to this anchor reloads the IFrame instead of jumping to the correct anchor position. I have also tried to give the IFrame a name and a id, but still the same behaviour. Even I know this is not a reference, but with the Internet Explorer it works fine for me.
You can review this problem with my example code:
http://www.tino-butz.de/firefox_anchor_bug.html
Reproducible: Always
Steps to Reproduce:
1. open the url in your browser
2. click on the link in the iFrame
Actual Results:
you can see that the iFrame is getting reloaded (this should not happen, as it is a link to an anchor)
Expected Results:
Not reloading the iFrame - jump to the anchors.
Seems like Firefox does not understand dynamic added anchors. If you reload the iFrame first and than click on the link there is a differend (normal?) behaviour.
Comment 1•18 years ago
|
||
This is not a calendar bug. Over to Firefox for triage.
Product: Calendar → Firefox
Updated•18 years ago
|
QA Contact: general → general
Comment 3•18 years ago
|
||
(In reply to comment #2)
> Could someone please confirm this bug?
>
(Paul Dickler)
I created BUG 366057, which applies to Frameset: However, I believe this is the same bug. It's dynamically-created anchors not being addressable when assigned to
document.location.hash.
Comment 4•16 years ago
|
||
Looks to me like more or less a duplicate of bug 210862. Marking dep for now.
Depends on: 210862
Comment 6•16 years ago
|
||
This isn't quite a duplicate of bug 210862. This happens because the base URI is the URI of the document that did the write(). So this is basically dependent on bug 275689.
When fixing, the location.hash change (bug 366057) should also be fixed....
Comment 7•11 years ago
|
||
Might be a dup of bug 881487 ? Anyway, TC is not there anymore (server gone)..
Flags: needinfo?(TinoButz)
Comment 8•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•