incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anis KADRI <>
Subject Re: Consistent implementation of the whitelist
Date Tue, 31 Jan 2012 02:39:29 GMT

Opera spec

W3C spec

According to the above. * is only used to allow unlimited access to
any resources but it doesn't explicitly say that it can be used to
build regular expressions.

Not sure what to do about the iOS attribute limitation.

On Mon, Jan 30, 2012 at 6:04 PM, Shazron <> wrote:
> During the 1.4.0 planning call, Anis proposed these requirements:
> 1.  a consistent implementation of the whitelist across all platforms
> 2.  follow the Opera standard (need a url to the docs for this,
> couldn't find it using the obvious keywords)
> 3.  white-listing should be documented on the docs site (Getting
> Started section)
> I like the Opera standard (see Android implementation here for an
> example:
> The only problem with iOS adopting this is the .plist format does not
> allow attributes in its xml. Right now the list of allowed hosts is
> just an array of strings, but to support "attributes" it would have to
> be an array of dictionaries. I could make this change but this
> satisfies neither requirements (1) nor (2).
> Changing the iOS implementation to support a PhoneGap.xml list instead
> of .plist is another effort entirely, but better now than later -
> unless we are going to use config.xml. Thoughts?

View raw message