Weird Behavior With asp.net 3.5 Menu Server Control

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Joey

    Weird Behavior With asp.net 3.5 Menu Server Control

    VS2008
    C#

    Hey guys, something crazy is going on when I try to view my website
    with either Google Chrome or Apple Safari. For some reason the web
    server is sending extra markup to the site's navigation menu
    (generated off a Menu server control).

    You can see what I'm talking about if you use either of these browsers
    and visit the live site...

    This domain has a pending ICANN verification and is suspended.


    ....look at the yellow navigation menu in the upper right corner.

    Any ideas about what's causing this? How can I fix it?

    Thanks!
  • =?Utf-8?B?YnJ1Y2UgYmFya2Vy?=

    #2
    RE: Weird Behavior With asp.net 3.5 Menu Server Control

    this a common problem with the asp.net controls. they count on a properly
    maintained browsers cap file to know what html to render. you need to update
    this file, so that chrome and safari are known to be w3c compliant.

    google browsercap for solutionsi. I stopped using any server control that
    count on it long ago to avoid this issue.

    -- bruce (sqlwork.com)


    "Joey" wrote:
    VS2008
    C#
    >
    Hey guys, something crazy is going on when I try to view my website
    with either Google Chrome or Apple Safari. For some reason the web
    server is sending extra markup to the site's navigation menu
    (generated off a Menu server control).
    >
    You can see what I'm talking about if you use either of these browsers
    and visit the live site...
    >
    This domain has a pending ICANN verification and is suspended.

    >
    ....look at the yellow navigation menu in the upper right corner.
    >
    Any ideas about what's causing this? How can I fix it?
    >
    Thanks!
    >

    Comment

    • Joey

      #3
      Re: Weird Behavior With asp.net 3.5 Menu Server Control

      On Nov 11, 10:31 am, bruce barker
      <brucebar...@di scussions.micro soft.comwrote:
      this a common problem  with the asp.net controls. they count on a properly
      maintained browsers cap file to know what html to render. you need to update
      this file, so that chrome and safari are known to be w3c compliant.
      >
      google browsercap for solutionsi.  I stopped using any server control that
      count on it long ago to avoid this issue.
      >
      -- bruce (sqlwork.com)
      >
      "Joey" wrote:
      VS2008
      C#
      >
      Hey guys, something crazy is going on when I try to view my website
      with either Google Chrome or Apple Safari. For some reason the web
      server is sending extra markup to the site's navigation menu
      (generated off a Menu server control).
      >
      You can see what I'm talking about if you use either of these browsers
      and visit the live site...
      >>
      ....look at the yellow navigation menu in the upper right corner.
      >
      Any ideas about what's causing this? How can I fix it?
      >
      Thanks!
      Thanks, Bruce. I found a cumbersome, but effective solution. I handled
      each page's Pre_Init event and use the following code...

      if((this.Reques t.ServerVariabl es["http_user_agen t"].ToString().Con tains("Chrome") )
      ||
      (this.Request.S erverVariables["http_user_agen t"].ToString().Con tains("Safari") ))
      { this.Page.Clien tTarget = "uplevel"; }

      Works like a champ (for now).

      Thanks,
      JP

      Comment

      • Mark Rae [MVP]

        #4
        Re: Weird Behavior With asp.net 3.5 Menu Server Control

        "Joey" <joey.powell@to pscene.comwrote in message
        news:e0c9fa38-e8fe-4ad3-81fd-27dc4f2e4bae@z2 8g2000prd.googl egroups.com...
        >This a common problem with the ASP.NET controls. They count on a properly
        >maintained browsers cap file to know what HTML to render. You need to
        >update
        >this file, so that Chrome and Safari are known to be w3c compliant.
        >>
        >Google browsercap for solutions. I stopped using any server controls that
        >count on it long ago to avoid this issue.
        >
        Thanks, Bruce. I found a cumbersome, but effective solution. I handled
        each page's Pre_Init event and use the following code...
        >
        if((this.Reques t.ServerVariabl es["http_user_agen t"].ToString().Con tains("Chrome") )
        ||
        (this.Request.S erverVariables["http_user_agen t"].ToString().Con tains("Safari") ))
        { this.Page.Clien tTarget = "uplevel"; }
        AAMOI, simpler solutions in terms of maintainability would be either to
        create a base class which inherits from Page and give it the above method
        and then get all your other pages to inherit from it, or use a MasterPage /
        content pages architecture...


        --
        Mark Rae
        ASP.NET MVP


        Comment

        • Joey

          #5
          Re: Weird Behavior With asp.net 3.5 Menu Server Control

          On Nov 11, 12:12 pm, "Mark Rae [MVP]" <m...@markNOSPA Mrae.netwrote:
          "Joey" <joey.pow...@to pscene.comwrote in message
          >
          news:e0c9fa38-e8fe-4ad3-81fd-27dc4f2e4bae@z2 8g2000prd.googl egroups.com...
          >
          This a common problem with the ASP.NET controls. They count on a properly
          maintained browsers cap file to know what HTML to render. You need to
          update
          this file, so that Chrome and Safari are known to be w3c compliant.
          >
          Google browsercap for solutions. I stopped using any server controls that
          count on it long ago to avoid this issue.
          >
          Thanks, Bruce. I found a cumbersome, but effective solution. I handled
          each page's Pre_Init event and use the following code...
          >
          if((this.Reques t.ServerVariabl es["http_user_agen t"].ToString().Con tains("Ch rome"))
          ||
          (this.Request.S erverVariables["http_user_agen t"].ToString().Con tains("Safar i")))
          { this.Page.Clien tTarget = "uplevel"; }
          >
          AAMOI, simpler solutions in terms of maintainability would be either to
          create a base class which inherits from Page and give it the above method
          and then get all your other pages to inherit from it, or use a MasterPage/
          content pages architecture...
          >
          --
          Mark Rae
          ASP.NET MVPhttp://www.markrae.net
          I also thought that. The source stated that it would not work with
          master pages.

          Comment

          • Mark Rae [MVP]

            #6
            Re: Weird Behavior With asp.net 3.5 Menu Server Control

            "Joey" <joey.powell@to pscene.comwrote in message
            news:6a4de800-1b7c-4157-8a6c-534a000164b0@x1 6g2000prn.googl egroups.com...
            >AAMOI, simpler solutions in terms of maintainability would be either to
            >create a base class which inherits from Page and give it the above method
            >and then get all your other pages to inherit from it, or use a MasterPage
            >/
            >content pages architecture...
            >
            I also thought that. The source stated that it would not work with
            master pages.
            It does:
            สล็อตเว็บตรง API แท้ ไม่ผ่านเอเย่นต์ เว็บสล็อตใหม่ล่าสุด ฝากถอนง่าย ผ่านทุกธนาคารในไทย เว็บตรง 100% เบทน้อยเล่นได้ ทุกที่ทุกเวลา



            --
            Mark Rae
            ASP.NET MVP


            Comment

            Working...