Re: [whatwg] JavaScript dialogs blocking user experience

Darin Adler writes: >> On Apr 14, 2016, at 2:17 PM, Arvind Nigam wrote: >> >> My iPad is on iOS 9.3.1, but I was using the UC browser at the time. > > It’s too bad you were using the UC browser. If you had been using > Safari you would not have been

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 14, 2016, at 2:17 PM, Arvind Nigam wrote: > > My iPad is on iOS 9.3.1, but I was using the UC browser at the time. It’s too bad you were using the UC browser. If you had been using Safari you would not have been trapped by the scam. If you continue to prefer

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 15, 2016, at 9:35 AM, Nils Dagsson Moskopp > wrote: > > Clearly distinguishing between browser chrome and the current document > interface-wise can be helpful here. While it is incredibly easy to fool > people in general, browsers that automagically hide

Re: [whatwg] JavaScript dialogs blocking user experience

Darin Adler writes: >> On Apr 15, 2016, at 9:35 AM, Nils Dagsson Moskopp >> wrote: >> >> Clearly distinguishing between browser chrome and the current document >> interface-wise can be helpful here. While it is incredibly easy to fool >> people

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 15, 2016, at 1:58 PM, Arvind Nigam wrote: > > While I understand your inclination towards Apple Safari, it is out of > question that people won't use other browsers like the Chrome or Firefox or > even the UC browser to surf the web. The problem you

Re: [whatwg] JavaScript dialogs blocking user experience

> It’s too bad you were using the UC browser. If you had been using > Safari you would not have been trapped by the scam. If you continue to > prefer the UC browser over Safari then you should consider how to let > the developers know you would like to see this improved. Oh, I love the Safari,

Re: [whatwg] JavaScript dialogs blocking user experience

> On Apr 15, 2016, at 1:58 PM, Arvind Nigam wrote: > > On mobile the browser goes totally unresponsive and the infinite-loop of > modal confirmations is literally inescapable. I’ll drop this thread after this, but what I wanted to say is this: This extremely bad