If something takes a DOMString as value is it clearly defined what happens
if the toString algorithm throws or returns a non-DOMString? I haven't
been able to find descriptions for that in the Web IDL specification. E.g.
obj = { toString:function() { throw(haha) } }
obj2 = {
On Apr 21, 2009, at 1:38 AM, Anne van Kesteren wrote:
If something takes a DOMString as value is it clearly defined what
happens if the toString algorithm throws or returns a non-DOMString?
I haven't been able to find descriptions for that in the Web IDL
specification. E.g.
obj = {
Dear Marcos,
See my comments inline.
Best Regards,
Rainer
*
T-Mobile International
Terminal Technology
Rainer Hillebrand
Head of Terminal Security
Landgrabenweg 151, D-53227 Bonn
Germany
+49 171 5211056 (My T-Mobile)
+49 228 936 13916 (Tel.)
+49 228 936
ISSUE-83 states:
Instantiated widget should not be able to read digital signature
http://www.w3.org/2008/webapps/track/issues/83
The following is a proposal of text to add to PC to address this
issue, based on text from Marcos and adding the notion of allowing
policy and access control
On Tue, Apr 21, 2009 at 3:31 PM, Frederick Hirsch
frederick.hir...@nokia.com wrote:
ISSUE-83 states:
Instantiated widget should not be able to read digital signature
http://www.w3.org/2008/webapps/track/issues/83
The following is a proposal of text to add to PC to address this issue,
based
On Thu, Apr 16, 2009 at 12:30 PM, jere.kapy...@nokia.com wrote:
Marcos,
thanks for a lucid and thorough widget I18N model proposal. This should
really help all concerned to come to agreement about how widgets should be
internationalized and localized. Also in this case I18N turned out to be
if there is no need for the Created property in the Widgets Signature
spec I suggest we remove it, though keep what we have in the Signature
Properties specification.
regards, Frederick
Frederick Hirsch
Nokia
On Apr 15, 2009, at 5:45 AM, ext Priestley, Mark, VF-Group wrote:
Dear All,
Hmm.. I tend to agree. Using an SQL database is only one possible
solution that we should be examining. I would rather say that we
should provide storage for structured data inside the UA. I'm not a
fan of calling out neither SQL or name-value pair storage.
At the same time I'm not sure that I
Anne van Kesteren:
If something takes a DOMString as value is it clearly defined what
happens if the toString algorithm throws or returns a non-DOMString?
Oliver Hunt:
I would assume that the exception will be propagated to the runtime, but
it should be stated.
Seems reasonable to state
On Apr 21, 2009, at 6:08 PM, Cameron McCormack wrote:
Anne van Kesteren:
If something takes a DOMString as value is it clearly defined what
happens if the toString algorithm throws or returns a non-DOMString?
Oliver Hunt:
I would assume that the exception will be propagated to the
runtime,
It’s only the ECMAScript language binding that uses the ES ToString
etc.
algorithms, so I think it would be fine to define in the ES language
binding section that exceptions thrown when converting an IDL value to
an ECMAScript value or vice versa will propagate to whatever invoked
that
Hi, Nikunj-
Nikunj Mehta wrote (on 4/21/09 5:44 PM):
Apparently the new charter [1] that forces everyone to re-join the WG
also lists among its deliverables as WebStorage with the explanation
that WebStorage is
two APIs for client-side data storage in Web applications: a name-value
pair
12 matches
Mail list logo
