Slide 1

Slide 1 text

Standardizing : What the future holds for HTML Controls

Slide 2

Slide 2 text

Hi! I’m Stephanie. Program Manager for Microsoft Edge Developer Experiences @seaotta

Slide 3

Slide 3 text

Hi! I’m Stephanie. Designer Front-end developer Dev and Designer Advocate @seaotta

Slide 4

Slide 4 text

Designer Developer

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

Mock up Code

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

HTML Controls

Slide 13

Slide 13 text

Standardizing The Past: why HTML Controls are the way they are The Present: where we’re at now The Future: what’s to come with HTML Controls (select!)

Slide 14

Slide 14 text

Some History HTML Form Controls

Slide 15

Slide 15 text

1995

Slide 16

Slide 16 text

1995

Slide 17

Slide 17 text

1995

Slide 18

Slide 18 text

1995

Slide 19

Slide 19 text

Pre- 1995 1.0

Slide 20

Slide 20 text

Pre- 1995 1.0

Slide 21

Slide 21 text

The primary focus of the specification draft was to capture common HTML practice in web browsers as of June 1994. http://www.blooberry.com/indexdot/history/html20.html

Slide 22

Slide 22 text

WorldWideWeb (Nexus) ViolaWWW Erwise MidasWWW MacWWW Mosaic Cello Lynx 2.0 Arena AMosaic 1.0 IBM WebExplorer Netscape Navigator SlipKnot 1.0 MacWeb Ibrowse Agora (Argo) Minuet Web Browsers 1991-1994 Wikipedia

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

1995

Slide 26

Slide 26 text

1995

Slide 27

Slide 27 text

1995

Slide 28

Slide 28 text

CSS IS AWESOME

Slide 29

Slide 29 text

CSS IS AWESOME 1997

Slide 30

Slide 30 text

1999 4.01 CSS IS AWESOME ❤

Slide 31

Slide 31 text

1995

Slide 32

Slide 32 text

https://www.456bereastreet.com/archive/200409/styling_form_controls/

Slide 33

Slide 33 text

.form { -webkit-appearance: value; -moz-appearance: value; appearance: value; }

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

Recap Pre-1995: Lots of browsers pop up 1994: HTML 1.0 draft expires 1995: HTML 2.0 becomes standardized spec Basic HTML form controls standardized No standard for styling Operating system dependency 1997: CSS Supported by HTML 3.20 not fully embraced by browsers 1999: CSS Supported by HTML 4.01 embraced by more browsers

Slide 36

Slide 36 text

1999 – present

Slide 37

Slide 37 text

The Current State of Styling Native Controls

Slide 38

Slide 38 text

It’s not bad…

Slide 39

Slide 39 text

But it’s not great either.

Slide 40

Slide 40 text

Feasibility of Styling Form Controls with CSS

Slide 41

Slide 41 text

Text-field () Buttons Feasibility of Styling Form Controls with CSS Can be styled with few problems

Slide 42

Slide 42 text

Text-field () Buttons Checkboxes Radios Feasibility of Styling Form Controls with CSS Can be styled with few problems Can be styled with complex CSS and hacks

Slide 43

Slide 43 text

Text-field () Buttons Checkboxes Radios Color picker Date controls Dropdown widgets Range File picker Feasibility of Styling Form Controls with CSS Can be styled with few problems Can be styled with complex CSS and hacks Good night and good luck.

Slide 44

Slide 44 text

Text-field () Buttons Checkboxes Radios Color picker Date controls Dropdown widgets Range File picker Feasibility of Styling Form Controls with CSS Can be styled with few problems Can be styled with complex CSS and hacks Good night and good luck.

Slide 45

Slide 45 text

Text-field () Buttons Checkboxes Radios Color picker Date controls Dropdown widgets Range File picker Feasibility of Styling Form Controls with CSS Can be styled with few problems Can be styled with complex CSS and hacks Good night and good luck.

Slide 46

Slide 46 text

Browser Inconsistencies

Slide 47

Slide 47 text

Browser Inconsistencies Chrome EdgeHTML Firefox Safari

Slide 48

Slide 48 text

No extensibility

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

Slide 51

Slide 51 text

Slide 52

Slide 52 text

Slide 53

Slide 53 text

Dribbble: Jordan Ranson

Slide 54

Slide 54 text

Dribbble: Mark Hendriks Dribbble: Seb kay

Slide 55

Slide 55 text

What do developers really want?

Slide 56

Slide 56 text

Do they really want better form controls?

Slide 57

Slide 57 text

No content

Slide 58

Slide 58 text

Initial Research 1400 respondents

Slide 59

Slide 59 text

Initial Research: Demographics Full results: https://aka.ms/controls-survey

Slide 60

Slide 60 text

Initial Research: Demographics Full results: https://aka.ms/controls-survey

Slide 61

Slide 61 text

Top 10 Re-created Form Controls Full results: https://aka.ms/controls-survey

Slide 62

Slide 62 text

Reasons Controls Are Created Full results: https://aka.ms/controls-survey

Slide 63

Slide 63 text

JSConfEU Survey Which form control gives you the most frustration? Why?

Slide 64

Slide 64 text

JSConfEU Survey Which form control gives you the most frustration?

Slide 65

Slide 65 text

JSConfEU Survey Why?

Slide 66

Slide 66 text

“ Requires hacky tricks

Slide 67

Slide 67 text

“ Can’t style elements at all to the extent we need to

Slide 68

Slide 68 text

Too little control over styling across popular browsers “

Slide 69

Slide 69 text

…but the amount of work it takes to implement an accessible alternative with complete feature parity is massive. “

Slide 70

Slide 70 text

How painful is it?

Slide 71

Slide 71 text

ImportantTM Research

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

No content

Slide 74

Slide 74 text

No content

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

No content

Slide 77

Slide 77 text

No content

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

No content

Slide 80

Slide 80 text

No content

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

No content

Slide 83

Slide 83 text

Clearly, there is an issue

Slide 84

Slide 84 text

The Future

Slide 85

Slide 85 text

Slide 86

Slide 86 text

HTML isn’t done

Slide 87

Slide 87 text

+

Slide 88

Slide 88 text

New Styles & Accessibility Improvements

Slide 89

Slide 89 text

Chromium Controls Visual Refresh

Slide 90

Slide 90 text

New Native Components

Slide 91

Slide 91 text

New native components

Slide 92

Slide 92 text

New native components https://aka.ms/virtual-scroller https://aka.ms/toggle-switch

Slide 93

Slide 93 text

From proposal to standard 1. Proposal incubates in the WICG 2. After incubation, multi-implementer interest is required before graduating to an HTML standard

Slide 94

Slide 94 text

Tell other implementers what you want! 1. @mozhacks on Twitter 2. Mozilla Firefox Platform Status: https://github.com/ mozilla/platform-status 3. @webkit on Twitter 4. WebKit Platform Status: https://webkit.org/status/

Slide 95

Slide 95 text

Fixing the current problems with controls

Slide 96

Slide 96 text

Form controls and their parts aren’t standardized

Slide 97

Slide 97 text

How do you standardize a control?

Slide 98

Slide 98 text

Open UI https://open-ui.org/

Slide 99

Slide 99 text

Open UI’s Mission Maintain an open standard for UI and promote its adherence and adoption.

Slide 100

Slide 100 text

Goals of Open UI • Document component names as they exist today • Define a common language for describing UIs and design systems • Eventual browser standards for web app components • Converging designer processes and developer workflows

Slide 101

Slide 101 text

Standardizing controls and components is hard…

Slide 102

Slide 102 text

No content

Slide 103

Slide 103 text

Open UI People who work on design systems Web platform engineers +

Slide 104

Slide 104 text

Investigations: Peeling open

Slide 105

Slide 105 text

No content

Slide 106

Slide 106 text

No content

Slide 107

Slide 107 text

aka.ms/select-ou Select Working Draft

Slide 108

Slide 108 text

aka.ms/open-ui Open UI Website

Slide 109

Slide 109 text

aka.ms/open-ui Add a design system Open UI Website

Slide 110

Slide 110 text

aka.ms/open-ui Add a design system Provide feedback

Slide 111

Slide 111 text

We need you!

Slide 112

Slide 112 text

We need you! • Provide feedback on the current HTML Control prototypes that Chrome has • Contribute to the form control investigations on Open UI • Tell browser vendors what you need from your form controls

Slide 113

Slide 113 text

Follow these folks • @stubbornella – Google Chrome PM • @gregwhitworth – Microsoft Edge PM • @seaotta – Microsoft Edge PM

Slide 114

Slide 114 text

We’re here to listen…

Slide 115

Slide 115 text

…because these improvements are for you.

Slide 116

Slide 116 text

Thank you! https://noti.st/seaotta @seaotta ststimac@microsoft.com