Great thanks - I'll watch the video a bit later. So it should be "like Facebook did with Konqueror: clearly they use bad stupid browser sniffing)." lawlz *edit looks like they finally added KHTML to their desktop list. I would not try to do content-negotiation based on user agent, as browsers lie and you wouldn't want to hit any desktops by accident (like Facebook does with Konqueror: clearly they use bad stupid browser sniffing). That link should be somewhere in the vicinity of the dropdown so users notice it. If it's just the dropdowns of the site that are making trouble for touch devices, then instead of a whole mobile site, just a link for the sitemap page should be enough.
I figure any site with deep menus should also already have a sitemap-style page, showing the relationship between the links like the dropdown does except without stuff hiding/reappearing. The other option is to put a layer of JS over your already-working dropdown that uses click events to do slightly other things, but I'm also leery of making a mobile (who is likely using G3 or some lesser network or are leeching off some cafe's wireless internet or whatever) load a bunch of scripts, which they will try to do if they are available (plus page loading stops until the scripts are loaded).ĭropdowns already have some basic usability issues with them even without touch taken into account. You might want to consider making a mobile version of your site (without dropdowns but plain links like a sitemap) and offer a link to that page near the top, so users of any kind of funky touch mobile can choose to go there instead of playing with the dropdowns. to find where the relevant area starts.Įven though he's talking about Javascript events, the parts about mobiles is interesting and useful. Unfortunately Yahoo just splooooeooeeegs all the text on the page, but you can /Device independence. Maybe there should be a "mobile" forum for these kind of questions? I can't figure out the best appraoch to do this though. I'm guessing though that if that happened the finger would obscure the content anyway. The only option to me then is to disable the hover on touchscreens as it serves no use unless it can be shown when the finger is just touching it. I could make it so that the click is disabled so the inner page isn't reached but that page is actually needed. I'm a bit stuck on what the best practice here would be. If I tap, it triggers the :hover but then goes to the page anyway meaning a quick glimpse of the flyout and then it disapears quickly as the page changes. On the iphone (only mobile device I have a the moment) if I hover over the menu with my finger nothing happens. If they click the top level menu, they go to a page that has the links that would be in the menu. If someone hovers over the top level menu, they see the flyouts.