I talked with Adobe support in India about this. They stated that this was a new error and that a technical supervisor would contact me.  It apparently works on Safari but not IE8 or IE9.

Version 2 wasn't released yesterday, so it makes sense that I am doing something incorrectly, but I cannot figure out what it is.

I will let you know what they find out.

Gramps,

I checked my .htaccess file.  It contains four lines, but none of them refer to a charset so I am not sure what I should do.

You had also suggested that I try the following in a different forum thread.

>> In the meantime have a look at the JS and ask yourself why you left

enableHoverNavigation: true,

>>  when a touch screen does not recognise a hover event. Normally one would leave the JS file in tact and change the value in the constructor.

I do see this line in the SpryMenu.js code but I have have not altered the code.  This code is straight from Adobe/Spry's 1.7 version which has a widget that builds the code.

Just to clarify what you said to Gail, I believe that Spry 1.7 does provide a good user experience for iPad users as Gail could see from the sample code that I provided in my link, but the IE8 and IE9 problems remain.

I certainly don't have the expertise that you have.  If I need to look in a different place for an .htaccess file, please let me know.

Thanks,

Scott

Gramps,

I appreciate you providing this.  I took a closer look at the errors and I made a few changes but this validator service continued to kick out errors.  In fact if you put Adobe's own web site into this application (http://www.adobe.com), it comes up with 44 errors.  As I mentioned before, the Adobe Widget Browser application for Spry Menubar 2 is essentially creating my code so I doubted that this was an actual problem.

While I have been interacting with you, I have also been awaiting an update from Adobe's senior technology staff for a solution.  I heard from them today.  Here is what Adobe said:  Spry Menubar 2 has problems with IE 8 and IE 9 (which I already knew).  The first person with whom I spoke at Adobe suggested that my customers running the IE 8 and IE 9 browsers should switch to a different browser, such as Chrome.  I explained that asking users to switch was not a solution -- that's about 35% of my users.  I then asked to speak with a manager / supervisor. 

My conversation with the supervisor went a bit better.  He told me that those running IE 8 and IE 9 on a Windows XP machine are ok.  Vista is a problem.  Windows 7 is also iffy.  My machine is a Vista and my wife's machine is a Windows 7.  It does not work on either machine for us.

I told him that Spry Menubar 2 should be withdrawn from their site or there should be a warning to insure that people are aware of the problems.  He didn't say that they would do that.  He suggested that I should check back with him in a couple of weeks.  I did not get a warm and fuzzy feeling that this was a priority item for them.

At this point, I'm bailing on Spry Menubar 2.  I may return to Spry Menubar 1.6 which requires a "double tap" on the nav buttons to work on an iPad.  I may also check out jQuery.

Thanks for the suggestions but it looks like Adobe has some serious issues.  If your customers are using iPads (and they are), Spry Menubar 2 is not a solution to fix the problems encountered in Spry 1.4 and Spry 1.6.

Scott