I have some concern about restriction on the
applicability of the readonly attribute on some of the
form elements. The readonly attribute should be
applicable to all form elements that can change. This
means that the elements that should not support the
readonly attribute is the output and button
Ian,
I'm not sure that Section 2 of WA1 belongs in the spec. None of it seems
to have much to do with web applications and it makes up 50% of the
document.
I know I've said this before but shouldn't this be a separate document?
Wasn't that the plan for the other bits and pieces of HTML5
On Thu, 21 Apr 2005, Dean Edwards wrote:
I'm not sure that Section 2 of WA1 belongs in the spec. None of it seems
to have much to do with web applications and it makes up 50% of the
document.
I originally would have agreed, however when making the Web Forms 2 spec
one important piece of
On 4/21/05, Dean Edwards [EMAIL PROTECTED] wrote:
Ian Hickson wrote:
Speaking of setTimeout, where is this defined?
http://whatwg.org/specs/web-apps/current-work/#settimeout
OK. That's twice in one day. I'm off to read the WA1 spec
It's rather odd though, as it's been defined
On Wed, 20 Apr 2005, Frederic Simard wrote:
I have some concern about restriction on the
applicability of the readonly attribute on some of the
form elements. The readonly attribute should be
applicable to all form elements that can change. This
means that the elements that should not
On Sat, 16 Apr 2005, fantasai wrote:
Jim Ley wrote:
Or at the very least use something that would not confuse people into
thinking that it is an
application of SGML or XML.
Do you want to replace NONSGML with THIS-IS-NOT-SGML?
No, I want to replace !DOCTYPE - with
IMHO, one of the biggest obstacles for growth in Web applications
development is the fact that the entire application lives in the scope
of one request.
Once next request is made, the browser essentially forgets
everything and the whole new cycle of loading, initialization, and
binding begins.
