WHATWG Wiki - User contributions [en]

Talk:Feature Proposals

2007-01-04T14:46:39Z

Matthew Raymond: /* Corner and Blink */

== Guidelines ==

Lachlan, I think these feature proposal guidelines are cluttering this page unnecessarily. It would be better to put them elsewhere and just create a link to the guidelines. Elsewhere could be on the Contribution Guidelines page, were you've put them initially, because feature proposals <em>are</em> contributions. --[[User:Michel Fortin|Michel Fortin]] 08:15, 16 November 2006 (PST)

: Replying to myself (again), maybe the guidelines are not needed anymore. If someone creates a proposal from the template and fills all the sections he can, others can complete the proposal if they think its valuable and are knowledgeable enough. That's why we have a wiki in the first place, isn't it? -[[User:Michel Fortin|Michel Fortin]] 08:21, 16 November 2006 (PST)

== Corner Element ==

Do we really need a <corner> element mentioned in the page? This is clearly presentational and already addressed by CSS. Same goes for <blink>. --[[User:Matthew Raymond|Matthew Raymond]] 14:46, 4 January 2007 (UTC)

Talk:Main Page

2006-11-19T17:21:34Z

Matthew Raymond: /* Terms, Acronyms and Abbreviations */

== WHATWG Specifications ==

* I think this whole section should go. Problems should be categorised by what they apply to, not classified by which specification should solve them. The solution, not the problem, is bound to a particular specification. --[[User:Michel Fortin|Michel Fortin]]
** I agree that problems shouldn't be categorised by the specification, but I don't agree this section should go. I think it's ok to provide some documentation about the actual specifications, including the actual features included within. It should be used to provide summaries and examples of actual features. Only when a proposal has been accepted and included in the spec, should it be included in this section. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:03, 15 Nov 2006 (PST)
*** That's fine with me. --[[User:Michel Fortin|Michel Fortin]]
**** That sounds fine, Lachlan. --[[User:Matthew Raymond|Matthew Raymond]]

== Terms, Acronyms and Abbreviations ==

* I think this section too should go too. --[[User:Michel Fortin|Michel Fortin]]
** I agree. If needed, we could create a glossary, but I don't think abbreviations and other terms should be on separate pages. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:05, 15 Nov 2006 (PST)
*** I agree that this can be condensed to a single page, but I think we still need a page for this. A glossary is a good idea. --[[User:Matthew Raymond|Matthew Raymond]]

Talk:Main Page

2006-11-19T17:19:22Z

Matthew Raymond: Me too...

Talk:Main Page

2006-11-19T17:13:32Z

Matthew Raymond: /* WHATWG Specifications */

== WHATWG Specifications ==

* I think this whole section should go. Problems should be categorised by what they apply to, not classified by which specification should solve them. The solution, not the problem, is bound to a particular specification. --[[User:Michel Fortin|Michel Fortin]]
** I agree that problems shouldn't be categorised by the specification, but I don't agree this section should go. I think it's ok to provide some documentation about the actual specifications, including the actual features included within. It should be used to provide summaries and examples of actual features. Only when a proposal has been accepted and included in the spec, should it be included in this section. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:03, 15 Nov 2006 (PST)
*** That's fine with me. --[[User:Michel Fortin|Michel Fortin]]

== Terms, Acronyms and Abbreviations ==

* I think this section too should go too. --[[User:Michel Fortin|Michel Fortin]]
** I agree. If needed, we could create a glossary, but I don't think abbreviations and other terms should be on separate pages. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:05, 15 Nov 2006 (PST)

Talk:Main Page

2006-11-19T17:12:38Z

Matthew Raymond: WHATWG Specifications

== WHATWG Specifications ==

* I think this whole section should go. Problems should be categorised by what they apply to, not classified by which specification should solve them. The solution, not the problem, is bound to a particular specification. --[[User:Michel Fortin|Michel Fortin]]
** I agree that problems shouldn't be categorised by the specification, but I don't agree this section should go. I think it's ok to provide some documentation about the actual specifications, including the actual features included within. It should be used to provide summaries and examples of actual features. Only when a proposal has been accepted and included in the spec, should it be included in this section. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:03, 15 Nov 2006 (PST)
*** That's fine with me. --[[User:Michel Fortin|Michel Fortin]]

== Terms, Acronyms and Abbreviations ==

* I think this section too should go too. --[[User:Michel Fortin|Michel Fortin]]
** I agree. If needed, we could create a glossary, but I don't think abbreviations and other terms should be on separate pages. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:05, 15 Nov 2006 (PST)

== WHATWG Specifications ==

I don't have a problem with this section changed so that it just has brief descriptions of the specs. The specifications change too much to really maintain any sort of detailed structure in a Wiki.

User:Matthew Raymond/vcalendar and vcard elements

2005-11-13T06:23:35Z

Matthew Raymond: Initial page creation...

I'll write a detailed description later. Until then, see my [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003111.html Markup for vCalendar and vCard] post in the mailing list archive.

HTML5

2005-11-13T05:45:06Z

Matthew Raymond:

User:Matthew Raymond

2005-11-13T05:44:24Z

Matthew Raymond: Slight change in vcalendar-related name.

On my user page I have some links to proposals I've made for various WHATWG specifications.

== Proposals for Web Forms 2.0 and Web Forms 3.0 ==

=== Current Proposals ===

* [[User:Matthew_Raymond:altinput_element|<altinput>]] element
* [[User:Matthew_Raymond:dataentry_element|<dataentry>]] element
* [[User:Matthew_Raymond:date_element|<date>]] element
* [[User:Matthew_Raymond:time_element|<time>]] element
* [[User:Matthew_Raymond:datetime_element|<datetime>]] element
* [[User:Matthew_Raymond:month_element|<month>]] element
* [[User:Matthew_Raymond:week_element|<week>]] element

=== Outdated / Abandoned Proposals ===

* [[User:Matthew_Raymond:format_element|<format>]] element
* [[User:Matthew_Raymond:idate_element|<idate>]] element
* [[User:Matthew_Raymond:icomplex_element|<icomplex>]] element

== Proposals for Web Applications 1.0 ==

* [[User:Matthew_Raymond:vcalendar_and_vcard_elements|<vcard>, <vcalendar>, <vevent> and <vattr>]] elements

== Proposals for Web Controls 1.0 ==

I have no current proposals for Web Controls 1.0.

User:Matthew Raymond

2005-11-13T05:39:10Z

Matthew Raymond: Updates...

On my user page I have some links to proposals I've made for various WHATWG specifications.

== Proposals for Web Forms 2.0 and Web Forms 3.0 ==

=== Current Proposals ===

* [[User:Matthew_Raymond:altinput_element|<altinput>]] element
* [[User:Matthew_Raymond:dataentry_element|<dataentry>]] element
* [[User:Matthew_Raymond:date_element|<date>]] element
* [[User:Matthew_Raymond:time_element|<time>]] element
* [[User:Matthew_Raymond:datetime_element|<datetime>]] element
* [[User:Matthew_Raymond:month_element|<month>]] element
* [[User:Matthew_Raymond:week_element|<week>]] element

=== Outdated / Abandoned Proposals ===

* [[User:Matthew_Raymond:format_element|<format>]] element
* [[User:Matthew_Raymond:idate_element|<idate>]] element
* [[User:Matthew_Raymond:icomplex_element|<icomplex>]] element

== Proposals for Web Applications 1.0 ==

* [[User:Matthew_Raymond:vcalendar_and_vcard|<vcard>, <vcalendar>, <vevent> and <vattr>]] elements

== Proposals for Web Controls 1.0 ==

I have no current proposals for Web Controls 1.0.

WHATWG Wiki:Deletion log

2005-11-13T05:28:49Z

Matthew Raymond: deleted "WA1:Communication": content was: 'This section contains new DOM interfaces related to server-set events, a standardization of XMLHttpRequest, and some other network-relates stuff.==C...'

Below is a list of the most recent deletions.
All times shown are server time (UTC).
<ul><li>05:28, 13 Nov 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Communication" <em>(content was: 'This section contains new DOM interfaces related to server-set events, a standardization of XMLHttpRequest, and some other network-relates stuff.==C...')</em></li>
<li>05:28, 13 Nov 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Multimedia" <em>(content was: 'This section covers the canvas element and a new DOM interface for sound.==Contributor Proposals==There are no proposals at this time.==Related P...')</em></li>
<li>05:28, 13 Nov 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Script and the DOM" <em>(content was: 'This section covers the DOM '''window''' interface and other commonly used DOM features that lie outside current specifications.==Contributor Propos...')</em></li>
<li>05:27, 13 Nov 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Editing" <em>(content was: 'This section covers editing using the contentEditable attribute.==Contributor Proposals==There are no proposals at this time.==Related Pages==* ...')</em></li>
<li>05:27, 13 Nov 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Menus, Buttons and Commands" <em>(content was: 'This section adds menus and associated markup to HTML.==Contributor Proposals==There are no proposals at this time.==Related Pages==* [[Web Appl...')</em></li>
<li>05:27, 13 Nov 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Semantics and Structure of HTML Elements"</li>
<li>05:26, 13 Nov 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Sections" <em>(content was: 'This section covers a more sophisticated heading and section system, including section grouping and specialized section markup with specific semantic ...')</em></li>
<li>11:48, 16 Jun 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Widgets" <em>(content was: 'This section deals with new widgets (such as trees, data grids, et cetera) that are common to other development environments, but are currently absent...')</em></li>
<li>11:22, 16 Jun 2005 [[User:Matthew Raymond|Matthew Raymond]] deleted "WA1:Details of HTML Semantics" <em>(content was: 'This section provides additional sematics for specific class names, link relationships and sections and headers.==Contributor Proposals==There are ...')</em></li>

</ul>

User:Matthew Raymond/altinput element

2005-07-06T01:17:46Z

Matthew Raymond: New altinput element.

The <altinput> element is intended to be a possible alternative to my earlier [[User:Matthew_Raymond:dataentry_element|<dataentry>]] element.

The <altinput> element is a way of accomplishing the same goals as <dataentry> while ensuring that the size of a form's elements collection and the position of controls within it doesn't change between legacy and WF2 browsers. Rather than the element itself being a form control, <altinput> instead performs the following:

* If it has a control with an |id| attribute equal to its |for| attribute, then it attempts to assign its own |type| attribute value to the |type| of the specified control.
* If the |type| is not supported, then the <altinput> acts as nothing more than a <span>.
* However, if the |type| is supported, the control has its |type| changed and the entire contents of the <altinput> element, with the exception of specified control, are not be rendered.

The result is that, in most cases, <altinput> acts almost exactly like <dataentry>.

==Examples==

Here's a simple example for the three <select> scenario:

<altinput for="d1" type="date" value="2005-02-09">
<input type="hidden" id="d1" name="d1" />
<select name="d1_day"></select> /
<select name="d1_month"></select> /
<select name="d1_year"></select>
</altinput>

Here's an example for users of jscalendar:

<altinput for="sel1" type="date">
<input type="text" id="sel1" name="date1" size="30" />
<input type="reset" value=" ... " onclick="return showCalendar('sel1', '%Y-%m-%d');">
YYYY-MM-DD
</altinput>

==Pros==

# The size of a form's elements collection in Javascript never changes.
# The <altinput> element can allow for a far greater range of legacy fallback than <input> alone.
# Because the |type| is defined in an attribute, <altinput> can be used for input types in later specifications, or for vendor-specific input types.
# Because the elemnt requires a child form control, it encourages the use of <input> alone in simple cases where legacy fallback needs are minimal.
# The element is designed only to prevent the presentation of its child elements. It does not require user agents to delete contents from the DOM or suppress Javascript execution.

==Cons==

# It's slightly more complicated to use than <dataentry>.
# In some situations, you must use a hidden <input> control as the target of the <altinput> element's |for| attribute.
# It may still inherit some minor issues from <dataentry>.

User:Matthew Raymond

2005-07-05T23:50:30Z

Matthew Raymond: Adding altinput element link.

On my user page I have some links to proposals I've made for various WHATWG specifications.

== Proposals for Web Forms 2.0 ==

=== Current Proposals ===

* [[User:Matthew_Raymond:altinput_element|<altinput>]] element
* [[User:Matthew_Raymond:dataentry_element|<dataentry>]] element
* [[User:Matthew_Raymond:date_element|<date>]] element
* [[User:Matthew_Raymond:time_element|<time>]] element
* [[User:Matthew_Raymond:datetime_element|<datetime>]] element
* [[User:Matthew_Raymond:month_element|<month>]] element
* [[User:Matthew_Raymond:week_element|<week>]] element

=== Outdated / Abandoned Proposals ===

* [[User:Matthew_Raymond:format_element|<format>]] element
* [[User:Matthew_Raymond:idate_element|<idate>]] element
* [[User:Matthew_Raymond:icomplex_element|<icomplex>]] element

== Proposals for Web Applications 1.0 ==

* [[User:Matthew_Raymond:menulabel_element|<menulabel>]] element

== Proposals for Web Controls 1.0 ==

I have no current proposals for Web Controls 1.0.

HTML5

2005-06-16T14:06:02Z

Matthew Raymond: Changed to reflect heavy alteration of the WA1 spec.

HTML has served the Web community well, but it lacks some basic semantics necessary for modern Web applications. Web Applications 1.0 attempts to rectify this, while at the same time updating the HTML specifications to address issues raised in the past few years.

==Status==
Web Applications 1.0 is still in the draft stage and is undergoing heavy development. Major changes in the specification can be expected.

==Sections==
* [[WA1:Semantics and Structure of HTML Elements|Semantics and Structure of HTML Elements]]
* [[WA1:Menus, Buttons and Commands|Menus, Buttons and Commands]]
* [[WA1:Editing|Editing]]
* [[WA1:Parsing|Parsing]]
* [[WA1:Rendering|Rendering]]
* [[WA1:Script and the DOM|Script and the DOM]]
* [[WA1:Multimedia|Multimedia]]
* [[WA1:Communication|Communication]]
* [[WA1:User Interaction|User Interaction]]

==External Links==
* [http://whatwg.org/specs/web-apps/current-work/ Web Applications 1.0]

User:Matthew Raymond/dataentry element

2005-04-05T15:05:54Z

Matthew Raymond: Changes to reflect updates from the mailing list.

The <dataentry> element is just like <input>, with three exceptions:

* It doesn't have the depreciated attributes.
* It has no |alt| attribute, but instead contains alternative contents as child nodes for legacy support.
* It requires a closing tag ("</dataentry>").
* It must contain at least one form control. If </dataentry> has a defined |name| attribute, then it must contain at least one form control with a defined |name| attribute.

==Examples==

Here's a simple example for the three <select> scenario:

<dataentry type="date" id="d1" name="d1" value="2005-02-09">
<select name="d1_day"></select> /
<select name="d1_month"></select> /
<select name="d1_year"></select>
</dataentry>

Here's an example for users of jscalendar:

<dataentry type="date" id="sel1_WF2" name="date1">
<input type="text" id="sel1" name="date1" size="30">
<input type="reset" value=" ... " onclick="return showCalendar('sel1', '%Y-%m-%d');">
YYYY-MM-DD
</dataentry>

==Pros==

# The <dataentry> element can allow for a far greater range of legacy fallback than <input>.
# Because the |type| is defined in an attribute, <dataentry> can be used for input types in later specifications, or for vendor-specific input types.
# The element is designed in both semantics and structure to encourages the use of <input> in simple cases where legacy fallback needs are minimal.
# The element is designed only to prevent the presentation of its child elements. It does not require user agents to delete contents from the DOM or suppress Javascript execution.
# Because it has the same attributes as <input>, there's nothing new to learn except the inclusion of fallback content.

==Cons==

# The size of a form's elements collection in Javascript may differ between user agents.
# There may be legacy Javascript issues that cause script failure when generating unrecognized elements.
# When creating an <dataentry> element, you should be able to test for the correct element type by checking to see if it has a .type property, but I can't be 100% certain.
# Some unneeded Javascript overhead on WF2 clients.
# CSS styling for <dataentry> can't be done directly because user agents that support unrecognized elements may use the styling instead of ignoring the <dataentry> as intended.

==Solutions For Cons==

# A simple method could be added to the DOM that would set whether a form control is include in the .elements collection. A function could then be run when the page loads to hide the <dataentry> elements from the collection.
# This is a general issue affecting all new elements we introduce.
# May not be an issue, but I'd like to hear from an expert.
# Ian seems to feel this is a non-issue, so I won't argue with him.
# I'm considering a pseudo-class (":controltype()" or ":dom(attr, val)"?) that should allow a web author to style <dataentry type="controltype"> when the control type is supported. I'm still working on this concept, though, and I'm wondering if a more general and more powerful pseudo-class can't be developed.
__NOTOC__

WHATWG Wiki:Contribution Guidelines

2005-03-31T02:42:03Z

Matthew Raymond: Added language to specify that copies or modified versions of WHATWG specs should not be part of the wiki.

Before you get started on editing any of the pages, please read all of the following carefully.

==Key Policies==
The WHATWG Wiki has policies similar to those of [http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines Wikipedia]. Among these are the following:

# '''Avoid bias.''' Articles should be written from a neutral point of view, representing differing views on a subject fairly and sympathetically. There will be some bias given the nature of this working group, but this does not mean that information should be excluded or opposing viewpoints supressed. All contributers should keep an open mind.
# '''Don't infringe copyrights.''' The WHATWG Wiki is licensed under the terms of the [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation License]. Submitting work to this wiki in violation of copyright threatens the objectives of the Web Hypertext Application Technology Working Group, and could lead to legal problems.
# '''WHATWG Wiki is not intended as a free wiki.''' It is intended to help people contribute to the development of WHATWG specifications, and to help others understand these specifications and why we feel they are necessary.
# '''Respect other contributors.''' Editing pages for any purpose other than to add value to the pages or to improve the fairness in which the subject is dealt with is inappropriate.

==Site-Specific Policies==
We also have some policies specific to our site:
# '''Don't misrepresent your own proposals or opinions as those of WHATWG.'''
# '''Keep pages expressing your own proposals and opinions under your own user namespace.''' That is, if you want create a page about your proposed <XYZZY> element and your user name is "Fluffy the Rabbit", you should create a page called "User:Fluffy the Rabbit:XYZZY element".
# '''If you're part of a group of people supporting the same proposal, use the "Group Proposal" namespace.''' In other words, if you have a group proposal for an <XYZZY> element, the page would be named "Group Proposal:XYZZY element".
# '''Avoid creating alternate versions of WHATWG specifications using this wiki.''' The WHATWG specifications can change swiftly and with little notice, so copies of part or all of a specification may become outdated overnight. Please submit requests for changes to a WHATWG specification directly to the [http://www.whatwg.org/mailing-list mailing list].

Main Page

2005-03-31T02:33:31Z

Matthew Raymond: Added language to specify that the spec itself should not be part of the wiki.

Welcome to the WHATWG Wiki. Before you begin, please read the [[WHATWG Wiki:Contribution Guidelines|Contribution Guidelines]].

==Purpose==
The purpose of the WHATWG Wiki is to create a place for WHATWG contributors to post and compile their own proposals and ideas regarding WHATWG specifications. The specifications themselves will not be available for editing via this wiki. However, ideas you post here may find their way into current and future WHATWG specifications.

==WHATWG Specifications==
* [[Web Forms 2.0]]
* [[Web Applications 1.0]]
* [[Web Controls 1.0]]

==Terms, Acronyms and Abbreviations==
* [[Common Abbreviations and Acronyms]]
* [[Common Terms]]

WA1:Focus

2005-03-15T18:41:26Z

Matthew Raymond: Initial page creation...

This section provides additional support related element focus and the use of the tab key to change focus between elements.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Applications 1.0]]

==External Links==
* [http://whatwg.org/specs/web-apps/current-work/#focus Web Applications 1.0 - Focus]

WA1:Structured Data

2005-03-15T18:19:27Z

Matthew Raymond: Initial page creation...

This section mainly covers proposals related to calendars and business cards.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Applications 1.0]]

==External Links==
* [http://whatwg.org/specs/web-apps/current-work/#structured Web Applications 1.0 - Structured data]

WC1:CSS3, Focus and Key Handling

2005-03-15T16:12:48Z

Matthew Raymond: Initial page creation...

Quoting directly from the spec: "..."

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Controls 1.0]]

==External Links==
* [http://whatwg.org/specs/web-controls/current-work/#x Web Controls 1.0 - ... (CSS3, Focus and Key Handling)]

WC1:Properties for Selection, Focus, and Editing

2005-03-15T16:08:54Z

Matthew Raymond: Changed a link title...

This section contains CSS properties control features that are directly related to the DOM.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Controls 1.0]]

==External Links==
* [http://whatwg.org/specs/web-controls/current-work/#properties Web Controls 1.0 - Properties for selection, focus, and editing]

WC1:DOM Interfaces

2005-03-15T16:07:40Z

Matthew Raymond: Initial page creation...

This section deals with assorted DOM interfaces related to the user interface.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Controls 1.0]]

==External Links==
* [http://whatwg.org/specs/web-controls/current-work/#dom-interfaces Web Controls 1.0 - DOM Interfaces]

WC1:Properties for Selection, Focus, and Editing

2005-03-15T16:03:34Z

Matthew Raymond: Initial page creation...

Main Page

2005-03-15T15:46:54Z

Matthew Raymond: Oops, that's WC1...

Welcome to the WHATWG Wiki. Before you begin, please read the [[WHATWG Wiki:Contribution Guidelines|Contribution Guidelines]].

==WHATWG Specifications==
* [[Web Forms 2.0]]
* [[Web Applications 1.0]]
* [[Web Controls 1.0]]

==Terms, Acronyms and Abbreviations==
* [[Common Abbreviations and Acronyms]]
* [[Common Terms]]

Web Controls 2.0

2005-03-15T15:42:55Z

Matthew Raymond: Web Controls 2.0 moved to Web Controls 1.0

#REDIRECT [[Web Controls 1.0]]

WF2:Extensions to the HTML Level 2 DOM Interfaces

2005-03-14T14:41:40Z

Matthew Raymond: Spelling correction

This section defines extensions to the DOM Level 2 HTML specification for the purpose of supporting new markup and features elsewhere in the specification.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#dom Web Forms 2.0 - Extensions to the HTML Level 2 DOM interfaces]

WF2:Fetching Data from External Resources

2005-03-14T14:41:13Z

Matthew Raymond: Spelling correction

This section covers the use of external data sources to fill forms and form controls.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#fetching-data Web Forms 2.0 - Fetching data from external resources]

WF2:Form Submission

2005-03-14T14:40:20Z

Matthew Raymond: Spelling correction

This section describes a modified version of the HTML4 form submission algorithm (HTML4 section 17.13.3).

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#form-submission Web Forms 2.0 - Form Submission]

WF2:The Forms Event Model

2005-03-14T14:39:49Z

Matthew Raymond: Spelling correction

This section introduces the new events and new semantics for the existing events.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#forms-events-model Web Forms 2.0 - The Forms Event Model]

WF2:The Repetition Model for Repeating Form Controls

2005-03-14T14:39:05Z

Matthew Raymond: Spelling correction

The repeating form controls model defines how forms with repeating items can be described without resorting to scripting.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#repeatingFormControls Web Forms 2.0 - The Repetition Model for Repeating Form Controls]

WF2:Styling Form Controls

2005-03-14T14:38:33Z

Matthew Raymond: Initial page creation...

This section specifies how to handle styling of form controls. Mostly, it addresses how to handle the CSS 3 Basic UI pseudo-classes.

==Contributor Proposals==
There are no proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#styling-form-controls Web Forms 2.0 - Styling form controls]

WF2:Extensions to the HTML Level 2 DOM Interfaces

2005-03-14T14:31:19Z

Matthew Raymond: Initial page creation...

This section defines extensions to the DOM Level 2 HTML specification for the purpose of supporting new markup and features elsewhere in the specification.

==Contributor Proposals==
There are now proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#dom Web Forms 2.0 - Extensions to the HTML Level 2 DOM interfaces]

WF2:Fetching Data from External Resources

2005-03-14T14:22:23Z

Matthew Raymond: Initial page creation...

This section covers the use of external data sources to fill forms and form controls.

==Contributor Proposals==
There are now proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#fetching-data Web Forms 2.0 - Fetching data from external resources]

WF2:The Forms Event Model

2005-03-14T14:16:50Z

Matthew Raymond: Added External Links section.

This section introduces the new events and new semantics for the existing events.

==Contributor Proposals==
There are now proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#forms-events-model Web Forms 2.0 - The Forms Event Model]

WF2:The Repetition Model for Repeating Form Controls

2005-03-14T14:15:18Z

Matthew Raymond: Added External Links section.

The repeating form controls model defines how forms with repeating items can be described without resorting to scripting.

==Contributor Proposals==
There are now proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#repeatingFormControls Web Forms 2.0 - The Repetition Model for Repeating Form Controls]

WF2:Extensions to Form Control Elements

2005-03-14T14:13:39Z

Matthew Raymond: Added External Links section.

This section describes how Web Forms 2.0 extends the traditional HTML form model to support new types and features.

==Contributor Proposals==
* [[User:Matthew Raymond:dataentry element|The <dataentry> element]] by [[User:Matthew Raymond|Matthew Raymond]]
* [[User:Matthew Raymond:date element|The <date> element]] by [[User:Matthew Raymond|Matthew Raymond]]

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#extend-form-controls Web Forms 2.0 - Extensions to Form Control Elements]

WF2:Form Submission

2005-03-14T14:09:52Z

Matthew Raymond: Initial page creation...

This section describes a modified version of the HTML4 form submission algorithm (HTML4 section 17.13.3).

==Contributor Proposals==
There are now proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

==External Links==
* [http://whatwg.org/specs/web-forms/current-work/#form-submission Web Forms 2.0 - Form Submission]

WF2:The Forms Event Model

2005-03-14T14:05:05Z

Matthew Raymond: Initial page creation...

This section introduces the new events and new semantics for the existing events.

==Contributor Proposals==
There are now proposals at this time.

==Related Pages==
* [[Web Forms 2.0]]

WF2:Extensions to Form Control Elements

2005-03-14T13:59:44Z

Matthew Raymond: "Related Links" section added for easier navigation.

WF2:The Repetition Model for Repeating Form Controls

2005-03-14T13:58:56Z

Matthew Raymond: "Related Links" section added for easier navigation.

WF2:The Repetition Model for Repeating Form Controls

2005-03-14T13:55:43Z

Matthew Raymond: Initial page creation...

The repeating form controls model defines how forms with repeating items can be described without resorting to scripting.

==Contributor Proposals==
There are now proposals at this time.

User:Matthew Raymond/dataentry element

2005-03-10T17:22:52Z

Matthew Raymond: Made a minor addition regarding :controltype().

The <dataentry> element is just like <input>, with three exceptions:

* It doesn't have the depreciated attributes.
* It has no |alt| attribute, but instead contains alternative contents as child nodes for legacy support.
* It requires a closing tag ("</dataentry>").

==Examples==

Here's a simple example for the three <select> scenario:

<dataentry type="date" id="d1" name="d1" value="2005-02-09">
<select name="d1_day"></select> /
<select name="d1_month"></select> /
<select name="d1_year"></select>
</dataentry>

Here's an example for users of jscalendar:

<dataentry type="date" id="sel1_WF2" name="date1">
<input type="text" id="sel1" name="date1" size="30">
<input type="reset" value=" ... " onclick="return showCalendar('sel1', '%Y-%m-%d');">
YYYY-MM-DD
</dataentry>

==Pros==

# The <dataentry> element can allow for a far greater range of legacy fallback than <input>.
# Because the |type| is defined in an attribute, <dataentry> can be used for input types in later specifications, or for vendor-specific input types.
# The element is designed in both semantics and structure to encourages the use of <input> in simple cases where legacy fallback needs are minimal.
# The element is designed only to prevent the presentation of its child elements. It does not require user agents to delete contents from the DOM or suppress Javascript execution.
# Because it has the same attributes as <input>, there's nothing new to learn except the inclusion of fallback content.

==Cons==

# The size of a form's elements collection in Javascript may differ between user agents.
# There may be legacy Javascript issues that cause script failure when generating unrecognized elements.
# When creating an <dataentry> element, you should be able to test for the correct element type by checking to see if it has a .type property, but I can't be 100% certain.
# Some unneeded Javascript overhead on WF2 clients.
# CSS styling for <dataentry> can't be done directly because user agents that support unrecognized elements may use the styling instead of ignoring the <dataentry> as intended.

==Solutions For Cons==

# We could just define <dataentry> as never showing up in the .elements collection, or provide an attribute to that effect. Neither are ideal, but if most of the WF2 content will be written from scratch, then .elements is only an issue for those trying to support browsers without support for getElementById.
# This is a general issue affecting all new elements we introduce.
# May not be an issue, but I'd like to hear from an expert.
# Ian seems to feel this is a non-issue, so I won't argue with him.
# I'm considering a pseudo-class (":controltype()"?) that should allow a web author to style <dataentry type="controltype"> when the control type is supported. I'm still working on this concept, though, and I'm wondering if a more general and more powerful pseudo-class can't be developed.
__NOTOC__

Web Controls 1.0

2005-03-10T14:45:22Z

Matthew Raymond: Initial page creation...

Web Controls 1.0 contains DOM and CSS extensions to create new form controls and widgets.

==Status==
This specification is in the very early stages of development, and active development will probably not occur until previous specifications are more mature. It is currently host to a number of features that were specified for other drafts but were removed from those drafts for various reasons.

==Sections==
'''Note: These sections and their names are subject to change.'''
* [[WC1:CSS3, Focus and Key Handling|CSS3, Focus and Key Handling]]
* [[WC1:Properties for Selection, Focus, and Editing|Properties for Selection, Focus, and Editing]]
* [[WC1:DOM Interfaces|DOM Interfaces]]

== External Links ==
* [http://whatwg.org/specs/web-controls/current-work/ Web Controls 1.0]

Web Forms 2.0

2005-03-10T14:32:31Z

Matthew Raymond: Moving the section stuff to the new WF2 namespace.

Web Forms 2.0 is an extension to the forms features found in [http://www.w3.org/TR/html401 HTML 4.01]'s forms chapter. The specification applies to both HTML and XHTML user agents, and provides new strongly-typed input fields, new attributes for defining constraints, a repeating model for declarative repeating of form sections, new DOM interfaces, new DOM events for validation and dependency tracking, and XML submission and initialization of forms. This specification also standardises and codifies existing practice in areas that have not been previously documented.

[http://www.w3.org/TR/html4 HTML4], [http://www.w3.org/TR/xhtml11/ XHTML 1.1] and the [http://www.w3.org/DOM/ DOM] are thus extended in a manner which has a clear migration path from existing HTML forms, leveraging the knowledge authors have built up with their experience with HTML so far.

== Status ==

Web Forms 2.0 has reached a relative stage of maturity, and major alterations of the specification are unlikely at this stage. However, major changes may be introduced in a [[Web Forms 3.0 (unofficial)|future specification]].

== Sections ==

* [[WF2:Extensions to Form Control Elements|Extensions to Form Control Elements]]
* [[WF2:The Repetition Model for Repeating Form Controls|The Repetition Model for Repeating Form Controls]]
* [[WF2:The Forms Event Model|The Forms Event Model]]
* [[WF2:Form Submission|Form Submission]]
* [[WF2:Fetching Data from External Resources|Fetching Data from External Resources]]
* [[WF2:Extensions to the HTML Level 2 DOM Interfaces|Extensions to the HTML Level 2 DOM Interfaces]]
* [[WF2:Styling Form Controls|Styling Form Controls]]

== External Links ==
* [http://whatwg.org/specs/web-forms/current-work/ Web Forms 2.0]

WF2 Form Control Extensions

2005-03-10T14:29:11Z

Matthew Raymond: WF2 Form Control Extensions moved to WF2:Extensions to Form Control Elements

#REDIRECT [[WF2:Extensions to Form Control Elements]]

HTML5

2005-03-10T14:27:31Z

Matthew Raymond: Initial page creation...

HTML has served the Web community well, but it lacks some basic semantics necessary for modern Web applications. Web Applications 1.0 attempts to rectify this, while at the same time updating the HTML specifications to address issues raised in the past few years.

==Status==
Web Applications 1.0 is still in the draft stage and is undergoing heavy development. Major changes in the specification can be expected.

==Sections==
* [[WA1:Semantics and Structure of HTML Elements|Semantics and Structure of HTML Elements]]
* [[WA1:Details of HTML Semantics|Details of HTML Semantics]]
* [[WA1:Sections|Sections]]
* [[WA1:Structured Data|Structured Data]]
* [[WA1:Widgets|Widgets]]
* [[WA1:Menus, Buttons and Commands|Menus, Buttons and Commands]]
* [[WA1:Editing|Editing]]
* [[WA1:Script and the DOM|Script and the DOM]]
* [[WA1:Multimedia|Multimedia]]
* [[WA1:Communication|Communication]]
* [[WA1:Focus|Focus]]

==External Links==
* [http://whatwg.org/specs/web-apps/current-work/ Web Applications 1.0]

Web Forms 2.0

2005-03-10T14:03:52Z

Matthew Raymond: Doing away with all the local links for related specifications, and going with external links.

Web Forms 2.0 is an extension to the forms features found in [http://www.w3.org/TR/html401 HTML 4.01]'s forms chapter. The specification applies to both HTML and XHTML user agents, and provides new strongly-typed input fields, new attributes for defining constraints, a repeating model for declarative repeating of form sections, new DOM interfaces, new DOM events for validation and dependency tracking, and XML submission and initialization of forms. This specification also standardises and codifies existing practice in areas that have not been previously documented.

[http://www.w3.org/TR/html4 HTML4], [http://www.w3.org/TR/xhtml11/ XHTML 1.1] and the [http://www.w3.org/DOM/ DOM] are thus extended in a manner which has a clear migration path from existing HTML forms, leveraging the knowledge authors have built up with their experience with HTML so far.

== Status ==

Web Forms 2.0 has reached a relative stage of maturity, and major alterations of the specification are unlikely at this stage. However, major changes may be introduced in a [[Web Forms 3.0 (unofficial)|future specification]].

== Sections ==

* [[WF2 Form Control Extensions|Extensions to form control elements]]
* [[WF2 Repetition Model|The repetition model for repeating form controls]]
* [[WF2 Form Events Model|The forms event model]]
* [[WF2 Form Submission|Form submission]]
* [[WF2 External Data Resources|Fetching data from external resources]]
* [[WF2 HTML DOM2 Extensions|Extensions to the HTML Level 2 DOM interfaces]]
* [[WF2 Form Control Styling|Styling form controls]]

== External Links ==
* [http://whatwg.org/specs/web-forms/current-work/ Web Forms 2.0]

Main Page

2005-03-10T13:57:31Z

Matthew Raymond: Removed the Competing and Related Spec sections.

Welcome to the WHATWG Wiki. Before you begin, please read the [[WHATWG Wiki:Contribution Guidelines|Contribution Guidelines]].

==WHATWG Specifications==
* [[Web Forms 2.0]]
* [[Web Applications 1.0]]
* [[Web Controls 2.0]]

==Terms, Acronyms and Abbreviations==
* [[Common Abbreviations and Acronyms]]
* [[Common Terms]]

WHATWG Wiki:Contribution Guidelines

2005-03-09T16:04:17Z

Matthew Raymond: Initial guidelines page.

Main Page

2005-03-09T15:55:24Z

Matthew Raymond: Changing guidelines link...

Welcome to the WHATWG Wiki. Before you begin, please read the [[WHATWG Wiki:Contribution Guidelines|Contribution Guidelines]].

== WHATWG Specifications ==
* [[Web Forms 2.0]]
* [[Web Applications 1.0]]
* [[Web Controls 2.0]]

== Related Specifications ==
* [[HTML 4.01]]
* [[CSS 2.1]] and [[CSS 3]]
* [[ECMAScript]]
* [[DOM 2]]
* [[hCalendar]]
* [[hCard]]
* [[ISO 8601]]

== Competing Specifications ==
* [[XForms]]
* [[SVG]]
* [[XAML]]
* [[XUL]]

== Terms, Acronyms and Abbreviations ==
* [[Common Abbreviations and Acronyms]]
* [[Common Terms]]

XForms

2005-03-09T15:12:08Z

Matthew Raymond: Added link to W3C XForms page.

''(Insert interesting comments on XForms here.)''

==External Links==
* [http://ln.hixie.ch/?start=1110316686&count=1 Hixie's Natural Log: XForms myths]
* [http://www.w3.org/MarkUp/Forms/ XForms - the next generation of Web forms]