On Tue, 10 Jul 2012 02:39:45 +0200, Ian Hickson i...@hixie.ch wrote:
On Mon, 26 Mar 2012, Boris Zbarsky wrote:
On 3/26/12 3:19 PM, Ian Hickson wrote:
Changing it to a string doesn't affect that, though, does it?
Well, changing to a nullable string does affect it because doing
something like
On Mon, 9 Jul 2012, Boris Zbarsky wrote:
On 7/9/12 8:39 PM, Ian Hickson wrote:
Surely that's going to set the attribute regardless of whether the
attribute is nullable or whatnot.
Well, that depends on how reflecting DOMString? attributes are
defined. Making setting null call
On Mon, 23 Apr 2012, Henri Sivonen wrote:
I propose we adopt the following rules:
1) Every document that's being built by a parser or being built by an
XSLT engine has loading as its readyState.
Rationale:
* This is intuitive.
* It makes sense to make the XSLT experience
On Wed, 2 May 2012, Rick Waldron wrote:
On Wed, May 2, 2012 at 7:17 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 2 May 2012, Rick Waldron wrote:
JS APIs like this should always return the object (constructed
instance or not) and therefore chain implicitly.
Let me rephrase, I simply
On Thu, 3 May 2012, Shaun Moss wrote:
An obvious use case for readonly checkboxes came up a few weeks ago when
I made this page: http://marssociety.org.au/membership
The checklist at the bottom I could have made more simply/cheaply with
readonly checkboxes. However I had to use images.
On 7/10/12 12:27 PM, Ian Hickson wrote:
Since it doesn't for any other attributes that take a string but where
empty string and absence are different, why is it suddenly an issue
specifically with this attribute?
Because this is a new attribute we're defining and I happened to notice? ;)
I
