Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Weird Browsers @ Webworker NRW

Weird Browsers @ Webworker NRW

Want to see a video of an earlier version of this presentation:
https://www.youtube.com/watch?v=ojGIva5801I

Ever since the web has conquered the desktop, people have been trying to bring it to other devices. Everything from microwaves and fridges to cars. Sometimes these experiments were a success and other times they were complete failures. What are the current frontiers for the web? Are there still any weird browsers left?

The latest generation of Smart TV’s run on the same operating systems as our mobile devices. How weird can these browsers be? Perhaps Smart TV’s aren’t as smart as we all would like to think. But there are more weird browsers. How do game consoles like the Xbox One handle your websites and are e-readers really capable of browsing the web? And are the browsers in VR headsets like the Hololens any good? I will try to give an overview of all the problems you are going to face when you want to make your site work on these weird browsers.

Niels Leenheer

August 11, 2016
Tweet

More Decks by Niels Leenheer

Other Decks in Technology

Transcript

  1. 370 
 Safari 9.1 492 
 Chrome 51 461 


    Firefox 48 555 0 desktop browsers results on html5test.com 460 
 Edge 14
  2. 555 0 desktop browsers results on html5test.com 370 
 Safari

    9.1 492 
 Chrome 51 461 
 Firefox 48 460 
 Edge 14
  3. 377 
 Edge 12 555 0 desktop browsers results on

    html5test.com 19 
 Internet Explorer 6 312 
 Internet Explorer 11 370 
 Safari 9.1 492 
 Chrome 51 461 
 Firefox 48 460 
 Edge 14 433 
 Edge 13
  4. television browsers are pretty good the last generation of television

    sets use operating systems that originate from mobile
  5. 427 
 LG WebOS 218 
 Google TV 199 


    LG Netcast 490 
 Samsung Tizen 478 
 Opera Devices 261 
 Panasonic
 Viera smart tv results on html5test.com 555 0 371 
 Panasonic
 Firefox OS 352 
 Samsung
 2014
  6. 289 
 Playstation 4 57 
 Playstation 3 258 


    Playstation TV 108 
 Xbox 360 256 
 Wii U 65 
 Wii 555 0 console results on html5test.com 401 
 Xbox One with Edge
  7. gesture control (throw your hands up in the air,
 and

    wave ’em like you just don’t care)
  8. the gamepad api var gamepads = navigator.getGamepads();
 for (var i

    = 0; i < gamepads.length; i++) {
 ...
 } 1
  9. the getusermedia api navigator.getUserMedia(
 { audio: true, video: { width:

    1280, height: 720 } },
 function(stream) { ... },
 function(error) { ... }
 ); 1
  10. and the content is now fully visible, the unused border

    is cropped out of the final image
  11. but not every television set enlarges the 
 image by

    exactly 5%, this can vary between manufacturers and models
  12. it is possible to disable overscan 
 on many television

    sets ‘screen fit’, ‘pixel perfect’ or ‘just scan’
  13. the visual viewport determines which part of the website will

    be visible measured in 
 device pixels the visual viewport
  14. the visual viewport determines which part of the website will

    be visible measured in 
 device pixels the visual viewport
  15. the visual viewport the visual viewport determines which part of

    the website will be visible measured in 
 device pixels
  16. the layout viewport the layout viewport determines the width in

    css pixels on which the site will be rendered
  17. the layout viewport the layout viewport determines the width in

    css pixels on which the site will be rendered
  18. the layout viewport the layout viewport determines the width in

    css pixels on which the site will be rendered
  19. the default layout viewport is different on 
 every smart

    tv, console or set-top box between 800 and 1920 css pixels
  20. it is possible to change the width of the 


    layout viewport with the ‘meta viewport’ tag <meta name="viewport" content=“width=device-width"> <meta name="viewport" content="width=1024"> physical device pixels device scale factor
  21. complication:
 meta viewport is not supported it is not possible

    to get the same layout viewport 
 width in all of the different browsers
  22. complication:
 device pixel ratio is not supported there is no

    proper way to show images with the same resolution as the physical screen
  23. Nintendo Wii 800 LG WebOS 960 Nintendo Wii U 980

    Philips 2014 series 980 Google TV 1024 Playstation TV 1024 Samsung Tizen 1024 Xbox 360 1051 Xbox One 1200 LG Netcast 1226 Panasonic Viera 1256 Opera Devices 1280 Samsung 2014 series 1280 Panasonic Firefox OS 1536 Playstation 3 1824 Playstation 4 1920
  24. sometimes devices pixels are not 
 physical devices pixels, but

    virtual device pixels the browser renders in a lower resolution 
 which is upscaled to the resolution of the display
  25. “Make fonts and graphics on the site larger to account

    for viewing distance. People sit proportionally farther from a TV than from a computer monitor of the same size.” 
 – Internet Explorer for Xbox One Developer Guide https://msdn.microsoft.com/en-us/library/dn532261(v=vs.85).aspx
  26. or maybe use viewport units – with polyfill body {

    font-size: 3vw; }
 .left { width: 60vw; height: 100vh; }
 .right { width: 40vw; height: 100vh; } 3
  27. screen size if (screen.width == 1920 && screen.height == 1080)

    {
 document.body.className += " television";
 } 2 ×
  28. screen size monitors and phones often use 
 hd resolutions,

    television browsers often use other resolutions 2
  29. useragent sniffing not all smart tv’s are recognisable Mozilla/5.0 (X11;

    Linux; ko-KR) 
 AppleWebKit/534.26+ (KHTML, like Gecko) 
 Version/5.0 Safari/534.26+ 3
  30. couch mode the only reliable way to optimise a website

    
 for television is to make two different websites… or give the user the ability to switch on 
 couch mode 4
  31. “Basically every feature that talks to the 
 operating system

    or hardware, is suspect.” 
 – Me http://blog.html5test.com/2015/08/the-problems-with-feature-detection/
  32. if (!!navigator.geolocation) { navigator.geolocation.getCurrentPosition(
 success, failure
 ); } 1 failure

    is called with a “permission denied” error code 2 no callback at all to success or failure
  33. if (!!navigator.geolocation) { navigator.geolocation.getCurrentPosition(
 success, failure
 ); } 3 success

    is called with longitude = 0 and latitude = 0 4 success is called with the coordinates of 
 Mountain View, USA
  34. e-reader results on html5test.com 555 0 154 
 Pocketbook 280

    
 Kobo 147 
 Sony Reader 152 
 Kindle Touch
  35. mouse events down/up move touch events amazon kindle touch yes

    pocketbook basic touch yes kobo glow yes yes sony reader yes yes 1 finger
  36. useragent sniffing there is no universal marker in the useragent

    string, but we can recognise individual manufacturers and models 2
  37. 258 
 Sony PlayStation Vita 257 
 New Nintendo 3DS

    portable console results html5test.com 555 0 83 
 Nintendo 3DS 65 
 Nintendo DSi
  38. a dual visual viewport
 (the bottom one is the primary

    visual viewport) 3d screen, but only 2d is supported in the browser resistive 
 touch screen
  39. a dual visual viewport
 (the bottom one is the primary

    visual viewport) 3d screen, but only 2d is supported in the browser resistive 
 touch screen
  40. a dual visual viewport
 (the bottom one is the primary

    visual viewport) 3d screen, but only 2d is supported in the browser resistive 
 touch screen
  41. a dual visual viewport
 (the bottom one is the primary

    visual viewport) 3d screen, but only 2d is supported in the browser resistive 
 touch screen
  42. “We cannot predict future behavior 
 from a current experience

    that sucks” 
 – Jason Grigsby http://blog.cloudfour.com/on-the-device-context-continuum/