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.
Before proposing a feature, there are a number of questions you should try to answer.
- 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?
If you want to add a feature request, you should probably start by coping the Problem Solving template page on a new page and fill as much information as you can.
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
- New Form Controls
- Search fields
- Combo boxes
- 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
- 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)