- From: Arvind Nigam <arvind.nigam@gmail.com>
- Date: Fri, 15 Apr 2016 16:58:04 -0400
- To: Darin Adler <darin@apple.com>
- Cc: "avi@chromium.org" <avi@chromium.org>, "Michael A. Peters" <mpeters@domblogger.net>, WHAT Working Group <whatwg@lists.whatwg.org>, Majid Valipour <majidvp@chromium.org>, Yay295 <yay295@gmail.com>, Domenic Denicola <d@domenic.me>
> 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, but... > "If you had been using Safari you would not have been trapped by the scam. " False dichotomy here? 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 issue:* The original issue that I reported on this thread was to make the top-level functionality of browsers remain "available" during execution of the javascript modal. In other words the controls "back, forward, change tab or close tab" shouldn't be hijackable by a measly modal -- no matter what the intent of a page is; to scam or not is immaterial. *Why so?* Because the annoyance (Unlike as reported on the original mail thread from which this one was forked) on tablets and smartphones is worse than it is on the desktops, where at least the user has an option to shut down or kill the browser by killing a process. On mobile the browser goes totally unresponsive and the infinite-loop of modal confirmations is literally inescapable. You cannot switch tabs, go back or close the window/tab. Closing and re-opening the browser doesn't help either. It only comes back to the same unresponsive state. The only way out then is to delete the browser and reinstall it with clear history. And that's not a pretty picture :-). Cheers, m --- On 15 April 2016 at 11:36, Darin Adler <darin@apple.com> wrote: > > On Apr 14, 2016, at 2:17 PM, Arvind Nigam <arvind.nigam@gmail.com> > 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 the > UC browser over Safari then you should consider how to let the developers > know you would like to see this improved. > > > I'm guessing that this is still a problem for a lot of users out there > > No question about it. The kind of mitigation we are discussing is valuable > to reduce the effectiveness of JavaScript dialogs as part of this, but I’m > sure the folks perpetrating fraud will find new effective ways to do so. > For example, nothing in browser technology can prevent a webpage from > displaying a misleading message that tries to trick you into thinking your > device is broken or was taken over. > > Apple support has a webpage with some advice on this topic that is updated > from time to tome <https://support.apple.com/en-us/HT203987>. > > — Darin
Received on Friday, 15 April 2016 20:58:30 UTC