3 ms·
I'm sure its nice on a desktop, but it's unusable on a phone. It's probably not your intended audience, so good effort nonetheless. I think in the not-to-dista
by jbail 15y ago
I'm sure its nice on a desktop, but it's unusable on a phone. It's probably not your intended audience, so good effort nonetheless.
I think in the not-to-distant-future, especially as mobile browsing overtakes desktop browsing, its going to be a prerequisite that plugins/widgets work on both screens. As people evaluate whether or not to use a plugin, this will quickly become a deciding factor.
Again, not a critique of this plugin. Just a thought I had while looking at this and being kind of sad that I couldn't really experience the demos on my phone.
- fletchowns 15y agoSeems to work fine on my iPhone?
- johnbender 15y agoI hate to harp on you here because you're clearly just attempting to help, but I think the statement > Seems to work fine on [the] iPhone? is representative of the main issue with the mobile web. Most people only build with iOS and maybe Android in mind. Thankfully Android's browser is bad enough that it's raised awareness of how difficult it is to build complex cross platform web applications.
- greybeardedgeek 15y agoWorks fine on my Android phone's stock browser...
- hrabago 15y agoOn my iPhone, it doesn't work as well. Yes, the dropdown selections show up, but the keyboard pops up as well, and on top of the selections, so unless you know that the selections are there, you won't even notice them.
- heyjonboy 15y agoVery true, mobile wasn't really taken into consideration with this plugin. One option would be to use a <select> dropdown as the element you attach $.timepicker() to, and only initialize the timepicker for certain screen sizes. Other screens would see the default <select> element, which works better on mobile devices.