On Oct 20, 2010, at 9:41 PM, Adam Barth wrote:
On Wed, Oct 20, 2010 at 7:14 AM, Stewart Brodie
stewart.bro...@antplc.com wrote:
Henri Sivonen hsivo...@iki.fi wrote:
When WebKit or Firefox trunk create an HTML script element node via
Range::createContextualFragment, the script has its
On 10/21/2010 09:43 AM, Maciej Stachowiak wrote:
On Oct 20, 2010, at 9:41 PM, Adam Barth wrote:
On Wed, Oct 20, 2010 at 7:14 AM, Stewart Brodie
stewart.bro...@antplc.com wrote:
Henri Sivonenhsivo...@iki.fi wrote:
When WebKit or Firefox trunk create an HTML script element node
via
On Oct 21, 2010, at 1:06 AM, Olli Pettay wrote:
On 10/21/2010 09:43 AM, Maciej Stachowiak wrote:
It is indeed not part of any standard. It was originally a Mozilla
vendor extension, later copied by Opera and Safari. We added support
for it in 2002 because at least at the time, some sites
On Wed, 20 Oct 2010 01:57:30 +0200, Jonas Sicking jo...@sicking.cc wrote:
The only real solution here is to abandon the use of URLs-strings
(blob:...) and instead use some type of object which represents a
reference to the blob/stream/whatever. Then make img.src, iframe.src,
I think I had already sent regrets for this call, and although the reason
has changed, I still have to send regrets (my youngest is ill, and I have
to go to the hospital with him).
Steven
On Wed, 20 Oct 2010 13:27:54 +0200, Arthur Barstow art.bars...@nokia.com
wrote:
Below is the
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3
Summary: [IndexedDB] The spec should be more explicit about the
queuing of setVersion transactions
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
On 10/21/10 6:50 AM, Anne van Kesteren wrote:
On Wed, 20 Oct 2010 01:57:30 +0200, Jonas Sicking jo...@sicking.cc
wrote:
The only real solution here is to abandon the use of URLs-strings
(blob:...) and instead use some type of object which represents a
reference to the blob/stream/whatever.
On Thu, Oct 21, 2010 at 3:50 AM, Anne van Kesteren ann...@opera.com wrote:
On Wed, 20 Oct 2010 01:57:30 +0200, Jonas Sicking jo...@sicking.cc wrote:
The only real solution here is to abandon the use of URLs-strings
(blob:...) and instead use some type of object which represents a
reference to
For IE9, we've adopted this attribute as well [msDoNotCheckDomainSecurity]
It has different meanings for different types of properites (fields vs.
accessors) and causes some proxies to be setup, but generally speaking it does
allow requests for the property to go through without an access
The forminput and formchange events are dispatched on all resettable
elements in a form when any element associated with the form
dispatches an input or a change event.
Is this case really worth the cost of increasing the size of the API
when it can easily be achieved with capturing events?
erik
On Thu, Oct 21, 2010 at 1:38 PM, Travis Leithead tra...@microsoft.com wrote:
For IE9, we've adopted this attribute as well [msDoNotCheckDomainSecurity]
It has different meanings for different types of properites (fields vs.
accessors) and causes some proxies to be setup, but generally
Jonas Sicking:
My gut reaction is to leave this out from the spec and not let WebIDL
specify security aspects.
Agreed. It’d be fine even for other specs (HTML5?) to define their own
security-related extended attributes to avoid writing prose that defines
when SECURITY_ERRs get thrown, but I
On Thu, Oct 21, 2010 at 2:39 PM, Cameron McCormack c...@mcc.id.au wrote:
Jonas Sicking:
My gut reaction is to leave this out from the spec and not let WebIDL
specify security aspects.
Agreed. It’d be fine even for other specs (HTML5?) to define their own
security-related extended attributes
On Fri, 22 Oct 2010 01:38:28 +0200, Doug Schepers schep...@w3.org wrote:
... I'm saying that when DOMActivate was first specced, in 1999-2000,
there wasn't a clean mobile-web model or significant use of inputs other
than keyboard and mouse, so click seemed to serve content authors just
as
14 matches
Mail list logo
