WHATWG Wiki - User contributions [en]

Page thumbnail

2009-08-12T21:09:08Z

Criminal:

The idea to assign a thumbnail to the page.

== The problem ==
To get a thumbnail (screenshot) of the page, we need to use some 3rd party services, such as Alexa, Snapcasa etc. Problem is that they are too slow. These services add request of the thumbnail to the queue so you are unable to get the thumbnail of the page instantly. What's more, you become dependent on them.

== Use Case Description ==
* Page thumbnail in the search results
* Thumbnail in various community sites (such as [http://www.facebook.com])
* Link submit sites, like [http://www.digg.com]
* WEB browsers to display thumbs on home page or bookmarks
* Any other websites, that needs to display thumbnail of the page.

== Proposed Solutions ==

=== My Solution ===
Solution would be to add new type of link tag. As we know, to indicate the favicon of the page, we need to use the following code:

<code>
<link rel="icon" href="favicon.ico">
</code>

We could use similar code to add the name of the page thumbnail. Proposal would be to use the following code:

<code>
<link rel="thumb" href="thumb.png">
</code>

Having this tag in the page and screenshot of the page in file called thumb.png, we propose that we have thumbnail of our webpage and want other services/applications to use it.

=== New problem ===
There might be a problem, that people will start to abuse this tag. For example, they could upload picture, which is not related with page at all, and say that it is the thumbnail of the page.

==== Adoption ====
This solution would make a lot easier for developers to add thumbnail of the page function to web sites.

[[Category:Feature Request|empty Template]]

Page thumbnail

2009-08-12T21:02:03Z

Criminal:

The idea to assign a thumbnail to the page.

== The problem ==
To get a thumbnail (screenshot) of the page, we need to use some 3rd party services, such as Alexa, Snapcasa etc. Problem is that they are too slow. These services add request of the thumbnail to the queue so you are unable to get the thumbnail of the page instantly. What's more, you became dependent on them.

== Use Case Description ==
* Page thumbnail in the search results
* Thumbnail in various community sites (such as [http://www.facebook.com])
* Link submit sites, like [http://www.digg.com]
* WEB browsers to display thumbs on home page or bookmarks
* Any other sites, which wants to display thumbnail of the page.

== Proposed Solutions ==

=== My Solution ===
Solution would be to add new type of link tag. As we know, to indicate the favicon of the page, we need to use the following code:

<code>
<link rel="icon" href="favicon.ico">
</code>

We could use similar code to add the name of the page thumbnail. Proposal would be to use the following code:

<code>
<link rel="thumb" href="thumb.png">
</code>

Having this tag in the page and screenshot of the page in file called thumb.png, we propose that we have thumbnail of out pages and want other services/applications to use it.

=== New problem ===
There might be the problem, that people will start to abuse this tag. For example, they could upload picture, which is not related with page at all, and say that it is the thumbnail of the page.

==== Adoption ====
This solution would make a lot easier for developers to add thumbnail of the page function to web sites.

[[Category:Feature Request|empty Template]]

Feature Proposals

2009-08-12T21:00:44Z

Criminal: /* Document Markup */

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 [http://blog.whatwg.org/proposing-features 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 ==
* [[Image Caption]]
* [[Layout tables]]
* [[Drag'n'Drop Uploads]]
* [[New Vocabularies]], [[Constraints for New Vocabularies]]
* [[Generic Metadata Mechanisms]]
* [[Link Icons]]
* [[Page thumbnail]]

== DOM Scripting ==
* [[Text in Canvas]]

== Security ==
* [[Link Hashes]]
* [[Digital Signatures]]

== Other ==

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 <code>q</code> elements.
* Make form validation easier
** <code>required</code> attribute
** <code>maxlength</code> attribute for textarea
** <code>pattern</code> attribute
** <code>min</code>
** <code>max</code>
* New Form Controls
** Search fields
** Combo boxes
** Date/Time
** E-mail
** Int
** Long
** Unsigned
** Float
** Number
** Currency
** URL
* WYSIWIG Editor (<code>contentEditable</code>)
* Placeholder attribute
* Captions for images
* Bring back the <code>start</code> and <code>value</code> attributes for ordered lists.
* Bring back the <code>menu</code> element
* Require XHTML-link syntax for HTML
* Caption/label/list header for lists
* Include the <code>role</code> attribute.
* Allow <code>href</code> 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).”
* <code>blink</code>!
* Fix the <code>object</code> element.
* Unify <code>img</code>, <code>object</code>, </code>embed</code> and <code>iframe</code> into a single element
* Headers and footers
* A mechanism to include content from an external source (e.g. <code>include</code>, perhaps like XInclude)
* A <code>corner</code> element (presumably for making rounded corners)
* Markup for advertisements
* Easier column layouts
* 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 <code>keygen</code> element)

[[Category:Feature Request]]

Page thumbnail

2009-08-12T20:59:51Z

Criminal:

The idea to assign a thumbnail to the page.

== The problem ==
To get a thumbnail (screenshot) of the page, we need to use some 3rd party services, such as Alexa, Snapcasa etc. Problem is that they are to slow. These services add request of the thumbnail to the queue so you are unable to get the thumbnail of the page instantly. What's more, you became dependent on them.

== Use Case Description ==
* Page thumbnail in the search results
* Thumbnail in various community sites (such as [http://www.facebook.com])
* Link submit sites, like [http://www.digg.com]
* WEB browsers to display thumbs on home page or bookmarks
* Any other sites, which wants to display thumbnail of the page.

== Proposed Solutions ==

=== My Solution ===
Solution would be to add new type of link tag. As we know, to indicate the favicon of the page, we need to use the following code:

<code>
<link rel="icon" href="favicon.ico">
</code>

We could use similar code to add the name of the page thumbnail. Proposal would be to use the following code:

<code>
<link rel="thumb" href="thumb.png">
</code>

Having this tag in the page and screenshot of the page in file called thumb.png, we propose that we have thumbnail of out pages and want other services/applications to use it.

=== New problem ===
There might be the problem, that people will start to abuse this tag. For example, they could upload picture, which is not related with page at all, and say that it is the thumbnail of the page.

==== Adoption ====
This solution would make a lot easier for developers to add thumbnail of the page function to web sites.

[[Category:Feature Request|empty Template]]

Page thumbnail

2009-08-12T20:42:02Z

Criminal: New page: The idea to assign a thumbnail to the page. == The problem == To get a thumbnail (screenshot) of the page, we need to use some 3rd party services, such as Alexa, Snapcasa etc. Problem is ...

The idea to assign a thumbnail to the page.

== The problem ==
To get a thumbnail (screenshot) of the page, we need to use some 3rd party services, such as Alexa, Snapcasa etc. Problem is that they are to slow. These services add request of the thumbnail to the queue so you are unable to get the thumbnail of the page instantly. What's more, you became dependent on them.

== Use Case Description ==
* Page thumbnail in the search results
* Thumbnail in various community sites (such as [http://www.facebook.com])
* Link submit sites, like [http://www.digg.com]
* Any other sites, which wants to display thumbnail of the page.

== 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:Feature Request|empty Template]]