HTML5 on TV
summary
HTML5 on TVs delivers full JS features like typed arrays and h.264 playback but repeatedly fails at DOM and platform APIs: localStorage and session storage are tiny or wiped, cookies disabled, and only one hardware decoder may be available. Remote UX relies on spatial navigation and key constants (Up/Down/Left/Right/Enter plus optional colored buttons). Large libraries like jQuery crash apps; the remedy is microjs/vanilla JS and testing in the opportunity emulator with Opera Dragonfly remote debugging.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:02History of Opera on TV
- 7:05TV user experience
- 9:40Overscan and layout
- 12:13Navigation patterns
- 16:03Input and event handling
- 18:20CSS and media queries
- 20:40Performance and libraries
- 23:32HTML5 and storage limits
- 26:46Audio and video storage
- 27:45Testing and developer tools
- 32:14Architecture and conclusion
related talks
29mHTML5 JavaScript APIs
35mHTML5 APIs - The New Frontier
43mMake Friends and Influence People with HTML5
48mThe Immobile Web
40mWeb Applications of the Future
30mThe State of HTML5 - Inaugural Address
26mMobile HTML5: Device APIs and related APIs
37mBuzz It For Real ! ... the tortuous road to Mobile HTML5 Apps