Re: [whatwg] General request regarding feature requests -- drawString()

[Stefan Haustein]

Hi,

I have updated the drawString() feature request accordingly:

http://rhino-canvas.sourceforge.net/www/drawstring.html

Best regards,
Stefan


Ian Hickson wrote:
I'm happy to see the increased interest in HTML5 recently -- especially 
with the amazing work Lachlan, Henri, and others are doing with the blog, 
the validator, feedback, and so forth.


Since the volume of feature requests is only going to increase in the near 
future, I'd like to request that feature requests be clear and include at 
least the following information:


 * What is the problem you are trying to solve?

 * What is the feature you are suggesting to help solve it?

 * What is the processing model for that feature, including error 
   handling? This should be very clear, including things such as event 
   timing if the feature involves events, how to create graphs 
   representing the data in the case of semantic proposals, etc.


 * Why do you think browsers would implement this feature?

 * Why do you think authors would use this feature?

 * What evidence is there that this feature is desparately needed?

Obviously, we want to keep the language as simple as possible. That means 
not everyone will get what they want. Having clear answers to the 
questions above will help all of us work out what is most important.


Cheers,
  

Re: [whatwg] Consistency of date formats between WF 2.0 and WA 1.0

[Henri Sivonen]

On Nov 19, 2006, at 23:53, Henri Sivonen wrote:


On Nov 18, 2006, at 12:48, Henri Sivonen wrote:

Why do WA 1.0 datetime formats for attributes allow space around  
"T" or multiple spaces in place of "T" when WF 2.0 only allows  
"T"? Also, why are spaces allowed before the time zone designator  
in the attribute variants in WA 1.0 when WF 2.0 does not allow  
spaces before "Z"?


The optional spaces in attribute values and replacing "T" with  
space are also a change from the format prescribed in HTML 4.01:

http://www.w3.org/TR/1999/REC-html401-19991224/types.html#h-6.11

Wouldn't it be prudent to stick to the HTML 4.01 format for  
attribute values?


Also, for consistency with WF 2.0 and HTML 4.01, I suggest that  
vaguer moments in time *in attributes* not allow spaces in conforming  
strings and require T as the date/time separator.


--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/

Re: [whatwg] Consistency of date formats between WF 2.0 and WA 1.0

[Henri Sivonen]

On Nov 18, 2006, at 12:48, Henri Sivonen wrote:

Why do WA 1.0 datetime formats for attributes allow space around  
"T" or multiple spaces in place of "T" when WF 2.0 only allows "T"?  
Also, why are spaces allowed before the time zone designator in the  
attribute variants in WA 1.0 when WF 2.0 does not allow spaces  
before "Z"?


The optional spaces in attribute values and replacing "T" with space  
are also a change from the format prescribed in HTML 4.01:

http://www.w3.org/TR/1999/REC-html401-19991224/types.html#h-6.11

Wouldn't it be prudent to stick to the HTML 4.01 format for attribute  
values?


--
Henri Sivonen
[EMAIL PROTECTED]
http://hsivonen.iki.fi/

[whatwg] [WF2] Pre-filling repetition templates

[J. King]

I was reading the section on seeding forms[1] earlier today, and I  
couldn't figure out how one is supposed to seed fields that are part of  
repetition templates with initial values.  Is this not possible?  Or am I  
just not reading the spec right?


I find that the section in question is particularly hard to read: I'm sure  
it's very helpful for implementors, but it doesn't seem to do a very good  
job of explaining the functioning of the form-data schema for authors.



[1] 
--
J. King
http://jking.dark-phantasy.com/

[whatwg] WF2: data attribute on SELECT

[Sean Hogan]

A few questions:

1. What happens when the data attribute is cleared?  Are all OPTIONs 
removed? Or no change?


2. What happens when the data attribute is set to the value it already 
contains?  Is that a refresh or no change?


3. Is there a way to start out with a SELECT that has hard-coded OPTIONs 
but no @data, set @data to load some OPTIONs (incrementally or 
otherwise) and then reset to the initial hard-coded options.


cheers,
SDH