Paul Straw

We're here. Sorry about the delays, things have been very busy on our end. Have you tested your fix on iOS/Android?

FancySelect only styles the trigger in mobile browsers; it displays the browser-native UI. I'm not sure if there's a great way around this; I'd have to look into detecting "fake"...

Personally, I'm a big fan of http://browserstack.com/ :)

Which IE versions are you seeing this in?

These diffs look like pretty much everything has changed; it's pretty difficult to figure out what's going on. Can you explain in a bit more detail?

This is actually supposed to be be the behavior on mobile (styled button, system dropdown). Looks like it might be a regression; I'll have to check it out.

I was also running into this problem. Downgrading to yup-phone 1.2.12 (or even 1.2.8) didn't solve my issue. I believe the root cause here is [the way npm handles caret...

@diego06884 as noted in my previous comment, you need to use the same yup minor version as the minor version specified in yup-phone. In your example of yup-phone `1.2.12`, [that...

Absolutely! A nice demo is 100% on my list, but in the meantime, here's this lame test bed I used while developing it: http://preview.octopuscreative.com/sundial/

Thanks for considering this. The name would also be nice, because otherwise all the cards on device will still be indistinguishable by eye.