Weird Browsers

A presentation at NLHTML5 in October 2015 in Amsterdam, Netherlands by Niels Leenheer

Slide 1

Slide 1

?weird browsers? nlhtml5 — october 15th 2015

Slide 2

Slide 2

Slide 3

Slide 3

Slide 4

Slide 4

this slide is inspirational as fuck

Slide 5

Slide 5

browser compatibility tester

Slide 6

Slide 6

Slide 7

Slide 7

402 Edge 12 400 521 Safari 9 Chrome 45 0 555 466 Firefox 41 desktop browsers results on html5test.com

Slide 8

Slide 8

402 Edge 12 400 521 Safari 9 Chrome 45 0 555 466 Firefox 41 desktop browsers results on html5test.com

Slide 9

Slide 9

402 Edge 12 458 Edge 13 400 521 Safari 9 Chrome 45 0 555 16 336 466 Internet Explorer 6 Internet Explorer 11 Firefox 41 desktop browsers results on html5test.com

Slide 10

Slide 10

Slide 11

Slide 11

?weird browsers? nlhtml5 — october 15th 2015

Slide 12

Slide 12

browsers and devices that do not adhere to current expectations

Slide 13

Slide 13

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

Slide 14

Slide 14

Slide 15

Slide 15

?weird browsers?

Slide 16

Slide 16

?weird browsers?

Slide 17

Slide 17

game consoles

Slide 18

Slide 18

portable game consoles

Slide 19

Slide 19

smart tvs

Slide 20

Slide 20

e-readers

Slide 21

Slide 21

smartwatches

Slide 22

Slide 22

photo cameras

Slide 23

Slide 23

Andre Jay Meissner cars

Slide 24

Slide 24

what do they have in common?

Slide 25

Slide 25

Slide 26

Slide 26

Slide 27

Slide 27

smart tvs, set-top boxes and consoles

Slide 28

Slide 28

“big screen browsers”

Slide 29

Slide 29

Slide 30

Slide 30

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

Slide 31

Slide 31

281 Google TV 418 LG WebOS 414 238 Panasonic Firefox OS LG Netcast 0 555 301 407 Panasonic Samsung Viera 2014 465 Samsung Tizen 449 Opera Devices smart tv results on html5test.com

Slide 32

Slide 32

53 309 Playstation 3 Playstation TV 98 328 Xbox 360 Playstation 4 286 Xbox One 0 555 66 311 Wii Wii U console results on html5test.com

Slide 33

Slide 33

Slide 34

Slide 34

1 control

Slide 35

Slide 35

the biggest challenge of of television browsers

Slide 36

Slide 36

navigation (without mouse or touchscreen)

Slide 37

Slide 37

d-pad

Slide 38

Slide 38

navigation with the d-pad

Slide 39

Slide 39

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

Slide 40

Slide 40

alternatives

Slide 41

Slide 41

analog controllers

Slide 42

Slide 42

remotes with trackpad

Slide 43

Slide 43

remotes with airmouse

Slide 44

Slide 44

second screen

Slide 45

Slide 45

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

Slide 46

Slide 46

Slide 47

Slide 47

Slide 48

Slide 48

Slide 49

Slide 49

text input (without keyboard)

Slide 50

Slide 50

d-pads

Slide 51

Slide 51

text input with the d-pad

Slide 52

Slide 52

alternatives

Slide 53

Slide 53

remotes with keyboards

Slide 54

Slide 54

wireless keyboards

Slide 55

Slide 55

and apps

Slide 56

Slide 56

Slide 57

Slide 57

Slide 58

Slide 58

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

Slide 59

Slide 59

navigation with gesture control

Slide 60

Slide 60

can we control these input methods directly from javascript?

Slide 61

Slide 61

the d-pad maybe

Slide 62

Slide 62

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

Slide 63

Slide 63

the gamepad maybe

Slide 64

Slide 64

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

Slide 65

Slide 65

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

Slide 66

Slide 66

the webcam no*

Slide 67

Slide 67

gestures no*

Slide 68

Slide 68

2 the difference between a television and a monitor

Slide 69

Slide 69

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

Slide 70

Slide 70

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

Slide 71

Slide 71

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

Slide 72

Slide 72

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

Slide 73

Slide 73

the image is then cropped to 1920 by 1080 pixels

Slide 74

Slide 74

the image is then cropped to 1920 by 1080 pixels

Slide 75

Slide 75

overscan causes blurry output +5%

Slide 76

Slide 76

solution 1 overscan correction

Slide 77

Slide 77

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

Slide 78

Slide 78

1920 pixels the television will enlarge the image by 5%

Slide 79

Slide 79

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

Slide 80

Slide 80

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

Slide 81

Slide 81

configure the correct overscan correction in the system preferences

Slide 82

Slide 82

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

Slide 83

Slide 83

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

Slide 84

Slide 84

solution 2 no overscan

Slide 85

Slide 85

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

Slide 86

Slide 86

the playstation 3 always shows the browser with overscan correction

Slide 87

Slide 87

the viewport (i really need some aspirin!)

Slide 88

Slide 88

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

Slide 89

Slide 89

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

Slide 90

Slide 90

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

Slide 91

Slide 91

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

Slide 92

Slide 92

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

Slide 93

Slide 93

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

Slide 94

Slide 94

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

Slide 95

Slide 95

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

<meta name=”viewport” content=“width=device-width”> <meta name=”viewport” content=”width=1024”>

Slide 96

Slide 96

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

Slide 97

Slide 97

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

Slide 98

Slide 98

800 pixels nintendo wii

Slide 99

Slide 99

980 pixels nintendo wii u

Slide 100

Slide 100

960 pixels lg webos

Slide 101

Slide 101

1024 pixels google tv

Slide 102

Slide 102

1041 of 1050 pixels microsoft xbox 360

Slide 103

Slide 103

1200 of 1236 pixels microsoft xbox one

Slide 104

Slide 104

1226 pixels lg netcast

Slide 105

Slide 105

1824 pixels sony playstation 3

Slide 106

Slide 106

1920 pixels sony playstation 4

Slide 107

Slide 107

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 108

Slide 108

device pixels != device pixels (of course not)

Slide 109

Slide 109

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 110

Slide 110

3 distance to the screen

Slide 111

Slide 111

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

Slide 112

fluid design++ the size of the contents is determined by the width of the viewport

Slide 113

Slide 113

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

Slide 114

Slide 114

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

Slide 115

Slide 115

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

Slide 116

Slide 116

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

Slide 117

Slide 117

youtube tv website

Slide 118

Slide 118

identifying smart tv’s (css for televisions)

Slide 119

Slide 119

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

Slide 120

Slide 120

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

Slide 121

Slide 121

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

Slide 122

Slide 122

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

Slide 123

Slide 123

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

Slide 124

Slide 124

3 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+

Slide 125

Slide 125

4 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

Slide 126

Slide 126

4 be careful with feature detection

Slide 127

Slide 127

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

Slide 128

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

Slide 129

Slide 129

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 130

Slide 130

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 131

Slide 131

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

Slide 132

Slide 132

Slide 133

Slide 133

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

Slide 134

Slide 134

android tv does not ship with a browser by default

Slide 135

Slide 135

Slide 136

Slide 136

e-readers

Slide 137

Slide 137

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

Slide 138

Slide 138

infrared touch screen

Slide 139

Slide 139

led’s sensors

Slide 140

Slide 140

mouse events down/up move amazon kindle touch yes pocketbook basic touch yes kobo glow yes yes sony reader yes yes touch events 1 finger

Slide 141

Slide 141

e-ink screens (slow, slower, slowest)

Slide 142

Slide 142

microscopic electrostatic charged balls

Slide 143

Slide 143

microscopic electrostatic charged balls + – – +

Slide 144

Slide 144

microscopic electrostatic charged balls + – – +

Slide 145

Slide 145

microscopic electrostatic charged balls

Slide 146

Slide 146

Slide 147

Slide 147

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

Slide 148

Slide 148

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

Slide 149

Slide 149

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

Slide 150

Slide 150

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

Slide 151

Slide 151

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

Slide 152

Slide 152

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

Slide 153

Slide 153

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

Slide 154

Slide 154

Slide 155

Slide 155

portable consoles

Slide 156

Slide 156

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

Slide 157

Slide 157

Slide 158

Slide 158

two screens (surprisingly normal)

Slide 159

Slide 159

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 160

Slide 160

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 161

Slide 161

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 162

Slide 162

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 163

Slide 163

Slide 164

Slide 164

Slide 165

Slide 165

?weird browsers!

Slide 166

Slide 166

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

Slide 167

Slide 167

but wait…

Slide 168

Slide 168

weird browsers!

Slide 169

Slide 169

weird browsers!

Slide 170

Slide 170

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

Slide 171

Slide 171

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

Slide 172

Slide 172

Slide 173

Slide 173

thank you niels leenheer @html5test