On Fri, 08 Jul 2011 00:55:11 +0200, Jonas Sicking jo...@sicking.cc wrote:
I don't have an opinion on url parsing since I don't know enough about
it. However throwing an exception on an invalid URI sounds good to me.
I do not think we would want to start throwing on spaces appearing in e.g.
On Thu, Jul 7, 2011 at 1:46 PM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Jul 6, 2011 at 9:41 PM, Jeremy Orlow jor...@chromium.org wrote:
On Wed, Jul 6, 2011 at 10:06 AM, Israel Hilerio isra...@microsoft.com
We believe an error should be thrown because of the violation of the
unique
On Jul 7, 2011, at 21:47 , Ian Hickson wrote:
On Thu, 7 Jul 2011, Jonas Sicking wrote:
It's a pain since it forces us to try to coordinate codes across
multiple specifications, working groups and standards organizations.
Anything that allows us to _not_ coordinate is an epic disaster,
On 8/07/11 8:28 AM, Jonas Sicking wrote:
On Thu, Jul 7, 2011 at 3:21 PM, John J Barton
johnjbar...@johnjbarton.com wrote:
Jonas Sicking wrote:
We are definitely
short on use cases for mutation events in general which is a problem.
3. Client side dynamic translation. Intercept mutations
On 7/7/11 6:00 PM, ext Adrian Bateman wrote:
We're keen to resolve the remaining issues with the WebSockets API and have a
timetable
to get to Candidate Recommendation. From informal conversations we've had, we
believe
other browser vendors share this goal. I think the current WebSocket API is
On 7/6/11 5:49 PM, ext Ian Hickson wrote:
On Wed, 6 Jul 2011, Arthur Barstow wrote:
Do you oppose others submitting fixes to your spec bugs?
If someone is interested in submitting fixes, they are welcome to contact
me, so that I can work with them to work out how we can get something set
up.
On Thu, Jul 7, 2011 at 6:21 PM, John J Barton
johnjbar...@johnjbarton.com wrote:
1. Graphical breakpoints. The user marks some DOM element or attribute to
trigger break. The debugger inserts mutation listeners to watch for the
event that causes that element/attribute to be created/modified.
On 8/07/11 10:21 PM, Sean Hogan wrote:
On 8/07/11 8:28 AM, Jonas Sicking wrote:
On Thu, Jul 7, 2011 at 3:21 PM, John J Barton
johnjbar...@johnjbarton.com wrote:
Jonas Sicking wrote:
We are definitely
short on use cases for mutation events in general which is a problem.
3. Client side
On Thursday, July 07, 2011 10:21 PM, Arun Ranganathan wrote:
On 7/6/11 10:13 PM, Cameron McCormack wrote:
There was a recent change in Web IDL which made interface types (like
the readAsXXX argument types) not include null by default, and if you
want to allow null, to write it as “Type?”.
On Fri, Jul 8, 2011 at 5:21 AM, Sean Hogan shogu...@westnet.com.au wrote:
- MathJax (http://mathjax.org) is a JS lib that facilitates putting math
onto the web by converting LaTeX or MathML markup in a page to HTML. By
default MathJax triggers off the onload event to run this conversion on the
On Fri, Jul 8, 2011 at 5:21 AM, Sean Hogan shogu...@westnet.com.au wrote:
On 8/07/11 8:28 AM, Jonas Sicking wrote:
On Thu, Jul 7, 2011 at 3:21 PM, John J Barton
johnjbar...@johnjbarton.com wrote:
Jonas Sicking wrote:
We are definitely
short on use cases for mutation events in general
On Thu, Jul 7, 2011 at 3:47 PM, Ian Hickson i...@hixie.ch wrote:
Anything that allows us to _not_ coordinate is an epic disaster, IMHO.
We absolutely should be coordinating. How else can we ensure the platform
is a consistent platform?
This is a feature, not a bug.
Maybe, but I still think
Thanks, Jonas.
I made the changes to the sync and async versions of openKeyCursor and will
absolutely update Overview whenever I merge.
An up-to-date draft is a happy draft. :-)
E
-Original Message-
From: Jonas Sicking [mailto:jo...@sicking.cc]
Sent: Thursday, July 07, 2011 5:47
done
-Original Message-
From: public-webapps-requ...@w3.org [mailto:public-webapps-
requ...@w3.org] On Behalf Of Jonas Sicking
Sent: Monday, June 27, 2011 6:13 PM
To: Israel Hilerio
Cc: ben turner; public-webapps@w3.org
Subject: Re: [indexeddb] IDBTransaction.oncomplete event type
On Fri, Jul 8, 2011 at 6:55 AM, Sean Hogan shogu...@westnet.com.au wrote:
On 8/07/11 10:21 PM, Sean Hogan wrote:
- ARIA support in JS libs currently involves updating aria-attributes to
be appropriate to behavior the lib is implementing. Attribute mutation
listeners would allow an inverse
Jonas, what do you think?
Israel
On Wednesday, July 06, 2011 9:35 PM, Jeremy Orlow wrote:
I'd be OK with it. Jonas, what do you think?
J
On Wed, Jul 6, 2011 at 10:27 AM, Israel Hilerio
isra...@microsoft.commailto:isra...@microsoft.com wrote:
On Tuesday, June 28, 2011 11:21 AM, Israel Hilerio
On Thu, 7 Jul 2011, Jonas Sicking wrote:
On Thu, Jul 7, 2011 at 12:47 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 7 Jul 2011, Jonas Sicking wrote:
It's a pain since it forces us to try to coordinate codes across
multiple specifications, working groups and standards organizations.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13104
Ian 'Hixie' Hickson i...@hixie.ch changed:
What|Removed |Added
Status|NEW |RESOLVED
On Thu, 7 Jul 2011, Adrian Bateman wrote:
10213 - The definition of absolute url makes https:foo not an absolute url
Open, Assigned to Adam Barth
MICROSOFT PROPOSAL: Section 3 of the protocol spec
(http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-09#section-3)
shows the
As a background for the wider Component Model discussion, I put
together an overview of the general behavior attachment problem on the
Web:
http://wiki.whatwg.org/wiki/Behavior_Attachment
Please take a look. Comments, additions, and critique are appreciated.
:DG
On Thu, 7 Jul 2011, Jonas Sicking wrote:
12816 - Make second argument in constructor an object for future
extensibility
I'd like to see this change made too.
So far there's been two counter proposals in the bug for how to deal
with future extensions (which I strongly suspect we'll end
This is a public call for prior art. The W3C seeks information about
access control systems available before October 2005 and content
distribution systems before April 2006 that offer a viable solution that
may apply to the use of access requests policy in Widgets.
On 13 November 2009, pursuant
On Jul 8, 2011, at 21:56 , Ian Hickson wrote:
On Fri, 8 Jul 2011, Robin Berjon wrote:
Obviously we should coordinate, but coordination is time-consuming.
Coordinating exceptions codes is just a matter of checking a wiki page.
It's hardly time-consuming.
It only takes one person to forget
On Fri, Jul 8, 2011 at 3:56 PM, Ian Hickson i...@hixie.ch wrote:
If the proposal is to make all exceptions have a name property (or
whatever we call it) whether in ES, in DOM, or anywhere else, and to have
everyone pick consistent exception names, then I'm fine with that. If we
do do that then
On Friday, July 08, 2011 1:12 PM, Ian Hickson wrote:
12917 - deflate-stream should be an optional extension when
establishing a connection
Resolved, WontFix
MICROSOFT PROPOSAL: We strongly disagree with the API spec overruling
the protocol spec
on what is optional in the protocol. The
On Fri, 8 Jul 2011, Adrian Bateman wrote:
I strongly disagree. We must have interoperability amongst browser
user agents. Having some support compression and others not would lead
to authoring mistakes and will force us into either having or not
having compression based on how big
I think setting the event.transaction to the newly created transaction
for setVersion's success event makes sense (we might even do that in
the firefox implementation iirc, but i'm not fully sure).
For all the other events mentioned in the original comment of this
thread it needs to be null as no
On Fri, 8 Jul 2011, Robin Berjon wrote:
On Jul 8, 2011, at 21:56 , Ian Hickson wrote:
On Fri, 8 Jul 2011, Robin Berjon wrote:
Obviously we should coordinate, but coordination is time-consuming.
Coordinating exceptions codes is just a matter of checking a wiki
page. It's hardly
On Fri, Jul 8, 2011 at 1:20 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 7 Jul 2011, Jonas Sicking wrote:
12816 - Make second argument in constructor an object for future
extensibility
I'd like to see this change made too.
So far there's been two counter proposals in the bug for how to
Yes, this should only impact the setVersion onsuccess handler and not the open
onsuccess handler. We're in agreement :-).
I will work with Eliot to update the spec here.
Israel
On Friday, July 08, 2011 4:18 PM, Jonas Sicking wrote:
I think setting the event.transaction to the newly created
On 7/8/2011 1:18 PM, Dimitri Glazkov wrote:
As a background for the wider Component Model discussion, I put
together an overview of the general behavior attachment problem on the
Web:
http://wiki.whatwg.org/wiki/Behavior_Attachment
Please take a look. Comments, additions, and critique are
On 7/8/11, Dimitri Glazkov dglaz...@chromium.org wrote:
As a background for the wider Component Model discussion, I put
together an overview of the general behavior attachment problem on the
Web:
http://wiki.whatwg.org/wiki/Behavior_Attachment
Please take a look. Comments, additions, and
32 matches
Mail list logo
