Quoting "SULLIVAN, BRYAN L (ATTCINW)" <[email protected]>:
Marcos,
That method works for well-know URI schemes except for http:// and
https://. The openURL() method would have launched the browser for
those schemes, and we still need a method to do that.
No. We dont. Please see my proposal.
I was not able to attend the last week's call and was not aware
there was a plan to remove the openURL() method. This leaves a major
hole in the functionality we need from
Major hole? No one has yet presented a single use case that could not
be done with an a element.
the Widgets specs (ability to
launch the browser when necessary/desirable, which is something only
known by the widget - e.g. it needs to invoke a resource that it
knows needs to be handled through the browser or other registered
URI scheme handler).
See my proposal. Its not needed.
Thanks,
Bryan Sullivan | AT&T
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Marcos Caceres
Sent: Friday, August 06, 2010 8:56 AM
To: Web Applications Working Group WG
Subject: Re: ACTION-568: Create an alternative mechanism for openURL
and send it to the mail list (Web Applications Working Group)
On 8/5/10 3:30 PM, Web Applications Working Group Issue Tracker wrote:
ACTION-568: Create an alternative mechanism for openURL and send it
to the mail list (Web Applications Working Group)
http://www.w3.org/2008/webapps/track/actions/568
On: Marcos Caceres
Due: 2010-08-12
If you do not want to be notified on new action items for this
group, please update your settings at:
http://www.w3.org/2008/webapps/track/users/39125#settings
The proposal is simply to use HTML <a> element.
So, instead of:
widget.openURL("sms:+123456789101112");
It would just be:
<a href="sms:+123456789101112">Send and SMS</a>
Then you can use the .click() element to open links programmatically (on
trusted URI types) or only respond to explicit user interaction (the
user clicks on the link to do something).
Kind regards,
Marcos
--
Marcos Caceres
Opera Software
