Closed
Bug 235123
Opened 22 years ago
Closed 20 years ago
link in Frame doesn't find correct target frame
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: noar, Unassigned)
References
()
Details
(Keywords: qawanted)
User-Agent:
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
In the page www.christinastuermer.com/index.html there is a 3-frame-frameset, .
the second frame includes another frameset (this frameset includes the
navigation as top frame), and this frameset (also 3 frames) finally includes
another frameset again (also 3 frames) (sounds complicated ;-) This last
frameset includes a frame named "content", the Navigation link targets are
pointing to this frame (target="content") but mozilla (1.6) doesn't find this
frame and opens the linked page as a parent site. I tried this page at iex and
opera and there it works without probs.
Reproducible: Always
Steps to Reproduce:
1.open www.christinastuermer.com
2.try the links at the navigation
3.look at the sources to see that it is coded correctly
Expected Results:
open in correct target frame
Comment 1•22 years ago
|
||
-> TE?
Comment 2•22 years ago
|
||
I don't see any targets at all in those navigation menus. For that matter,
there are no anchors. There are divs with onclick methods that run some code.
This bug needs a minimal testcase.
Keywords: qawanted
| Reporter | ||
Comment 3•22 years ago
|
||
(In reply to comment #2)
> I don't see any targets at all in those navigation menus. For that matter,
> there are no anchors. There are divs with onclick methods that run some code.
> This bug needs a minimal testcase.
The targets are set in the skript (...,"content",...), if i link to a frame
that is not deeply included into another frameset the whole thing works (so
there shouldnt be an error whithin the script i guess). Maybe the target frame
is not found because of the complex architecture of the frameset.
Updated•21 years ago
|
Product: Browser → Seamonkey
Comment 4•20 years ago
|
||
worksforme with linux trunk 2005032002, I assume the page changed
can you reproduce the bug with a recent build (1.7 or 1.8b1)?
Comment 5•20 years ago
|
||
no response -- resolving WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•