Bug 85901 - when I go to http://www.srh.noaa.gov/lzk/, I click on my county and it does not map to the correct county. It does under IE, thunderbird, mozilla etc.
Summary: when I go to http://www.srh.noaa.gov/lzk/, I click on my county and it does n...
Status: RESOLVED DUPLICATE of bug 59701
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-24 23:55 UTC by jeffjohnson
Modified: 2005-03-09 00:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jeffjohnson 2004-07-24 23:55:17 UTC
Version:           3.2.3 (using KDE 3.2.3, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.95-default

when I go to http://www.srh.noaa.gov/lzk/, I click on my county and it does not map to the correct county. It does work under IE, thunderbird, mozilla etc.
Comment 1 Tom Shaw 2004-10-09 04:47:33 UTC
Same issue here and I emailed the noaa.gov people and after some testing he came to this rather general conclusion.

He said;
"The fact that when you click on areas in the southern part of the map 
and get forecasts for the northern areas tells me the browser is not 
sending the proper x,y pixel coordinates to the server.  I don't know 
the reason for the offset."

This is happening with:
http://www.wrh.noaa.gov/otx/

I've changed the browser id/user agent and it does change the behavior but it never makes the map calibration correct to the proper geographical area.

This is with Konqueror 3.3.0 on Gentoo.
Comment 2 Tom Shaw 2005-03-08 23:50:04 UTC
This is a duplicate of bug 59701 and the patch in that bug fixed the issue
with the maps at noaa.gov. I applied the patch to kdelibs 3.4_rc1 and it works fine now.
Comment 3 Matt Rogers 2005-03-09 00:24:13 UTC
Duplicate of 59701 and fixed for KDE 3.4.1

*** This bug has been marked as a duplicate of 59701 ***