FireFox bug in V3

I tried my VE v3 app in FireFox and I got the following error:

Error: [Exception... "'Msn.Drawing.Exception: Your Web browser does not support SVG or VML. Some graphics features may not function properly.' when calling method: [nsIOnReadystatechangeHandler::handleEvent]" nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "<unknown>" data: no]

Any help is appreciated.



Answer this question

FireFox bug in V3

  • Ryan Garaygay

    It appears that the map.Load() function fails. I tried both the ways like:

    map.LoadMap(); // OR
    map.LoadMap(new VELatLong(33.88688993362329, -117.9274606704712), 13, 'r', false);
    I do see the map but my GetMap() function is incomplete that is, it does not execute the rest of my code like adding pushpins, etc. The error is shown in the Javascript Console (under the Tools menu).

    In the status bar I see Firefox downloading a bunch of tiles. For example, it says "Transfering data from r0.ortho.tiles.virtualearth.net..." It's r0 or r1, r2 or r3 for each tile. However, at some point it (the status bar) freezes.

    I appreciate your help.


  • Krad

    Dilipk,

    I encountered the same errors in firebug. Did you resolve the problem I would appreciate help.
    Thanks.

  • Zep--

    I upgraded Firefox to 1.5.0.4 and the it's even worse. Now I get a bunch of error messages as follows:

    Error: Unknown property 'word-wrap'. Declaration dropped.
    Source File: http://local.live.com/css/en/ero.css
    Line: 1

    Error: Unknown property 'behavior'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'text-overflow'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'TEXT-OVERFLOW'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'TEXT-OVERFLOW'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'filter'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'TEXT-OVERFLOW'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'TEXT-OVERFLOW'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'TEXT-OVERFLOW'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'filter'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'filter'. Declaration dropped.
    Source File: http://local.live.com/css/en/api.css
    Line: 1

    Error: Unknown property 'filter'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1

    Error: Error in parsing value for property 'display'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1

    Error: Unknown property 'filter'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1

    Error: Error in parsing value for property 'cursor'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1

    Error: Error in parsing value for property 'cursor'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1

    Error: Error in parsing value for property 'cursor'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1

    Error: Error in parsing value for property 'cursor'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1

    Error: Error in parsing value for property 'cursor'. Declaration dropped.
    Source File: http://local.live.com/css/en/mapcontrol.css
    Line: 1


  • k.Rahul

    Hi all,

    Msn.Drawing.Exception. Your web browser does not support SVG or VML...

    FF 2.0RC2

    any way around

    thx
    Mayah

  • John Lieurance

    Nope, "works for me" means that I get a working map in Firefox with no noticeable problems.

  • Teddy79

    I'm surprised to see that nobody has encountered this bug. (since nobody has replied to this message) Or, probably nobody from Microsoft is monitoring this forum!!!!!!
  • NuclearChicken

    I just tried my app in FireFox and it works very nicely. Are you treating Firefox as an uplevel browser (Assuming you are using .NET)
  • paso

    Thanks for your help. But, it didn't work either. :-(
  • RICH525234

    What do you mean by "treating Firefox as an uplevel browser" Thanks.
  • mobigital

    I'm running FF 2 RC2 and the following works for me:

    try{
    map.LoadMap(new VELatLong(-34.92, 138.59),11,VEMapStyle.Road,false);
    }catch(e){
    //Browser does not support SGV or VML
    }

    Just by adding a try/catch statement around the LoadMap method allows the exception to get caught, but does not stop the execution of the rest of your code. I'm not sure what gets dropped for not supporting SGV or VML, but it seems to be running fine.

  • Dudley

    When you say "works for me" you mean the rest of your JavaScript stuff runs, but you don't get a VE map, right

    Just checking.


  • Yang Tono

    The issue doesn't happen in 1.5. It did in 1.0. However, it also happens in 2.0... Is there another solution

  • rpreston

    The V3 map doesn't work in Firefox < 1.5, so if you have like 1.0.7 it doesn't work with the error you noted. Hope they'll fix it soon. Still alot of people are on < 1.5.
  • ThePope78705

    Those are all just stylesheet errors for things that IE supports, but Firefox doesn't.

    Try adding the following to your web.config's system.web section:

    <browserCaps>

    TagWriter=System.Web.UI.HtmlTextWriter

    </browserCaps>

    By default, .NET treats Firefox as an "old" downlevel browser and emits old HTML syntax. For example, you get tables rather than divs, if you use a .NET Panel control. When you add the above, .NET always emits HTML code appropriate to modern, "uplevel" browsers. There are other ways to do this for specific browsers, but letting .NET control the degradation to IE 4, or some other old browser doesn't seem like a very good idea either. IMHO, you are better off requiring an up-to-date browser and emitting only current HTML.


  • FireFox bug in V3