A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "Feature Proposals"

From WHATWG Wiki
Jump to: navigation, search
(Guidelines)
m (Other: <code>)
Line 26: Line 26:
 
This list of features needs to be sorted out.  They've come from all the [http://del.icio.us/lachlan.hunt/WHATWG feedback provided on blogs] over the past few weeks.
 
This list of features needs to be sorted out.  They've come from all the [http://del.icio.us/lachlan.hunt/WHATWG feedback provided on blogs] over the past few weeks.
  
* Don’t render quotation marks around q elements.
+
* Don't render quotation marks around <code>q</code> elements.
 
* Make form validation easier
 
* Make form validation easier
** required attribute
+
** <code>required</code> attribute
** maxlength attribute for textarea
+
** <code>maxlength</code> attribute for textarea
** pattern attribute
+
** <code>pattern</code> attribute
** min
+
** <code>min</code>
** max
+
** <code>max</code>
 
* New Form Controls
 
* New Form Controls
 
** Search fields
 
** Search fields
Line 45: Line 45:
 
** Currency
 
** Currency
 
** URL
 
** URL
* WYSIWIG Editor (contentEditable)
+
* WYSIWIG Editor (<code>contentEditable</code>)
 
* Placeholder attribute
 
* Placeholder attribute
 
* Captions for images
 
* Captions for images
* Bring back the start and value attributes for ordered lists.
+
* Bring back the <code>start</code> and <code>value</code> attributes for ordered lists.
* Bring back the menu element
+
* Bring back the <code>menu</code> element
 
* Require XHTML-link syntax for HTML
 
* Require XHTML-link syntax for HTML
 
* Caption/label/list header for lists
 
* Caption/label/list header for lists
* Include the role attribute.
+
* Include the <code>role</code> attribute.
* Allow href on all elements
+
* Allow <code>href</code> on all elements
 
* Make it easier to mark up blocks of code
 
* Make it easier to mark up blocks of code
 
* Allow block level elements inside paragraphs
 
* Allow block level elements inside paragraphs
 
* “a tag that could hold "bad grammar" and not have any effect on the validation (sort of like a document.write from JavaScript) and would terminate all unclosed items at the end of the element (like TDs tend to do).”
 
* “a tag that could hold "bad grammar" and not have any effect on the validation (sort of like a document.write from JavaScript) and would terminate all unclosed items at the end of the element (like TDs tend to do).”
* <blink>!!!
+
* <code>blink</code>!
* Fix the object element.
+
* Fix the <code>object</code> element.
* Unify img, object, embed and iframe into a single element
+
* Unify <code>img</code>, <code>object</code>, </code>embed</code> and <code>iframe</code> into a single element
 
* Headers and footers
 
* Headers and footers
* A mechanism to include content from an external source (e.g. <include>, perhaps like XInclude)
+
* A mechanism to include content from an external source (e.g. <code>include</code>, perhaps like XInclude)
* A <corner> element (presumably for making rounded corners)
+
* A <code>corner</code> element (presumably for making rounded corners)
 
* Markup for advertisements
 
* Markup for advertisements
 
* Easier column layouts
 
* Easier column layouts
* A <foot> element for containing scripts at the bottom of the page, or something to help deal with cross-browser load events.
+
* A <code>foot</code> element for containing scripts at the bottom of the page, or something to help deal with cross-browser load events.
* Key Generation/Certificate management (The keygen element)
+
* Key Generation/Certificate management (The <code>keygen</code> element)

Revision as of 16:49, 8 December 2006

This document contains a list of the problems for which feature requests have been made. Linked problem pages contain the document of the problem and their relevant solutions. Obviously, we want to keep HTML as simple as possible. That means not everyone will get what they want. Having good documentation for the problems at hand will help all of us work out what is most important.

Guidelines

Before proposing a feature, please read Proposing features. If you want to add a feature request, start by copying the Problem Solving template page onto a new page and fill out as much information as you can.

You don't have to provide detailed answers for everything straight away. The most important information to provide at first is the problem description. Once we have detailed descriptions, use cases and an understanding of the limitations with existing markup, we can then begin to discuss the best way in which to address the problems and work out more of the more technical details.

Document Markup

DOM Scripting

Security

Other

This list of features needs to be sorted out. They've come from all the feedback provided on blogs over the past few weeks.

  • Don't render quotation marks around q elements.
  • Make form validation easier
    • required attribute
    • maxlength attribute for textarea
    • pattern attribute
    • min
    • max
  • New Form Controls
    • Search fields
    • Combo boxes
    • Date/Time
    • E-mail
    • Int
    • Long
    • Unsigned
    • Float
    • Number
    • Currency
    • URL
  • WYSIWIG Editor (contentEditable)
  • Placeholder attribute
  • Captions for images
  • Bring back the start and value attributes for ordered lists.
  • Bring back the menu element
  • Require XHTML-link syntax for HTML
  • Caption/label/list header for lists
  • Include the role attribute.
  • Allow href on all elements
  • Make it easier to mark up blocks of code
  • Allow block level elements inside paragraphs
  • “a tag that could hold "bad grammar" and not have any effect on the validation (sort of like a document.write from JavaScript) and would terminate all unclosed items at the end of the element (like TDs tend to do).”
  • blink!
  • Fix the object element.
  • Unify img, object, embed and iframe into a single element
  • Headers and footers
  • A mechanism to include content from an external source (e.g. include, perhaps like XInclude)
  • A corner element (presumably for making rounded corners)
  • Markup for advertisements
  • Easier column layouts
  • A foot element for containing scripts at the bottom of the page, or something to help deal with cross-browser load events.
  • Key Generation/Certificate management (The keygen element)