Slide 1

Slide 1 text

?weird browsers? london ajax — januari 12th 2016 @html5test

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

400 
 Safari 9 521 
 Chrome 47 468 
 Firefox 43 555 0 desktop browsers results on html5test.com 458 
 Edge 13

Slide 5

Slide 5 text

400 
 Safari 9 468 
 Firefox 43 555 0 desktop browsers results on html5test.com 521 
 Chrome 47 458 
 Edge 13

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

?weird browsers?

Slide 9

Slide 9 text

browsers and devices that do not
 adhere to current expectations

Slide 10

Slide 10 text

if ('ontouchstart' in window) { element.addEventListener(‘touchstart’, function(e) {
 ...
 }); }
 else {
 element.addEventListener(‘click’, function(e) {
 ...
 }); }

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

?weird browsers?

Slide 13

Slide 13 text

?weird browsers?

Slide 14

Slide 14 text

game consoles

Slide 15

Slide 15 text

portable game consoles

Slide 16

Slide 16 text

smart tvs

Slide 17

Slide 17 text

e-readers

Slide 18

Slide 18 text

smartwatches

Slide 19

Slide 19 text

photo cameras

Slide 20

Slide 20 text

cars Andre Jay Meissner

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

smart tvs, set-top boxes and consoles

Slide 23

Slide 23 text

“big screen browsers”

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

television browsers are pretty good the last generation of television sets use operating systems that originate from mobile

Slide 26

Slide 26 text

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

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

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

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

1 control

Slide 31

Slide 31 text

the biggest challenge of 
 of television browsers

Slide 32

Slide 32 text

navigation (without mouse or touchscreen)

Slide 33

Slide 33 text

d-pad

Slide 34

Slide 34 text

navigation with the d-pad

Slide 35

Slide 35 text

but it can be worse: moving the cursor with the arrow keys

Slide 36

Slide 36 text

alternatives

Slide 37

Slide 37 text

analog controllers

Slide 38

Slide 38 text

remotes with trackpad

Slide 39

Slide 39 text

remotes with airmouse

Slide 40

Slide 40 text

second screen

Slide 41

Slide 41 text

many manufacturers also create apps for controlling the smart tv, console or set-top box

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

text input (without keyboard)

Slide 45

Slide 45 text

d-pads

Slide 46

Slide 46 text

text input with the d-pad

Slide 47

Slide 47 text

alternatives

Slide 48

Slide 48 text

remotes with keyboards

Slide 49

Slide 49 text

wireless keyboards

Slide 50

Slide 50 text

and apps

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

gesture control (throw your hands up in the air,
 and wave ’em like you just don’t care)

Slide 53

Slide 53 text

navigation with gesture control

Slide 54

Slide 54 text

can we control these input methods 
 directly from javascript?

Slide 55

Slide 55 text

the d-pad maybe

Slide 56

Slide 56 text

keyboard events window.addEventListener("keypress", function(e) {
 e.preventDefault(); // no navigation
 ... }); 1

Slide 57

Slide 57 text

the gamepad maybe

Slide 58

Slide 58 text

the gamepad api var gamepads = navigator.getGamepads();
 for (var i = 0; i < gamepads.length; i++) {
 ...
 } 1

Slide 59

Slide 59 text

wii u api window.setInterval(function() {
 var state = window.wiiu.gamepad.update();
 ... }, 100); 2

Slide 60

Slide 60 text

the webcam maybe

Slide 61

Slide 61 text

the getusermedia api navigator.getUserMedia(
 { audio: true, video: { width: 1280, height: 720 } },
 function(stream) { ... },
 function(error) { ... }
 ); 1

Slide 62

Slide 62 text

2 the difference between 
 a television and a monitor

Slide 63

Slide 63 text

overscan (let’s make it a bit more complicated)

Slide 64

Slide 64 text

due to historical reasons televisions will 
 not show the borders of the image

Slide 65

Slide 65 text

the television enlarges all images 
 from the hdmi input by 5% 1920 pixels

Slide 66

Slide 66 text

the television enlarges all images 
 from the hdmi input by 5% 1920 pixels

Slide 67

Slide 67 text

the image is then cropped to 
 1920 by 1080 pixels

Slide 68

Slide 68 text

the image is then cropped to 
 1920 by 1080 pixels

Slide 69

Slide 69 text

overscan causes blurry output +5%

Slide 70

Slide 70 text

solution 1 overscan correction

Slide 71

Slide 71 text

the browser does not use
 the edges of the image 1920 pixels

Slide 72

Slide 72 text

the television will enlarge 
 the image by 5% 1920 pixels

Slide 73

Slide 73 text

and the content is now fully visible, the unused border is cropped out of the final image

Slide 74

Slide 74 text

but not every television set enlarges the 
 image by exactly 5%, this can vary between manufacturers and models

Slide 75

Slide 75 text

configure the correct overscan correction 
 in the system preferences

Slide 76

Slide 76 text

the playstation 4 will always show the browser without overscan correction in full screen mode

Slide 77

Slide 77 text

the playstation 4 will always show the browser without overscan correction in full screen mode

Slide 78

Slide 78 text

solution 2 no overscan

Slide 79

Slide 79 text

it is possible to disable overscan 
 on many television sets ‘screen fit’, ‘pixel perfect’ or ‘just scan’

Slide 80

Slide 80 text

the playstation 3 always shows the 
 browser with overscan correction

Slide 81

Slide 81 text

the viewport (i really need some aspirin!)

Slide 82

Slide 82 text

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

Slide 83

Slide 83 text

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

Slide 84

Slide 84 text

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

Slide 85

Slide 85 text

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

Slide 86

Slide 86 text

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

Slide 87

Slide 87 text

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

Slide 88

Slide 88 text

the default layout viewport is different on 
 every smart tv, console or set-top box between 800 and 1920 css pixels

Slide 89

Slide 89 text

it is possible to change the width of the 
 layout viewport with the ‘meta viewport’ tag physical device pixels device scale factor

Slide 90

Slide 90 text

complication:
 meta viewport is not supported it is not possible to get the same layout viewport 
 width in all of the different browsers

Slide 91

Slide 91 text

complication:
 device pixel ratio is not supported there is no proper way to show images with the same resolution as the physical screen

Slide 92

Slide 92 text

nintendo wii 800 pixels

Slide 93

Slide 93 text

nintendo wii u 980 pixels

Slide 94

Slide 94 text

lg webos 960 pixels

Slide 95

Slide 95 text

microsoft xbox 360 1041 of 1050 pixels

Slide 96

Slide 96 text

microsoft xbox one 1200 of 1236 pixels

Slide 97

Slide 97 text

sony playstation 3 1824 pixels

Slide 98

Slide 98 text

sony playstation 4 1920 pixels

Slide 99

Slide 99 text

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

Slide 100

Slide 100 text

device pixels != device pixels (of course not)

Slide 101

Slide 101 text

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

Slide 102

Slide 102 text

3 distance to the screen

Slide 103

Slide 103 text

“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

Slide 104

Slide 104 text

responsive design the size of the contents is determined 
 by the width of the viewport

Slide 105

Slide 105 text

use percentages for positioning .left { width: 60%; }
 .right { left: 60%; width: 40%; } 1

Slide 106

Slide 106 text

base the fontsize on the viewport document.body.style.fontSize = 
 ((window.innerWidth / 1920) * 300) + '%'; 2

Slide 107

Slide 107 text

or maybe use viewport units – with polyfill body { font-size: 3vw; }
 .left { width: 60vw; height: 100vh; }
 .right { width: 40vw; height: 100vh; } 3

Slide 108

Slide 108 text

use a safe margin around the contents body {
 padding: 5%;
 } 4

Slide 109

Slide 109 text

youtube tv website

Slide 110

Slide 110 text

identifying smart tv’s (css for televisions)

Slide 111

Slide 111 text

css media types @media tv {
 body {
 font-size: 300%; } } 1 ×

Slide 112

Slide 112 text

css media types all television browsers use the 
 css media type ‘screen’ 1

Slide 113

Slide 113 text

screen size if (screen.width == 1920 && screen.height == 1080) {
 document.body.className += " television";
 } 2 ×

Slide 114

Slide 114 text

screen size monitors and phones often use 
 hd resolutions, television browsers often use other resolutions 2

Slide 115

Slide 115 text

useragent sniffing if (navigator.userAgent.search(/TV/i) >= 0) {
 document.body.className += " television";
 } 3 ×

Slide 116

Slide 116 text

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

Slide 117

Slide 117 text

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

Slide 118

Slide 118 text

4 be careful with
 feature detection

Slide 119

Slide 119 text

“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/

Slide 120

Slide 120 text

if (!!navigator.geolocation) { navigator.geolocation.getCurrentPosition(
 success, failure
 ); }
 else {
 // alternative
 }

Slide 121

Slide 121 text

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

Slide 122

Slide 122 text

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

Slide 123

Slide 123 text

is there a future for web apps 
 on the big screen?

Slide 124

Slide 124 text

No content

Slide 125

Slide 125 text

the new apple tv does not ship 
 with a browser by default

Slide 126

Slide 126 text

android tv does not ship 
 with a browser by default

Slide 127

Slide 127 text

No content

Slide 128

Slide 128 text

e-readers

Slide 129

Slide 129 text

e-reader results on html5test.com 555 0 196 
 Pocketbook 280 
 Kobo 157 
 Sony Reader 52 
 Kindle 3 187 
 Kindle Touch

Slide 130

Slide 130 text

infrared touch screen

Slide 131

Slide 131 text

led’s sensors

Slide 132

Slide 132 text

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

Slide 133

Slide 133 text

e-ink screens (slow, slower, slowest)

Slide 134

Slide 134 text

microscopic electrostatic charged balls

Slide 135

Slide 135 text

microscopic electrostatic charged balls + – – +

Slide 136

Slide 136 text

+ – – + microscopic electrostatic charged balls

Slide 137

Slide 137 text

microscopic electrostatic charged balls

Slide 138

Slide 138 text

No content

Slide 139

Slide 139 text

maybe css animations and transitions 
 weren’t such a great idea after all

Slide 140

Slide 140 text

two completely different colors can look 
 exactly the same in black and white

Slide 141

Slide 141 text

two completely different colors can look 
 exactly the same in black and white

Slide 142

Slide 142 text

identifying e-readers (css for e-ink screens)

Slide 143

Slide 143 text

css monochrome mediaquery @media (monochrome) {
 ... } 1 ×

Slide 144

Slide 144 text

css monochrome mediaquery all tested e-readers act like 
 they have a color screen 1

Slide 145

Slide 145 text

useragent sniffing there is no universal marker in the useragent string, but we can recognise individual manufacturers and models 2

Slide 146

Slide 146 text

No content

Slide 147

Slide 147 text

portable consoles

Slide 148

Slide 148 text

66 
 Nintendo DSi 309 
 Sony PlayStation Vita 311 
 New Nintendo 3DS portable console results html5test.com 555 0 80 
 Nintendo 3DS

Slide 149

Slide 149 text

No content

Slide 150

Slide 150 text

two screens (surprisingly normal)

Slide 151

Slide 151 text

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

Slide 152

Slide 152 text

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

Slide 153

Slide 153 text

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

Slide 154

Slide 154 text

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

Slide 155

Slide 155 text

No content

Slide 156

Slide 156 text

No content

Slide 157

Slide 157 text

?weird browsers!

Slide 158

Slide 158 text

“We cannot predict future behavior 
 from a current experience that sucks” 
 – Jason Grigsby http://blog.cloudfour.com/on-the-device-context-continuum/

Slide 159

Slide 159 text

but wait…

Slide 160

Slide 160 text

browsers! weird

Slide 161

Slide 161 text

browsers! weird

Slide 162

Slide 162 text

browsers! browsers browsers browser browsers! browsers rowsers browsers browsers brows browsers wsers! browsers

Slide 163

Slide 163 text

one arm arm injury new parent permanent situational https://www.microsoft.com/en-us/design/practice

Slide 164

Slide 164 text

No content

Slide 165

Slide 165 text

thank you niels leenheer
 @html5test