4 ms·

There is no reason that I can think of that just because Mobile Safari uses tap and hold for some functions, that it couldn't pass it along to Flash when perfor

There is no reason that I can think of that just because Mobile Safari uses tap and hold for some functions, that it couldn't pass it along to Flash when performed on a Flash element.

tvon 17y ago
Well, then you'd have to expect the user to know what is a Flash element and what isn't.
- boucher 17y ago
  any element can prevent the default action at any time. flash, or not flash, it's like two lines of javascript.
  - glhaynes 17y ago
    What do you mean? I don't recall ever using Safari on iPhone and having tap-and-hold not do the Safari default thing (pop up contextually-dependent menus giving choices like "Copy" and "Open in New Window" for links, "Save" and "Copy" for images, etc) and don't think that JavaScript has access to that.
    - Zev 17y ago
      The closest thing that I can think of is -webkit-user-select, although I'm not sure if thats available on the iPhone. Nor would it let you change UIMenuController behavior. I suspect that if it is possible, it would be under an NDA. That is, after all, how these things seem to work. Would love to be wrong though. Alternate, Occams Razor take: Apple just hardcodes the options, based on the type of object that is selected.
  - deleted 17y ago
    [deleted]
  - tvon 17y ago
    A user would still have to understand why trying to grab+drag to scroll would work on one part of a page but inexplicably not on another part (eg, a Flash ad). Most likely it would be a crap shoot between pages that took the iPhone/iPad into account, and those that would confusingly not work.
- slillibri 17y ago
  No, I would expect the software to know what is a Flash element and what isn't. I would also expect the software to make it easy for the user to know one from the other and see the behavior is different.
Zev 17y ago
Changing defaults around means that you're forcing people to learn new behavior specifically for your site. Not a particularly user-friendly thing to do. And in Safari, doing this would raise even more confusion; the default behavior works in other parts of the app (the next tab over, for example) but not the tab for your site. It is easy to see a user getting confused as to why something isn't working for one particular site. Maybe they want to copy text from a flash element, but it ends up doing something completely different.

There is no reason that I can think of that just because Mobile Safari uses tap and hold for some functions, that it couldn't pass it along to Flash when performed on a Flash element.

tvon 17y ago

Well, then you'd have to expect the user to know what is a Flash element and what isn't.

boucher 17y ago
any element can prevent the default action at any time. flash, or not flash, it's like two lines of javascript.
- glhaynes 17y ago
  What do you mean? I don't recall ever using Safari on iPhone and having tap-and-hold not do the Safari default thing (pop up contextually-dependent menus giving choices like "Copy" and "Open in New Window" for links, "Save" and "Copy" for images, etc) and don't think that JavaScript has access to that.
  - Zev 17y ago
    The closest thing that I can think of is -webkit-user-select, although I'm not sure if thats available on the iPhone. Nor would it let you change UIMenuController behavior. I suspect that if it is possible, it would be under an NDA. That is, after all, how these things seem to work. Would love to be wrong though. Alternate, Occams Razor take: Apple just hardcodes the options, based on the type of object that is selected.
- deleted 17y ago
  [deleted]
- tvon 17y ago
  A user would still have to understand why trying to grab+drag to scroll would work on one part of a page but inexplicably not on another part (eg, a Flash ad). Most likely it would be a crap shoot between pages that took the iPhone/iPad into account, and those that would confusingly not work.
slillibri 17y ago
No, I would expect the software to know what is a Flash element and what isn't. I would also expect the software to make it easy for the user to know one from the other and see the behavior is different.

Zev 17y ago

Changing defaults around means that you're forcing people to learn new behavior specifically for your site. Not a particularly user-friendly thing to do. And in Safari, doing this would raise even more confusion; the default behavior works in other parts of the app (the next tab over, for example) but not the tab for your site. It is easy to see a user getting confused as to why something isn't working for one particular site. Maybe they want to copy text from a flash element, but it ends up doing something completely different.