> 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 experience described here is a
> 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 complained about is fixed in the b
> 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, bu
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 in general, browsers that automagically hide the
> 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 the address bar also
> hide info
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 trapped by the scam. If you continue to
> pre
> 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 the UC
browser over Safari
> The problem you describe above was addressed by Apple in iOS 9.3 and also in
Safari 9.1 on Mac.
My iPad is on iOS 9.3.1, but I was using the UC browser at the time.
I couldn't relocate the exact scamjam page I saw in the morning, but found
this url of a company that supposedly "helps" people fi
> On Apr 14, 2016, at 1:04 PM, Domenic Denicola wrote:
>
> I'm not sure whether this has much of a spec impact. The spec already allows
> great leniency in these areas; e.g.
> https://html.spec.whatwg.org/multipage/webappapis.html#dom-alert step 3 and
> the "optionally" in step 7. If any brows
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of
> The problem you describe above was addressed by Apple in iOS 9.3 and also
> in Safari 9.1 on Mac. That release changed the style of JavaScript alerts so
> that they are less likely to appear to come from Safari, the operating sys
10 matches
Mail list logo
