Weird Browsers

A presentation at GrunnJS in September 2015 in Groningen, Netherlands by Niels Leenheer

Slide 1

Slide 1

?weird browsers? grunnjs — september 9th 2015

Slide 2

Slide 2

402 Edge 396 521 Safari 8 Chrome 45 0 555 336 467 Internet Explorer 11 Firefox 40 desktop browsers results on html5test.com

Slide 3

Slide 3

402 Edge 396 521 Safari 8 Chrome 45 0 555 336 467 Internet Explorer 11 Firefox 40 desktop browsers results on html5test.com

Slide 4

Slide 4

402 Edge 396 521 Safari 8 Chrome 45 0 555 16 336 467 Internet Explorer 6 Internet Explorer 11 Firefox 40 desktop browsers results on html5test.com

Slide 5

Slide 5

?weird browsers?

Slide 6

Slide 6

browsers and devices that do not adhere to current expectations

Slide 7

Slide 7

?weird browsers?

Slide 8

Slide 8

?weird browsers?

Slide 9

Slide 9

game consoles

Slide 10

Slide 10

portable game consoles

Slide 11

Slide 11

smart tvs

Slide 12

Slide 12

e-readers

Slide 13

Slide 13

smartwatches

Slide 14

Slide 14

photo cameras

Slide 15

Slide 15

Andre Jay Meissner cars

Slide 16

Slide 16

comparable with mobile before the iphone and android everybody is trying to figure it out

Slide 17

Slide 17

Slide 18

Slide 18

Slide 19

Slide 19

smart tvs, set-top boxes and consoles

Slide 20

Slide 20

“big screen browsers”

Slide 21

Slide 21

Slide 22

Slide 22

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

Slide 23

Slide 23

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 24

Slide 24

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 25

Slide 25

Slide 26

Slide 26

1 control

Slide 27

Slide 27

the biggest challenge of of television browsers

Slide 28

Slide 28

navigation (without mouse or touchscreen)

Slide 29

Slide 29

d-pad

Slide 30

Slide 30

navigation with the d-pad

Slide 31

Slide 31

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

Slide 32

Slide 32

alternatives

Slide 33

Slide 33

analog controllers

Slide 34

Slide 34

remotes with trackpad

Slide 35

Slide 35

remotes with airmouse

Slide 36

Slide 36

second screen

Slide 37

Slide 37

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

Slide 38

Slide 38

Slide 39

Slide 39

Slide 40

Slide 40

Slide 41

Slide 41

text input (without keyboard)

Slide 42

Slide 42

d-pads

Slide 43

Slide 43

text input with the d-pad

Slide 44

Slide 44

alternatives

Slide 45

Slide 45

remotes with keyboards

Slide 46

Slide 46

wireless keyboards

Slide 47

Slide 47

and apps

Slide 48

Slide 48

Slide 49

Slide 49

Slide 50

Slide 50

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

Slide 51

Slide 51

navigation with gesture control

Slide 52

Slide 52

can we control these input methods directly from javascript?

Slide 53

Slide 53

the d-pad maybe

Slide 54

Slide 54

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

Slide 55

Slide 55

the gamepad maybe

Slide 56

Slide 56

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

Slide 57

Slide 57

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

Slide 58

Slide 58

the webcam no*

Slide 59

Slide 59

gestures no*

Slide 60

Slide 60

2 the difference between a television and a monitor

Slide 61

Slide 61

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

Slide 62

Slide 62

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

Slide 63

Slide 63

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

Slide 64

Slide 64

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

Slide 65

Slide 65

the image is then cropped to 1920 by 1080 pixels

Slide 66

Slide 66

the image is then cropped to 1920 by 1080 pixels

Slide 67

Slide 67

overscan causes blurry output +5%

Slide 68

Slide 68

solution 1 overscan correction

Slide 69

Slide 69

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

Slide 70

Slide 70

1920 pixels the television will enlarge the image by 5%

Slide 71

Slide 71

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

Slide 72

Slide 72

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

Slide 73

Slide 73

configure the correct overscan correction in the system preferences

Slide 74

Slide 74

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

Slide 75

Slide 75

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

Slide 76

Slide 76

solution 2 no overscan

Slide 77

Slide 77

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

Slide 78

Slide 78

the playstation 3 always shows the browser with overscan correction

Slide 79

Slide 79

the viewport (i really need some aspirine!)

Slide 80

Slide 80

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

Slide 81

Slide 81

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

Slide 82

Slide 82

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

Slide 83

Slide 83

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

Slide 84

Slide 84

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

Slide 85

Slide 85

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

Slide 86

Slide 86

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

Slide 87

Slide 87

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 88

Slide 88

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

Slide 89

Slide 89

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

Slide 90

Slide 90

800 pixels nintendo wii

Slide 91

Slide 91

980 pixels nintendo wii u

Slide 92

Slide 92

960 pixels lg webos

Slide 93

Slide 93

1024 pixels google tv

Slide 94

Slide 94

1041 of 1050 pixels microsoft xbox 360

Slide 95

Slide 95

1200 of 1236 pixels microsoft xbox one

Slide 96

Slide 96

1226 pixels lg netcast

Slide 97

Slide 97

1824 pixels sony playstation 3

Slide 98

Slide 98

1920 pixels sony playstation 4

Slide 99

Slide 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

Slide 100

Slide 100

device pixels != device pixels (of course not)

Slide 101

Slide 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

Slide 102

Slide 102

3 distance to the screen

Slide 103

Slide 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

Slide 104

Slide 104

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

Slide 105

Slide 105

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

Slide 106

Slide 106

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

Slide 107

Slide 107

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

Slide 108

Slide 108

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

Slide 109

Slide 109

youtube tv website

Slide 110

Slide 110

identifying smart tv’s (css for televisions)

Slide 111

Slide 111

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

Slide 112

Slide 112

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

Slide 113

Slide 113

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

Slide 114

Slide 114

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

Slide 115

Slide 115

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

Slide 116

Slide 116

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 117

Slide 117

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 118

Slide 118

4 be careful with feature detection

Slide 119

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

Slide 120

Slide 120

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

Slide 121

Slide 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

Slide 122

Slide 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

Slide 123

Slide 123

Slide 124

Slide 124

e-readers

Slide 125

Slide 125

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

Slide 126

Slide 126

infrared touch screen

Slide 127

Slide 127

led’s sensors

Slide 128

Slide 128

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 129

Slide 129

e-ink screens (slow, slower, slowest)

Slide 130

Slide 130

microscopic electrostatic charged balls

Slide 131

Slide 131

microscopic electrostatic charged balls + – – +

Slide 132

Slide 132

microscopic electrostatic charged balls + – – +

Slide 133

Slide 133

microscopic electrostatic charged balls

Slide 134

Slide 134

Slide 135

Slide 135

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

Slide 136

Slide 136

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

Slide 137

Slide 137

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

Slide 138

Slide 138

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

Slide 139

Slide 139

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

Slide 140

Slide 140

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

Slide 141

Slide 141

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

Slide 142

Slide 142

Slide 143

Slide 143

portable consoles

Slide 144

Slide 144

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

Slide 145

Slide 145

Slide 146

Slide 146

two screens (surprisingly normal)

Slide 147

Slide 147

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 148

Slide 148

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 149

Slide 149

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 150

Slide 150

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 151

Slide 151

Slide 152

Slide 152

?weird browsers!

Slide 153

Slide 153

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

Slide 154

Slide 154

thank you niels leenheer @html5test