Weird Browsers @ London Ajax

Now that everybody builds responsive sites and mobile has become the new normal, 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 console handle your websites and are e-readers really capable of browsing the web?

Transcript

1. ?weird browsers? london ajax — januari 12th 2016 @html5test
4. 400 
 Safari 9 521 
 Chrome 47 468 
 Firefox 43 555 0 desktop browsers results on html5test.com 458 
 Edge 13
5. 400 
 Safari 9 468 
 Firefox 43 555 0 desktop browsers results on html5test.com 521 
 Chrome 47 458 
 Edge 13
6. 402 
 Edge 12 400 
 Safari 9 521 
 Chrome 47 468 
 Firefox 43 555 0 desktop browsers results on html5test.com 16 
 Internet Explorer 6 458 
 Edge 13 336 
 Internet Explorer 11
8. ?weird browsers?
9. browsers and devices that do not
 adhere to current expectations
10. if ('ontouchstart' in window) { element.addEventListener(‘touchstart’, function(e) {
 ...
 }); }
 else {
 element.addEventListener(‘click’, function(e) {
 ...
 }); }
12. ?weird browsers?
13. ?weird browsers?
14. game consoles
15. portable game consoles
16. smart tvs
17. e-readers
18. smartwatches
19. photo cameras
20. cars Andre Jay Meissner
22. smart tvs, set-top boxes and consoles
23. “big screen browsers”
25. television browsers are pretty good the last generation of television sets use operating systems that originate from mobile
26. 418 
 LG WebOS 281 
 Google TV 238 
 LG Netcast 465 
 Samsung Tizen 449 
 Opera Devices 301 
 Panasonic
 Viera smart tv results on html5test.com 555 0 414 
 Panasonic
 Firefox OS 407 
 Samsung
 2014
27. 328 
 Playstation 4 53 
 Playstation 3 309 
 Playstation TV 98 
 Xbox 360 286 
 Xbox One 311 
 Wii U 66 
 Wii 555 0 console results on html5test.com
28. 328 
 Playstation 4 53 
 Playstation 3 309 
 Playstation TV 98 
 Xbox 360 286 
 Xbox One 311 
 Wii U 66 
 Wii 555 0 console results on html5test.com 426 
 Xbox One with Edge
30. 1 control
31. the biggest challenge of 
 of television browsers
32. navigation (without mouse or touchscreen)
33. d-pad
34. navigation with the d-pad
35. but it can be worse: moving the cursor with the arrow keys
36. alternatives
37. analog controllers
38. remotes with trackpad
39. remotes with airmouse
40. second screen
41. many manufacturers also create apps for controlling the smart tv, console or set-top box
44. text input (without keyboard)
45. d-pads
46. text input with the d-pad
47. alternatives
48. remotes with keyboards
49. wireless keyboards
50. and apps
52. gesture control (throw your hands up in the air,
 and wave ’em like you just don’t care)
53. navigation with gesture control
54. can we control these input methods 
 directly from javascript?
55. the d-pad maybe
56. keyboard events window.addEventListener("keypress", function(e) {
 e.preventDefault(); // no navigation
 ... }); 1
57. the gamepad maybe
58. the gamepad api var gamepads = navigator.getGamepads();
 for (var i = 0; i < gamepads.length; i++) {
 ...
 } 1
59. wii u api window.setInterval(function() {
 var state = window.wiiu.gamepad.update();
 ... }, 100); 2
60. the webcam maybe
61. the getusermedia api navigator.getUserMedia(
 { audio: true, video: { width: 1280, height: 720 } },
 function(stream) { ... },
 function(error) { ... }
 ); 1
62. 2 the difference between 
 a television and a monitor
63. overscan (let’s make it a bit more complicated)
64. due to historical reasons televisions will 
 not show the borders of the image
65. the television enlarges all images 
 from the hdmi input by 5% 1920 pixels
66. the television enlarges all images 
 from the hdmi input by 5% 1920 pixels
67. the image is then cropped to 
 1920 by 1080 pixels
68. the image is then cropped to 
 1920 by 1080 pixels
69. overscan causes blurry output +5%
70. solution 1 overscan correction
71. the browser does not use
 the edges of the image 1920 pixels
72. the television will enlarge 
 the image by 5% 1920 pixels
73. and the content is now fully visible, the unused border is cropped out of the final image
74. but not every television set enlarges the 
 image by exactly 5%, this can vary between manufacturers and models
75. configure the correct overscan correction 
 in the system preferences
76. the playstation 4 will always show the browser without overscan correction in full screen mode
77. the playstation 4 will always show the browser without overscan correction in full screen mode
78. solution 2 no overscan
79. it is possible to disable overscan 
 on many television sets ‘screen fit’, ‘pixel perfect’ or ‘just scan’
80. the playstation 3 always shows the 
 browser with overscan correction
81. the viewport (i really need some aspirin!)
82. the visual viewport determines which part of the website will be visible measured in 
 device pixels the visual viewport
83. the visual viewport determines which part of the website will be visible measured in 
 device pixels the visual viewport
84. the visual viewport the visual viewport determines which part of the website will be visible measured in 
 device pixels
85. the layout viewport the layout viewport determines the width in css pixels on which the site will be rendered
86. the layout viewport the layout viewport determines the width in css pixels on which the site will be rendered
87. the layout viewport the layout viewport determines the width in css pixels on which the site will be rendered
88. the default layout viewport is different on 
 every smart tv, console or set-top box between 800 and 1920 css pixels
89. 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
90. complication:
 meta viewport is not supported it is not possible to get the same layout viewport 
 width in all of the different browsers
91. complication:
 device pixel ratio is not supported there is no proper way to show images with the same resolution as the physical screen
92. nintendo wii 800 pixels
93. nintendo wii u 980 pixels
94. lg webos 960 pixels
95. microsoft xbox 360 1041 of 1050 pixels
96. microsoft xbox one 1200 of 1236 pixels
97. sony playstation 3 1824 pixels
98. sony playstation 4 1920 pixels
99. 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
100. device pixels != device pixels (of course not)
101. 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
102. 3 distance to the screen
103. “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
104. responsive design the size of the contents is determined 
 by the width of the viewport
105. use percentages for positioning .left { width: 60%; }
 .right { left: 60%; width: 40%; } 1
106. base the fontsize on the viewport document.body.style.fontSize = 
 ((window.innerWidth / 1920) * 300) + '%'; 2
107. or maybe use viewport units – with polyfill body { font-size: 3vw; }
 .left { width: 60vw; height: 100vh; }
 .right { width: 40vw; height: 100vh; } 3
108. use a safe margin around the contents body {
 padding: 5%;
 } 4
109. youtube tv website
110. identifying smart tv’s (css for televisions)
111. css media types @media tv {
 body {
 font-size: 300%; } } 1 ×
112. css media types all television browsers use the 
 css media type ‘screen’ 1
113. screen size if (screen.width == 1920 && screen.height == 1080) {
 document.body.className += " television";
 } 2 ×
114. screen size monitors and phones often use 
 hd resolutions, television browsers often use other resolutions 2
115. useragent sniffing if (navigator.userAgent.search(/TV/i) >= 0) {
 document.body.className += " television";
 } 3 ×
116. 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
117. 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
118. 4 be careful with
 feature detection
119. “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/
120. if (!!navigator.geolocation) { navigator.geolocation.getCurrentPosition(
 success, failure
 ); }
 else {
 // alternative
 }
121. 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
122. 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
123. is there a future for web apps 
 on the big screen?
125. the new apple tv does not ship 
 with a browser by default
126. android tv does not ship 
 with a browser by default
128. e-readers
129. e-reader results on html5test.com 555 0 196 
 Pocketbook 280 
 Kobo 157 
 Sony Reader 52 
 Kindle 3 187 
 Kindle Touch
130. infrared touch screen
131. led’s sensors
132. 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
133. e-ink screens (slow, slower, slowest)
134. microscopic electrostatic charged balls
135. microscopic electrostatic charged balls + – – +
136. + – – + microscopic electrostatic charged balls
137. microscopic electrostatic charged balls
139. maybe css animations and transitions 
 weren’t such a great idea after all
140. two completely different colors can look 
 exactly the same in black and white
141. two completely different colors can look 
 exactly the same in black and white
142. identifying e-readers (css for e-ink screens)
143. css monochrome mediaquery @media (monochrome) {
 ... } 1 ×
144. css monochrome mediaquery all tested e-readers act like 
 they have a color screen 1
145. useragent sniffing there is no universal marker in the useragent string, but we can recognise individual manufacturers and models 2
147. portable consoles
148. 66 
 Nintendo DSi 309 
 Sony PlayStation Vita 311 
 New Nintendo 3DS portable console results html5test.com 555 0 80 
 Nintendo 3DS
150. two screens (surprisingly normal)
151. 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
152. 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
153. 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
154. 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
157. ?weird browsers!
158. “We cannot predict future behavior 
 from a current experience that sucks” 
 – Jason Grigsby http://blog.cloudfour.com/on-the-device-context-continuum/
159. but wait…
160. browsers! weird
161. browsers! weird
162. browsers! browsers browsers browser browsers! browsers rowsers browsers browsers brows browsers wsers! browsers
163. one arm arm injury new parent permanent situational https://www.microsoft.com/en-us/design/practice
165. thank you niels leenheer
 @html5test