Menus in Chrome, Ch 7 p244-

Alanrf · February 1st, 2010, 08:05 AM

Hi Imar,

I've just stumbled across something of an oddity with menus in Chrome. The issue was raised on the Forum under Styling the Menu Control in March 2009. Your final post to that thread, 17 March 2009 mentioned a possible solution at http://blog.the-dargans.co.uk/2008/0...work-with.html

I was interested in this but have also had a further look around on Google. There seems to be an interesting, (better??), solution (in a contribution dated 10-29-2008, 11:14 PM) at,

http://forums.asp.net/p/1315088/2713325.aspx

which offers some code to insert in the BrowserFile browser script. Having tried this out, after creating App_Browsers and generating BrowserFile.browser, it does seem to work OK.

However, I would be interested to know your views. Is this a 'better' solution, or have you any suggestions for inserting some code in one of the existing pages.

Just as a reminder, the line

Home Reviews About Login

appears as:

Home Reviews Expand Reviews About Expand About Login

Apologies for intruding upon your limited time.

Imar · February 2nd, 2010, 07:02 AM

Hi Alan,

In the thread you linked to, a few different solutions and links are mentioned. Which one are you referring to?

Imar

Alanrf · February 2nd, 2010, 07:18 AM

Hi Imar,

Apologies for the omission. I had realised my carelessness about an hour ago so perhaps there is some form of mental telpathy here.

However the particular 'solution' was posted by cnobles on October 29 2008, (the ninth post down), as follows:

Code:

 
<browsers>
  <!-- Disable the Menu Adapter for the Safari browser without changing the root browser file -->
  <browser refID="Safari1Plus">
    <controlAdapters>
      <adapter controlType="System.Web.UI.WebControls.Menu"
               adapterType="" />
    </controlAdapters>
  </browser>
</browsers>

Imar · February 3rd, 2010, 03:30 PM

Hi Alan,

Sorry fior the late reply; had to test this out before I could post back.

This seems like a good solution to me to work around this issue. What I like about it is that it gives you fine-grained control over how you override settings. So, if another issue comes up, you can define another control inside the Browser file. And so far, I haven't been able to see anything "wrong" with this.

FYI: the menu of ASP.NET 4 works fine in Google and doesn't require special handling.

Cheers,

Imar

Alanrf · February 4th, 2010, 08:21 AM

Hi Imar,
Thanks for your response. It is encouraging to know that the idea is 'acceptable'. I can see your point that this might be a way to handle any possible browser issues as well.

chroniclemaster1 · May 14th, 2010, 02:28 PM

Any sense of why the version change eliminated the Chrome issue? I don't have 4.0 yet, and can't see what the XHTML or CSS look like? I'm assuming there's been some change?

Imar · May 15th, 2010, 03:49 AM

They made changes to the browsers they recognize and made changes to the HTML the controls emit.

Check out www.planetwrox.com and look at the differences in source for the 3.5 and 4.0 versions of the site.

Cheers,

Imar

chroniclemaster1 · May 16th, 2010, 10:50 PM

Interesting. There are some marked improvements in the CSS rendered in the document head. It's still there, which isn't best practice, but the selectors they're using to target elements on the page is MUCH more natural.

Imar · May 17th, 2010, 01:58 AM

Quote:

There are some marked improvements in the CSS rendered in the document head. It's still there, which isn't best practice,

In-line CSS isn't necessarily a bad practice though. But you can now turn it off completely: http://msdn.microsoft.com/en-us/libr...tyleblock.aspx

Cheers,

Imar

chroniclemaster1 · May 17th, 2010, 01:37 PM

Quote:

Originally Posted by Imar

In-line CSS isn't necessarily a bad practice though. But you can now turn it off completely: http://msdn.microsoft.com/en-us/libr...tyleblock.aspx

Cheers,

Imar

Agreed, in fact when I'm working with jQuery, that's something I'll do since most JS support typically implies a browser that's capable of and configured for CSS. It's also more sensible if you have a style for one page, just embed it and keep the bloat out of the stylesheets.

Though all other things being equal, I still prefer to insert, remove, or swap classes in jQuery, just so all of my style rules are in the stylesheet. I like having everything in one place and knowing where to go during the maintenance (or construction) cycles.