Slide 1
Slide 1 text
Responsive Web
Applications
with Container Queries
Slide 2
Slide 2 text
Michael Rog’s
Talk on Context-
aware CSS
#contextcss
Slide 3
Slide 3 text
No content
Slide 4
Slide 4 text
No content
Slide 5
Slide 5 text
Beautiful
Accounting
Software
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
Goal #1
Evolve the design
Slide 10
Slide 10 text
Goal #2
Support Multiple
Devices
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
No content
Slide 14
Slide 14 text
Goal #1
Evolve the design
Slide 15
Slide 15 text
Goal #2
Support Multiple
Devices
Slide 16
Slide 16 text
Responsive
Slide 17
Slide 17 text
Responsive
Slide 18
Slide 18 text
No content
Slide 19
Slide 19 text
No content
Slide 20
Slide 20 text
Device-specific
design and
development
Slide 21
Slide 21 text
A team of designers
and developers for
each platform
Slide 22
Slide 22 text
No content
Slide 23
Slide 23 text
Goal #1
Evolve the design
Slide 24
Slide 24 text
Goal #2
Support Multiple
Devices
Slide 25
Slide 25 text
No content
Slide 26
Slide 26 text
No content
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
Monolithic app with
accessible templates
Slide 29
Slide 29 text
Ignored Mobile Web
Slide 30
Slide 30 text
Limited Mobile App
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
No content
Slide 33
Slide 33 text
Each horizontal block
is considered in the
context of the viewport
Slide 34
Slide 34 text
No content
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
No content
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
No content
Slide 39
Slide 39 text
Each page can more
easily be art directed
Slide 40
Slide 40 text
No content
Slide 41
Slide 41 text
• No orders
• One order
• Less than one page of
orders
• Multiple pages of
orders
• Has Info Notifications
• Tab overflow
• Has Warning
Notifications
• Has limited access to
features
• Has different apps
installed
Slide 42
Slide 42 text
And now consider all of
those things for
multiple viewports
Slide 43
Slide 43 text
And now consider all of
those things for
multiple languages
Slide 44
Slide 44 text
A single page in a web
application can have
dozens of variations
Slide 45
Slide 45 text
A component-based
site has components
respondingly differently
to multiple contexts
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
With media queries,
you have to know the
interplay of all objects
in all scenarios
Slide 49
Slide 49 text
What if…
Slide 50
Slide 50 text
With container
queries, you only have
to know the interplay
within a single object
Slide 51
Slide 51 text
No spec for
container queries
Slide 52
Slide 52 text
No content
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
Declare in:
CSS,
HTML, or
JavaScript
Slide 55
Slide 55 text
https://github.com/ResponsiveImagesCG/cq-demos
.element:media( min-width:500px ) {}
https://github.com/tysonmatanich/elementQuery
.element[min-width~="500px"] {
background-color: #eee;
}
Slide 56
Slide 56 text
http://elementqueries.com/
@element ".element" and
(min-width: 500px) {
.element {
background: gold;
}
}
Slide 57
Slide 57 text
https://github.com/tysonmatanich/elementQuery
.element[min-width~="400px"] { }
Slide 58
Slide 58 text
To parse CSS, either
need to be on same
domain or set up CORS
Slide 59
Slide 59 text
https://github.com/Snugug/eq.js
data-eq-pts="small: 400, medium: 600,
large: 900"
Slide 60
Slide 60 text
At HTML level, requires
consistency of
implementation
across app
Slide 61
Slide 61 text
We chose JavaScript
and built our own
Slide 62
Slide 62 text
elements = [
{
"module": ".flex--2x1",
"className":"responsiveClass",
"minWidth": 768, "maxWidth": 1024
}
]
Slide 63
Slide 63 text
Going Responsive
meant a consistent
feature set across all
devices
Slide 64
Slide 64 text
New features
automatically have
cross-device support
Slide 65
Slide 65 text
No content
Slide 66
Slide 66 text
Went responsive in under a month†
• Design considerations done
in the months prior
• Went component by component
• Would continue to work in
non-responsive design
• Allowed us to just flip a switch
when we were ready
Slide 67
Slide 67 text
No content
Slide 68
Slide 68 text
No content
Slide 69
Slide 69 text
It’s not about the
properties, it’s about
the purpose.
Slide 70
Slide 70 text
No content
Slide 71
Slide 71 text
No content
Slide 72
Slide 72 text
No content
Slide 73
Slide 73 text
Tried to use grid
classes for
everything
Slide 74
Slide 74 text
.grid { }
.grid--inner { }
.grid--inner__first
.grid--inner__last
…
Slide 75
Slide 75 text
Had to write extra
classes just to define
responsive story
Slide 76
Slide 76 text
.grid { }
...
.grid--responsive--a
.grid--responsive--b
Slide 77
Slide 77 text
Single purpose
classes resulted in
less edge cases (and
less code!)
Slide 78
Slide 78 text
.layout-a { display: flex; }
.layout-b { display: flex; }
.grid { display: flex; }
Slide 79
Slide 79 text
Gzip minimizes
duplicate properties
really well
Slide 80
Slide 80 text
Tables are difficult
Slide 81
Slide 81 text
No content
Slide 82
Slide 82 text
No content
Slide 83
Slide 83 text
No content
Slide 84
Slide 84 text
No content
Slide 85
Slide 85 text
Avoid too much on
the horizontal axis
Slide 86
Slide 86 text
No content
Slide 87
Slide 87 text
No content
Slide 88
Slide 88 text
No content
Slide 89
Slide 89 text
No content
Slide 90
Slide 90 text
No content
Slide 91
Slide 91 text
Goal #1
Evolve the design
Slide 92
Slide 92 text
Goal #2
Support Multiple
Devices
Slide 93
Slide 93 text
Goal #1 reframed:
Allow anybody to make
product-wide design
changes quickly and easily
Slide 94
Slide 94 text
Problems:
• Different teams
• Different deliverables
• Different tech stacks
Slide 95
Slide 95 text
Solutions:
• Component-based approach
• Design systems team to establish patterns
• Design Systems team dedicated to
building and maintaining components
Slide 96
Slide 96 text
No content
Slide 97
Slide 97 text
Make the right
things easy and the
wrong things hard
Slide 98
Slide 98 text
No content
Slide 99
Slide 99 text
Yahoo! still does a
custom experience
per device
Slide 100
Slide 100 text
Shopify got rid of
Container Queries
Slide 101
Slide 101 text
No content
Slide 102
Slide 102 text
…
…
Slide 103
Slide 103 text
.two-columns {
display: flex;
flex-wrap: wrap;
}
.col1, .col2 { flex-grow: 1; }
.col1 {
flex-basis: 66%;
min-width: 360px;
}
.col2 {
flex-basis: 33%;
}
Slide 104
Slide 104 text
No content
Slide 105
Slide 105 text
No content
Slide 107
Slide 107 text
.media-body {
display: flex;
flex-wrap: wrap;
}
Slide 108
Slide 108 text
.media-content {
flex-grow: 1;
flex-basis: 400px;
margin-right: 20px;
}
Slide 109
Slide 109 text
.media-actions {
align-self: center;
margin: 20px 0;
}
Slide 110
Slide 110 text
No content
Slide 111
Slide 111 text
No content
Slide 112
Slide 112 text
...
Slide 113
Slide 113 text
.box {
display: flex;
flex-wrap: wrap;
}
Slide 114
Slide 114 text
.box-image {
flex-grow: 1;
flex-shrink: 0;
flex-basis: 150px;
}
.box-image > img {
width: 100%;
object-fit: cover;
}
Slide 115
Slide 115 text
.box-content {
margin: 10px;
flex-shrink: 1;
flex-grow: 1;
flex-basis: 60%;
}
Slide 116
Slide 116 text
…
…
…
Slide 117
Slide 117 text
.items {
display: grid;
grid-template-columns:
repeat(auto-fit, minmax(400px, 1fr));
}
Slide 118
Slide 118 text
No content
Slide 119
Slide 119 text
ResizeObserver
Slide 120
Slide 120 text
Houdini
Slide 121
Slide 121 text
What’s Houdini:
• Layout API
• Custom Paint API
• Parser API
• Properties and Values
• Animation Workout
• Typed OM
• Font Metrics API
Slide 122
Slide 122 text
No content
Slide 123
Slide 123 text
In Chrome:
• Layout API
• Custom Paint API
• Parser API
• Properties and Values
• Animation Workout
• Typed OM
• Font Metrics API
Slide 124
Slide 124 text
Layout API just gives
us layout
Slide 125
Slide 125 text
grid-template-columns:
200px 300px;
grid-template-columns:
200px 300px 600w,
200px 200px 1fr 900w;
Slide 126
Slide 126 text
Designers should
think Responsive
before they need to.
Slide 127
Slide 127 text
Container Queries
enable faster
development
Slide 128
Slide 128 text
Use techniques to
avoid media or
container queries
altogether
Slide 129
Slide 129 text
http://ricg.io
Slide 130
Slide 130 text
Thank you.
http:/
/snook.ca/
@snookca