Then I came across something new. The CANVAS element. New in the Web Application 1.0 Specification that describes the successor to HTML4 and XHTML1. A specification that browsers like Firefox, Safari and Opera take their lead from. And perhaps Internet Explorer as well???
Web Application 1.0 Specification
A little citation from the Web App specification:
have managed to base entire businesses on them. What is required are
extensions to these technologies to provide much-needed features such as:
- Native pop-up menus and context menus.
- Inline markup for pop-up windows, for example for dialog boxes or tool
palettes, so that dialogs need not be defined in separate files.
- Command updating: applications that have several access points for the
same feature, for instance a menu item and a tool-bar button, would
benefit from having to disable such commands only once, instead of having
to keep each access point synchronized with the feature’s availability at
all times. Similarly menu items or tool-bar buttons that represent a
toggle state could automatically stay synchronized whenever toggled.
- Server-sent events: triggering DOM3 Events from the server-side, for
example for tickers or status updates.
- Client-server communications methods that do not require page loads,
enabling on-demand data retrieval (where the UA automatically fetches
data from the server as required), remote procedure calls (where script
can invoke code on the server side and get an XML fragment in return),
- More device-independent DOM events: The DOM event set needs
device-independent events, such as events that fire when a button or link
is activated, whether via the mouse or the keyboard.
DOMActivateis a start, but it lacks equivalent HTML
attributes, and additional events may be needed.