Ideas for HTML5

November 14th, 2011 | Categories: Web Applications

These ideas are outcome of my experience in developing my project RichStyle.

A Unified Label Attribute

Think of using label="" as a unified naming attribute; as an alternative to all naming tags and attribute:

<caption> , <label>, <legend>, alt="", for="", title="", summary="".

Tile text (the mouseover-text) could be displayed using a CSS rule like this:

{ title: attr(label) | attr(accesskey) | attr(label) attr(accesskey) | none }

The standard way for label presentation is to use :before and :after pseudo elements.

Command Representation

<command> should have an href="" attribute (link attribute) as an optional attribute, since a command could be simply a link.

icon="" attribute should be deprecated in favor of CSS icon attribute, which , in turn, should have an additional value called glyph(), e.g.:

command.go_up {icon: glyph(↑)}

And just like <input>, command should accept text as a type beside “command”, “checkbox”, and “radio”:

<command type="text">

Think of “search” and “zoom” fields in a toolbar.

Time Representation

Time, as a tag, should be used as a part of a context in an article or so on, the purpose here is to give the developer enough flexibility in time presentation (time-zone, time format) using CSS.

For articles’ time-stamp, and any other embedded content like
audio, video, or image, there should be two attributes: published, and
modified (last-modification date).

time,
article:time {
	time-format: dd-mm-yyyy;
	time-zone: +5;
}

A “Window” Tag

Unlike Window object used in JavaScript, such a tag might be easily maintained and customized using CSS like this:

window {
	position: fixed;
	left: 50%;
	top: 50%;
	buttons: close || maximize || minimize;
}

Standardizing jQuery

jQuery is the most popular alternative to JavaScript, it’s a powerful “meta-language” tries to circumvent the raw-javascript limitations. I think this language should be standardized.

Isolating events from the the HTML code the way CSS does regarding presentation attributes should be enough reason for W3C to adopt it.

No comments yet.


9 - = two

Favicon Plugin made by Alesis