A rags to riches design/developer blog
Home About Twitter Press Projects Apps

What HTML5 Javascript2 and CSS3 should have been

Jun 30, 2010 7:09 PM

What HTML5 Javascript2 and CSS3 should have been

Published: Jun 30, 2010 7:09 PM

With all this fuss over what HTML5 should be like, I had some thoughts on what I think HTML5 JavaScript 2 and CSS3 should include.  Some of these features are already in some browsers, extensions or plugins.  It would be nice if all new browsers supported all these features.

HTML5

  • DRM – digital rights management
  • new Tags: web camera, microphone, VOIP, IsBot, API, WYSIWYG, charts, volume, target audience, website  rating
  • new UI controls – better form controls, treeview, picture  listbox, calendar, OS treeview file browser, active directory/LDAP
  • multiscreen support
  • text/voice recognition
  • video/audio playback control toolbar
  • video captioning
  • auto complete, spell check – with dictionary referencing
  • video conferencing
  • better accessibility
  • browser transparency
  • out of browser support
  • tag attributes – tag anything
  • better keyboard shortcuts
  • monitor control – flip display, full screen multiple screens
  • local storage – like a virtual drive
  • audio/video timeline playback – stop background music and Flash audio  from playing from the beginning on each page load.  I love how Netflix uses Silverlight to restart my movie when I return to the page.  It should be that way for audio/video.

JavaScript 2.0

  • client-side database
  • peer to peer
  • GPU hardware acceleration
  • multi-core support
  • memory/CPU capping – a debug for developers to keep scripts from memory leaks
  • new events: touch, gesture, broken links, accelerator (axis/tilt), voice, handwriting, video gesture
  • built in form validation
  • multi-lingual support
  • scheduled batch scripting – like cron jobs
  • image/video editing
  • encrypted cookie/session security
  • drag/drop between peer to peer remote browser sessions or cloud storage
  • built-in screen snapshot or video screen capture
  • local/offline caching – I use to save webpage as mht single files, but it would be nice to have a cache timeline you can rewind to see how a webpage has changed
  • GEO location
  • bandwidth speed detection

CSS3

  • web fonts – load a font from your web server, like an image, and it looks the same in EVERY browser
  • smooth fonts and picture rotation
  • image/video watermarking
  • style the appearance of the browser – branding
  • 3D – page curls, paper tear affects, post-its, pattern overlays, 3D fonts, etc for crazy creativity
  • erasing – on touch screens, wiping parts of webpage you’re not interesting in viewing.  Not just a “display: none;”, but as detailed as erasing portions of elements, like making the letter O look like the letter C.  Of course local storage would keep it that way unless the page changes.
  • timeline animation – for things like Flash tweens
  • monitor display resolution/bandwidth detection to auto scale for low resolution resources
  • pointer manipulation – change the click area size for touch displays and change the shape of the click size (circle, square, triangle or a drawn line)
  • change mouse cursor for multiple mouse pointers used on the same device
  • color/transparency gradients
  • sound effect properties for elements
  • finger/pen drawing recognition – it would be cool on bigger touch devices to recognize the finger print (or pen serial number) then draw a different color line respectively
  • pen brushes – different paint/pen brush heads for different strokes. Highlighter, water color brush, charcoal
  • surround sound properties

Even with all these features that could be added to HTML5, JavaScript 2.0 and CSS3, there will always be something left out that browser plugins will accomplish (Flash/Silverlight/QuickTime).  I hope this opened your mind to how functional the open web could be.