746050 - FF won't display an interactive map that IE and SeaMonkey will display

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[SeaBuggy]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120312181643

Steps to reproduce:

I visited the webpage: http://efa.mvv-muenchen.de/mvv/XSLT_TRIP_REQUEST2?sessionID=0&language=en&ptOptionsActive=0&execInst=normal&placeInfo_origin=invalid&nameInfo_origin=invalid&typeInfo_origin=invalid&target_url=%2Fstatic_languages%2Fen%2Fhome%2Ftimetable%2Fjourneyplanner%2Findex.html&placeInfo_destination=invalid&nameInfo_destination=invalid&typeInfo_destination=invalid&requestID=0&command=&itdLPxx_help=&itOptionsActive=&hiddendate=&type_origin=any&type_destination=any&anySigWhenPerfectNoOtherMatches=1&anyObjFilter_origin=0&stateless=1&name_origin=hauptbahnhof&name_destination=bavariafilmstadt&itdTimeHour=03&itdTimeMinute=19&itdDateDay=16&itdDateMonth=04&x=26&y=5#outputMapAnchor_1



Actual results:

When I clicked on "Interactive Map", the correct background map of Munich displays below, but the colored, interactive path of the planned journey via metro (U-bahn & strassenbahn, in this case) in the city of Munich does not display superimposed on the background map.


Expected results:

The map should have had a multicolored path traced superimposed over the background map of the city.  The path is interactive, in that one can click at any point on the colored path to obtain information about the journey across town.  I verified that the website is working, by putting the above URL into the address fields of both IE8 and SeaMonkey 2.8 and obtaining the correctly displayed maps in both browsers.

Comment 1

[Romain DEP.]

Works here.

Comment 2

[Andre Klapper]

Works fine here too in Firefox 11.0 on Fedora 16.
Can you please try in safe mode with a fresh account without extensions/add-ons?

Comment 3

[SeaBuggy]

The problem has disappeared when I use FF 16.0.2.  I apologize for taking so long to check this out.  When the two comments reported that it worked for them, I assumed that was it, and that I just had some local problem.