Hi Rich,
On Fri, Jun 10, 2011 at 12:09 AM, Rich Tibbett rich.tibb...@gmail.com wrote:
On Thu, Jun 9, 2011 at 1:29 PM, Marcos Caceres marcosscace...@gmail.com
wrote:
Hi,
The current widget URI spec does not work with XHR and hence can't be
used with popular JS libraries like JQuery Mobile.
Le 9 juin 2011 à 19:09, Rich Tibbett a écrit :
Are there are any plans to undertake a Provisional (or Permanent) URI
Scheme Registration for the widget URI? [1]
Usually a scheme should be used for identifying a new protocol.
(I know that it has been used for different reasons too).
What are
On Fri, Jun 10, 2011 at 11:03 AM, Karl Dubost ka...@opera.com wrote:
Le 9 juin 2011 à 19:09, Rich Tibbett a écrit :
Are there are any plans to undertake a Provisional (or Permanent) URI
Scheme Registration for the widget URI? [1]
Usually a scheme should be used for identifying a new
On Jun/10/2011 6:14 AM, ext Karl Dubost wrote:
Le 10 juin 2011 à 06:10, Marcos Caceres a écrit :
What are the benefits of having a different scheme?
I'm confused... different to what?
:) http
FYI, some of that info was consolidated in:
http://www.w3.org/2008/webapps/wiki/WidgetURIScheme
On Fri, Jun 10, 2011 at 11:14 AM, Karl Dubost ka...@opera.com wrote:
Le 10 juin 2011 à 06:10, Marcos Caceres a écrit :
What are the benefits of having a different scheme?
I'm confused... different to what?
:) http
http://www.w3.org/2008/webapps/wiki/WidgetURIScheme#http:_URI_Scheme
--
Hi,
The current widget URI spec does not work with XHR and hence can't be
used with popular JS libraries like JQuery Mobile. This makes the URI
scheme basically useless for a massive number of use cases.
To fix it, the widget URI spec needs to respond with HTTP responses
when a URI is
On Thu, Jun 9, 2011 at 1:29 PM, Marcos Caceres marcosscace...@gmail.com wrote:
Hi,
The current widget URI spec does not work with XHR and hence can't be
used with popular JS libraries like JQuery Mobile. This makes the URI
scheme basically useless for a massive number of use cases.
Oops :)
On Jun/9/2011 7:09 PM, ext Rich Tibbett wrote:
On Thu, Jun 9, 2011 at 1:29 PM, Marcos Caceresmarcosscace...@gmail.com wrote:
To fix it, the widget URI spec needs to respond with HTTP responses
when a URI is dereferenced... similar to what blob:// does: