Closed Bug 107155 Opened 24 years ago Closed 24 years ago

topozone.com - TOPOZONE doesn't display maps

Categories

(Tech Evangelism Graveyard :: English US, defect, P1)

Product:
Tech Evangelism Graveyard
Component:
English US
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: gschueler, Assigned: bc)

References

(
URL
)

Details

(Whiteboard: [bae:20011126][DOCTYPE][TOOL][DYNAPI][aok])

Attachments

(1 file)

source with base href and DOCTYPE removed => QUIRKS mode
20.13 KB, text/html
Details
all parts of the map are loaded onto the same spot blow the designated area. Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.5+) Gecko/20011009
Confirmed on linux. Not a blocker.
Severity: blocker → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows NT → All
Hardware: PC → All
*** Bug 110295 has been marked as a duplicate of this bug. ***
heh, who can hike without topos!
Priority: -- → P1
Whiteboard: [bae:20011126]
*** Bug 111867 has been marked as a duplicate of this bug. ***
Any progress on this one? I notice from a comment from Bug#:111867 that there appear to be issues with TopoZone's js & html. Has TopoZone been contacted? --Doug
roberts, no not yet, sorry, but have been really swamped. I will send them a note tonight. you can tell when a site has been contacted when the Status changes to Assigned and the target milestone is set for follow up testing.
Error: is is not defined Source File: http://www.topozone.com/script/dynapi/src/dynapi.js Line: 221 Error: setting a property that has only a getter Source File: http://www.topozone.com/map.asp Line: 98 map displays fine in NS62 but is incorrectly displayed in Mozilla. Obvious Server Side sniffing issues. Contact info info@topozone.com. Sent message and will followup in Jan.
Status: NEW → ASSIGNED
Whiteboard: [bae:20011126] → [bae:20011126][USERAGENT]
Target Milestone: --- → Jan
I took the liberty of contacting them with the previous comments on this bug. They stated that eventhough it did not fully pass the test it should not be broken in a typical browser. However, the developer had me test out an alternate link where he had made some modifications. These worked great. He mentioned he was going to test with other browsers and if all is good update the pages. He was quite helpful but did maintain it was not a problem in other browsers. K
ok, i looked again and did a diff on the source from mozilla and the source from ns6.2. The only difference was in an object tag which I would not think would cause the difference in the layout, so I was wrong when I attributed the problem to server side sniffing: <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=4,0,2,0" width="468" height="60"> <param name="movie" value="/TopoNet/banner.swf"> <param name="quality" value="best"> <param name="play" value="true"> <embed src="banner.swf" type="application/x-shockwave-flash" width="468" height="60" pluginspage="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash" quality="best" play="true"> </object> So, the next candidate is the dynapi script or the other script http://www.topozone.com/script/maptools.js. I can not find anything in particular that stands out in maptools.js. Kevin, since you have a contact with the developer can you ask him what version of dynapi he is using? It is not in the source file.
I've made the request and will post the response as soon as I get it. K
Go, team: way to hustle! Can't wait til I can't see my TopoZone maps in Mozilla. --Doug
Oops: One too many brown ales. Meant to say: "Can't wait til I _can_ see my Topozone maps in Mozilla".
Got that object tag fixed yet? --Doug
Ah, I am full of crap. This site works in NS 6.2 and Mozilla 0.9.4 but not in 0.9.5 or later. DOCTYPE <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN"> http://www.bath.ac.uk/%7Epy8ieh/cgi/compat-test.pl?DOCTYPE=%3C%21DOCTYPE+HTML+PUBLIC+%22-%2F%2FW3C%2F%2FDTD+HTML+4.0+Strict%2F%2FEN%22%3E&MODE=full => STRICT Mode. Kevin, Can you contact your developer and ask if he can remove the DOCTYPE? That will invoke quirks mode in NS6.2 and in recent post 0.9.4 Mozilla builds. I am attaching the source with a base href and the DOCTYPE removed. This displays correctly in recent Mozilla builds.
updating whiteboard=> DOCTYPE
Whiteboard: [bae:20011126][USERAGENT] → [bae:20011126][DOCTYPE]
I never got a response to the question about the dynapi version from TOPOZONE. I'll ask again along with the question about the DOCTYPE.
I've not heard back from Ed McNierney <ed@topozone.com> on my last two requests.
I sent another note to the info address and ed explaining my mistaken earlier analysis and explaining the DOCTYPE issue.
Just in from Ed at Topozone: I'm using the current (2.5.6) release. I got an email this morning from Robert Clary at Netscape telling me that if I remove the DOCTYPE statement from my HTML, my page should display just fine. [edit] So I guess I just need to include it and remove it on the same page and everything will be fine <g>....
Did Ed at Topozone give an indication on when he might get around to this? --Doug
He said he wouldn't have time to work on this till next week.
I've been in communication with Ed @ Topozone (ed@topozone.com). It seems he's been getting some conflicting advice regarding this issue: "I've got one group of Mozilla developers telling me that all the pages on my site MUST pass the W3C HTML validator (which *requires* the DOCTYPE tag) and another telling me I must *remove* the DOCTYPE tag. I can assure you I will do at least one of those things...." Maybe this should get sorted out? --Doug
I sent a message to him detailing that he is invoking standards mode with his DOCTYPE. I recommended that he either remove the DOCTYPE or remove the URI. I gave him references to the mozilla.org DOCTYPE/quirks article. He has not replied to me.
Ok: There's apparently been some confusion wrt Ed @ Topozone. He seems to think somebody on the Mozilla team is going to give hime a specific recommendation on how to handle the DOCTYPE issue. Before this is addressed with him again, though, I have a request: could somebody please explain to me why NS6.2 (based on Mozilla 9.4.1) can render the TopoZone mapes correctly, and newer versions of Mozilla cannot? Are the newer Mozillas more standards-complient, or is there a bug in the current Mozilla? If it is a standards issue, and TopoZone is producing non-complient html, could someone plese explain to me (and to Ed) _exactly_ what the fix for his site should be? Thanks, --Doug
The issue is that a bug was fixed in Mozilla after Netscape 6.2 was released that changed whether an HTML 4.01 Transitional DOCTYPE with URI invoked Quirks or Standards mode or not. See bug 42525 and bug 55264 for the gory details. There are several approaches Ed can take. Remove the DOCTYPE altogether to invoke Quirks mode, Remove the URI from the DOCTYPE to invoke Quirks mode, change the layout of his page so that it lays out as he intended for downlevel browsers that do not support Standards mode as well as for modern browsers that do. It is up to him to make a choice depending on factors such as difficulty, cost, etc. He can contact me directly if he wants to discuss this. Handling this issue via an intermediary in bugzilla is just not efficient.
not fixed as of today. :-(
Blocks: 54458
Whiteboard: [bae:20011126][DOCTYPE] → [bae:20011126][DOCTYPE][TOOL][DYNAPI]
I spoke with Ed @ topozone last week. It doesn't sound like it will be fixed any time soon. Topozone has a browser compatibilty upgrade planned some time in the next couple of months, but they have to do compatibility testing on IE, Opera, whatever the most popular Mac browser is, and a few other broswers besides Mozilla which I hadn't even heard of before thay can implement the DOCTYPE change. --Doug
Thanks for the feedback Doug. Will follow up in Feb. If you hear anything else, please comment the bug. For now you can use NS6.2.1 !
Target Milestone: Jan → Feb
You're welcome, Bob. Looks like Netscape 6.2 it is (until the next branch :-{). --Doug
Whiteboard: [bae:20011126][DOCTYPE][TOOL][DYNAPI] → [bae:20011126][DOCTYPE][TOOL][DYNAPI][aok]
Ed (Ed@topoZone) made a change: Topozone's maps now display properly in Mozilla 0.9.7! --Doug
yay! and they are using dynapi 2!
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verified 2002022703/WinXP
Status: RESOLVED → VERIFIED
modified URL since this happened with other maps.
URL: http://www.topozone.com/map.asp?z=12&... → http://www.topozone.com/
Summary: TOPOZONE doesn't display maps → topozone.com - TOPOZONE doesn't display maps
I believe this one should be closed out. A couple of months ago TopoZone upgraded their system, and maps have been rendering fine with Mozilla since. --Doug
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: