W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

RE: ACTION-568: Create an alternative mechanism for openURL andsend it to the mail list (Web Applications Working Group)

From: <marcosc@opera.com>
Date: Tue, 10 Aug 2010 17:37:48 +0000
Message-ID: <20100810173748.m6mt3cbtus4gcogk@staff.opera.com>
To: "SULLIVAN, BRYAN L (ATTCINW)" <BS3131@att.com>
Cc: gautamc@opera.com, Web Applications Working Group WG <public-webapps@w3.org>
Quoting "SULLIVAN, BRYAN L (ATTCINW)" <BS3131@att.com>:

> If the "linked location is outside the widget package", it should   
> not automatically load in the browser.

I don't understand what you mean here?

> We need the ability of  widgets to download and present  
> network-based content through means  other than XHR or iframes.

What does this have to do with openURL? What do you need openURL to do  
that window.open can't do? or that <a href=> can't do?

> If my widget is designed to ingest and  present content from  
> external sources (declared as per WARP) within  its context (and not  
> just within an iframe), causing such external  references to launch  
> in the browser will prevent the intended  operation of the widget.

The proposal has no inpact on XHR. What does this have to do with openURL?
Received on Tuesday, 10 August 2010 17:38:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:10 UTC