Bug 95307 - [testcase] Frames misinterpret links where located in seperate directory
Summary: [testcase] Frames misinterpret links where located in seperate directory
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 3.3.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-16 23:52 UTC by Carl
Modified: 2012-06-18 14:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Here's the attachment I talked about above (49.79 KB, application/x-gzip)
2004-12-16 23:53 UTC, Carl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Carl 2004-12-16 23:52:09 UTC
Version:            (using KDE KDE 3.3.2)
Installed from:    SuSE RPMs
OS:                Linux

If a frame is located in a seperate directory than the main html file, then the links in the frame ignore the directory where the frame source is located if the link uses ./ to point to its target.  The url that I'm talking about is at www.mtsu.edu/~csal .  I reported this bug a while ago but you couldn't resolve the url and closed the bug report.  So I recreated the page I'm talking about and am including it as a tar package.
Comment 1 Carl 2004-12-16 23:53:58 UTC
Created attachment 8697 [details]
Here's the attachment I talked about above
Comment 2 Thiago Macieira 2004-12-17 04:14:36 UTC
I can confirm this problem, HEAD 20041209.
Comment 3 Carl 2004-12-17 10:25:53 UTC
I forgot to tell you which file to open in the package. It's ~csal.html.
Comment 4 Jure Repinc 2008-04-07 14:37:02 UTC
Using Konqueror 4 (trunk svn r794395) the links still don't open (I get 404 error) when clicking CS3210 and other links in the top left frame.
Comment 5 Myriam Schweingruber 2012-06-18 14:09:35 UTC
Message from the Bugsquad and Konqueror teams:
This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore.
If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report.
Thank you for your understanding.