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 "Link prerender events"

From WHATWG Wiki
Jump to: navigation, search
(gphemsley please give gavinp user rights!)
 
(copy Proposal template)
Line 1: Line 1:
 +
This is an empty page that describes what should be documented about a problem and the different solutions proposed to address it. Feel free to copy this template to when creating a new page.
 +
 +
:''Brief description of the problem to solve.''
 +
 +
== Use Case Description ==
 +
''Complete description of the use case.''
 +
 +
=== Current Limitations ===
 +
''Explanation of why the current markup is insufficient.''
 +
 +
=== Current Usage and Workarounds ===
 +
''Some evidence that this feature is desperately needed on the web.  You may provide a separate examples page for listing these.''
 +
 +
=== Benefits ===
 +
 +
''Explanation of how and why new markup would be useful.''
 +
 +
=== Requests for this Feature ===
 +
 +
* <cite>[http://example.com Source]</cite> <blockquote><p>I would like this feature ...</p></blockquote>
 +
 +
== Proposed Solutions ==
 +
 +
=== My Solution ===
 +
:''Brief description of the solution and of how it address the problem at hand.''
 +
 +
==== Processing Model ====
 +
:''Explanation of the changes introduced by this solution. It explains how the document is processed, and how errors are handled. This should be very clear, including things such as event timing if the solution involves events, how to create graphs representing the data in the case of semantic proposals, etc.''
 +
 +
==== Limitations ====
 +
:''Cases not covered by this solution in relation to the problem description; other problems with this solution, if any.''
 +
 +
==== Implementation ====
 +
:''Description of how and why browser vendors would take advantage of this feature.''
 +
 +
==== Adoption ====
 +
:''Reasons why page authors would use this solution.''
  
 
[[Category:Proposals]]
 
[[Category:Proposals]]

Revision as of 21:42, 7 November 2012

This is an empty page that describes what should be documented about a problem and the different solutions proposed to address it. Feel free to copy this template to when creating a new page.

Brief description of the problem to solve.

Use Case Description

Complete description of the use case.

Current Limitations

Explanation of why the current markup is insufficient.

Current Usage and Workarounds

Some evidence that this feature is desperately needed on the web. You may provide a separate examples page for listing these.

Benefits

Explanation of how and why new markup would be useful.

Requests for this Feature

  • Source

    I would like this feature ...

Proposed Solutions

My Solution

Brief description of the solution and of how it address the problem at hand.

Processing Model

Explanation of the changes introduced by this solution. It explains how the document is processed, and how errors are handled. This should be very clear, including things such as event timing if the solution involves events, how to create graphs representing the data in the case of semantic proposals, etc.

Limitations

Cases not covered by this solution in relation to the problem description; other problems with this solution, if any.

Implementation

Description of how and why browser vendors would take advantage of this feature.

Adoption

Reasons why page authors would use this solution.