You might find this article interesting:

http://www.projectseven.com/products/menusystems/pmm2/ug-examples/acce ssible/index.htm

Where can we download Spry 2.0?!?!

Hi:

I was using the Spry Menu which shipped with DW CS4 and noticed nested links would not work on mobile Safari (iPhone, iPod, iPad).  I found the newer version and gave that a try:
// SpryMenu.js - version 0.19 - Spry Pre-Release 1.7

This works better, but there is still some issue.  I need to click on a nested menu item twice in order for it to register on mobile Safari.  If I have 2 nested menu items in a horizontal menu bar... I can also notice the following:
Click on item1, then item2, then item1, then item2.. you will never get anywhere.   BUT.. click on either of them twice in a row and it works.

I am guessing this can be fixed with an edit to the JavaScript somewhere inside the menu code.  Does anyone know which part will handle this so I can modify before an official change gets released (assuming one does which resolves this issue)?

Thanks!

Hi:

That is the one I am using... I got the latest version from the widget browser.  Any other suggestions?

Thanks!

Hi

I can confirm that I have created a menu using the widget browser and it works fine on my iPhone. The trick is knowing how to get the drop-down menu to appear. I discovered that I had to just gently hold my finger on the top level menu for a short time and the sub-menu will appear.

This is good news and I will now have to apply this to all my Spry menus out there.
Thanks to the Spry Team for the Widget Browser - That can save quite a bit of time - wish I could find all the examples and docs for the new version though......

Cheers

Thanks. I noticed the same problem. I've removed the extra code from my html page and the drop-down menu works perfectly on a touch screen. One click activates the drop-down and a second activates the link.

The fix

Instead of

var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetClass: "MenuBar  MenuBarLeftShrink",
      });

Use

var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
      widgetClass: "MenuBar  MenuBarLeftShrink",
      insertMenuBarBreak: true,
      });

I have tested in all major browsers on Mac, PC and iPhone and all seems ok.

Hi:

I had it working just fine in IE with what I had.  The only thing which doesn't work are my round corners (not supported in IE CSS) and the menu seems to float over the next float even though it is cleared.  Making the change you suggested does not do anything different for me.  My CSS worked fine in IE except for the above.

Thanks.

Do you have links on the top level items? If so, they will need to be replaced with just #. This seems to allow the menu option to contain a link and therefore use the css properties, but does not take the user away from the page.

This worked for me on a site - http://www.rosshandling.co.uk

I put together a test page using a menu created in the Spry widget jigger.

I found that if I gently touch the top level menu for a short time and lift off, the second level menu appears   It takes about a second or less to achieve this otherwise on the iPhone a menu is presented with options to Open, Open in a new Page, Copy or Cancel.

Try www.intellinet.com.au/spry/

Hi

Are you using all the required css files ??

In my case, I eventually gave up on Spry and moved to jQuery/superfish. A far better choice.

Good luck.

css files - not fields.

To produce a spry menu you need both the required js file and css files.

If you have not yet done so, I suggest that you use the Adobe Widget Browser to generate a menu identical to what you need and save the created files then use that as a template for your site.

I don't agree at all that this question is answered (properly)!

A drop down menu fully compatible with iPad and other touch devices should offer the possibility to also have a link in the top level menu entry!

I've seen this already on various sites: First click shows the menu, second click goes to the top level menu entry link.

So if someone has a patch for this (not really) great Spry2.0 Menu to allow this, THEN the answer will be answered.

Thank you for the reply.

Here's one site example: http://nwneighborhoodvet.com/

Yes, I realize that and that is what I outlined/explained in this forum. I am using the 2.0 widget and it produces the same 1.6.1 version of the js file. Where should be getting a different js file?

thanks

Thanks for your answers.

Looks like the browser on iPad simulator doesn't behave like the real touch device, because on iPad itself definitely all unmodified Spry 2.0 menus and also that example ( http://nwneighborhoodvet.com/ ) don't work properly. When I touch "About Us" on http://nwneighborhoodvet.com/, then it immediately loads http://nwneighborhoodvet.com/pages/about-us.html instead of displaying the drop down menu.

Somehow I also don't understand your versioning scheme. I downloaded today again the so called Spry 2.0 Dropdown Menu with the Widget Browser and when I install it on my site the directory with the CSS and Javascripts inside is called Spry-UI-1.7. When this is supposed to be Spry 2.0, why don't you call it Spry-UI-2.7 or 2.0.7 or something similar? Or do I get the wrong version from that strange Widget Browser/Dreamweaver CS5?

My test page (should be unmodified and it's not formatted properly at the moment) is http://www.safeexambrowser.org/Templates/main-D.dwt, also doesn't work properly on iPad.

This is a example (jQuery Superfish) which is actually working on iPad: http://users.tpg.com.au/j_birch/plugins/superfish/#examples (see the menu below "The result:".

Hi,

The simulator behaves exactly the same the regular iPad, ( I just tested it on my iPad 3G, latest firmware and my iPad Wifi with origional firmware ).

About the version scheme, the 2.0 is the widget's version. But it uses Spry UI 1.7 as core JavaScript framework. But I didn't make up the versioning, I'm just a humble Spry user .

As for my testing I was testing: http://labs.adobe.com/technologies/spry/ui/samples/MenuBar2Sample.html which didn't have a url as top level item, just a single hash. And that worked fine, after modifing my local version of Spry I was able to reproduce the issue.

It's probably fixable, with a few simple tweaks to the JavaScript files but I wonder what would be the adviced pattern than. If you have a touch enabled device the first "click" on the element, if no submenu is toggled should trigger the submenu. And if you click again on the element it would activate the <a> element?

So, I'm still wondering where I am to get the 2.0 version.

Thank you.