Seems like that JSBin sample expired as it was on anonymous account. Just created a new one: http://jsbin.com/zidaqa/3
I am able to trigger the focus bug when I run it inside the chrome browser on iOS 8. This is essentially an issue on UIWebView but not on iOS8 Safari. Let me know if you can't reproduce it. On Mon Oct 27 2014 at 5:46:21 PM Daniel Freedman <[email protected]> wrote: > Hey Akhilesh. > > I've been playing with your example and I can't seem to trigger the focus > bug on iOS 8. Are you only seeing this on iOS 7? > > On Fri, Oct 24, 2014 at 10:56 AM, Akhilesh <[email protected]> > wrote: > >> Thanks Daniel. Let me know once you have something that I can play with. >> >> On Thu, Oct 23, 2014 at 6:19 PM, Daniel Freedman <[email protected]> >> wrote: >> >>> Yeah this seems like a pretty valid use case to fix in the gesture >>> system. I'll investigate this for the next release. >>> On Oct 22, 2014 9:19 AM, "Akhilesh" <[email protected]> wrote: >>> >>>> Apologies for delayed response. Was kind of heads down with the >>>> Dreamforce prep and polymer demos, which were just awesome! >>>> >>>> Coming back to the preventDefault problem, I was able to create a >>>> simple sample that shows the issue. Try this link on Chrome on iOS: >>>> http://jsbin.com/mogusutono >>>> Source: http://jsbin.com/mogusutono/edit?html >>>> >>>> When you click the button, the view navigates to next page with the >>>> paper-input element. And on the next page, paper-input automatically >>>> receives a focus event and and keyboard pops up. Not ideal. I am able to >>>> work-around this by listening for touch-end event after the tap and then >>>> calling event.preventDefault. Would be better if tap event could handle >>>> this automatically for me. This also seems to only happen inside the >>>> UIWebView and not the iOS Safari. >>>> >>>> Let me know if you guys need more details. Hope this helps! >>>> >>>> On Thu, Oct 2, 2014 at 9:59 AM, Steve Orvell <[email protected]> >>>> wrote: >>>> >>>>> Hey Akhilesh, >>>>> >>>>> Can you outline why you'd like to prevent clicks? Is it because some >>>>> other user code may have installed a click listener you want to avoid or >>>>> is >>>>> it some native platform action (e.g. following a link) that you want to >>>>> abort? >>>>> >>>>> It would be great if you could just preventDefault in the tap event, >>>>> unfortunately, tap is generated separately from click and is typically >>>>> fired after it. >>>>> >>>>> As Daniel mentioned, we're investigating providing a relatively easy >>>>> way to do this in PolymerGestures. >>>>> >>>>> On Thu, Oct 2, 2014 at 8:57 AM, 'Daniel Freedman' via Polymer < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Akhilesh >>>>>> >>>>>> We don't currently have a strategy to prevent clicks. I can take a >>>>>> look at what that would entail. >>>>>> >>>>>> Touch-action is only supposed to control scrolling and zoom, so >>>>>> making the "none" value control clicks as well is a little outside the >>>>>> intended scope. >>>>>> >>>>>> What you can do for now is place a document wide, capturing click >>>>>> listener that calls stopPropagation inside the "up" event handler, and >>>>>> then >>>>>> remove that click handler when a click happens, or after a timeout. This >>>>>> is >>>>>> the approach I am planning to evaluate. >>>>>> I have been trying to figure out an easier way to prevent click >>>>>> events from an element that listens for tap. This is more of an issue on >>>>>> touch devices (iOS in particular). Here's an example: >>>>>> http://jsbin.com/totuhoveguke/2/edit >>>>>> >>>>>> One solution is to attach another listener for touchend and then do >>>>>> event.preventDefault(). This causes weird side-effects which I want to >>>>>> avoid. Ideally my assumption was that when I am using touch-action = >>>>>> "none", I will be able to avoid all default browser events. >>>>>> >>>>>> What's the best solution for such cases? >>>>>> >>>>>> >>>>>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Polymer" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/polymer-dev/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/polymer-dev/6f3bb3d1-52cb-4b89-9424-2cfdec3139f2%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>>>>> --- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Polymer" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/polymer-dev/CAAUAVAgfxq6JQDX%2Bev%2BPtbuo48a2D780rZLP2VpQ_AJBujUxEQ%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/polymer-dev/CAAUAVAgfxq6JQDX%2Bev%2BPtbuo48a2D780rZLP2VpQ_AJBujUxEQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> >>>> >> > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAJGcB39sRG36%2Bduoqki4as_eOTWohL183Ntc%3DX9jk40vMhHW8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
