Repository navigation
Commit 0748e48
# [web] Report `env(safe-area-inset-*)` as `FlutterView.viewPadding`
## The problem
`SafeArea` does nothing on the web. On an iPhone running the app as a
standalone PWA, content sits under the notch, the Dynamic Island and the
home
indicator, and `MediaQuery.paddingOf(context)` is `EdgeInsets.zero` on
every
browser. The issue has been open since 2021, and the workaround that
everybody
in the thread reaches for — adding `<meta name="viewport" content="...,
viewport-fit=cover">` to `index.html` — has no effect.
Issue: flutter#84833
## Root cause
There are two independent causes, and fixing either one alone leaves the
bug in
place.
**1. The engine deletes the app's opt-in.**
`FullPageEmbeddingStrategy._applyViewportMeta()`
(`engine/src/flutter/lib/web_ui/lib/src/engine/view_embedder/embedding_strategy/full_page_embedding_strategy.dart:70`)
runs `querySelectorAll('meta[name="viewport"]')`, calls `remove()` on
every
match (line 86), and appends its own tag with a hard-coded
`content = 'width=device-width, initial-scale=1.0, maximum-scale=5.0'`
(line 96). There is no `viewport-fit` in it. So an app that wrote
`viewport-fit=cover` in its `index.html` has that descriptor deleted
during
bootstrap, WebKit reverts to keeping the viewport inside the safe area,
and
`env(safe-area-inset-*)` correctly reports that there is nothing to
inset. This
is why every workaround in the thread fails.
**2. Nothing ever reads `env(safe-area-inset-*)`.**
Grepping `safe-area|safeAreaInset|viewport-fit|viewportFit` across
`engine/src/flutter/lib/web_ui/lib/` returns no matches before this
change.
`EngineFlutterView.viewPadding` (`window.dart:264`) and
`EngineFlutterView.padding` (`window.dart:270`) both read a
`final ViewConfiguration _viewConfiguration = const
ViewConfiguration();`
(`window.dart:97`) that is never reassigned, so they are permanently
`ui.ViewPadding.zero`. Only `viewInsets` works, because it is backed by
a
mutable field that `_computeOnScreenKeyboardInsets` (`window.dart:363`)
updates
through `DimensionsProvider.computeKeyboardInsets`.
## Reproduction
Measured on an iPhone simulator, `devicePixelRatio` 3, UA
`Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X)
AppleWebKit/605.1.15
(KHTML, like Gecko) Version/26.1 Mobile/15E148 Safari/604.1`. Two pages
were
served side by side from the same origin: a plain HTML control that
declares
`viewport-fit=cover` and reads `env(safe-area-inset-*)` out of
`getComputedStyle`, and a Flutter app whose `index.html` declares the
same tag
and which additionally reports `MediaQuery.viewPaddingOf` / `paddingOf`.
Both
declare `apple-mobile-web-app-status-bar-style=black-translucent`. Each
was read
in a Safari tab and as a standalone add-to-home-screen PWA, in both
orientations. 11 configurations were recorded in all, from 997 samples;
the four
below are the ones the argument rests on.
**The Flutter app was built with Flutter 3.44.6 stable**, not with this
branch,
so the engine tag quoted in row 3 is the one that release writes.
Current `main`
writes `maximum-scale=5.0` and no `user-scalable` descriptor. The
difference is
immaterial here: what matters is that neither carries a `viewport-fit`,
and both
remove the tag the app authored.
| page | mode | orientation | `innerWidth` | viewport meta actually in
the DOM | browser `env()` T/R/B/L | `MediaQuery.viewPaddingOf` |
|---|---|---|---|---|---|---|
| control | tab | landscape | 874 | `…, viewport-fit=cover` *(author's)*
| `0 / 62 / 20 / 62` | n/a |
| control | PWA | portrait | 402 | `…, viewport-fit=cover` *(author's)*
| `0 / 0 / 34 / 0` | n/a |
| Flutter | tab | landscape | 750 | `width=device-width,
initial-scale=1.0, maximum-scale=1.0, user-scalable=no`
*(`flt-viewport`)* | `0 / 0 / 20 / 0` | `zero` |
| Flutter | PWA | portrait | 402 | *(`flt-viewport`, no `viewport-fit`)*
| `0 / 0 / 0 / 0` | `zero` |
Two things to read off this:
* The `viewport-fit=cover` the app wrote is **not in the DOM** on the
Flutter
page. The tag that is there is the engine's, and it has no
`viewport-fit`.
That is cause 1, observed directly.
* The viewport is correspondingly narrower — 750 against the control's
874 in
the same orientation on the same device. The difference, 124, is exactly
`62 + 62`, the left and right insets the control reports. The app is
being
laid out inside the safe area.
`MediaQuery.viewPaddingOf` was `EdgeInsets.zero` in **all 997 readings
taken
from the Flutter page**, including the runs where the viewport meta tag
was
restored by hand so that the page *did* go full-bleed and `env()` *did*
report
`0 / 62 / 20 / 62`. That isolates cause 2: even with the browser
reporting a
safe area correctly, nothing in the engine reads it.
**What has not been measured on device.** The numbers above are all
pre-patch.
The patched engine has unit coverage (below) but has not been run on a
device or
simulator, so this PR claims no measured post-patch
`MediaQuery.padding`.
`env(safe-area-inset-top)` was **zero in all 11 configurations**,
including the
two standalone-PWA ones, where there is no Safari chrome to explain it
away. I
don't have an account of why, so I'm not offering one: the top axis is
simply
uncovered on device and rests on unit tests. If a reviewer knows the
configuration that produces a non-zero top inset in mobile WebKit, I'd
like to
measure it. An end-to-end confirmation that a `SafeArea` child moves is
also
still owed. Both are repeated under "Not covered".
The same run also shows why the `env()` values cannot be passed through
verbatim: with **no** `viewport-fit` anywhere, iOS Safari still reports
`env(safe-area-inset-bottom) = 20px` (row 3 above). See "Backwards
compatibility" below.
## What the fix does
**Layer 1 — preserve the app's `viewport-fit`.**
`_applyViewportMeta()` now reads the `viewport-fit` descriptor off the
viewport
meta tags it is about to remove and copies it into the tag it writes.
Parsing
lives in one new file, `view_embedder/viewport_fit.dart`, so that the
side that
reads a descriptor and the side that writes it can never drift apart.
The
resolution matches the browser's:
* the **last** viewport meta tag of the page wins outright, including
when it
declares no `viewport-fit` (WebKit builds a fresh set of viewport
arguments
per tag, so descriptors that the last tag omits revert to their
defaults);
* `,`, `;` and whitespace are all accepted as descriptor separators,
because
browsers accept all three — `content="width=400;initial-scale=1"` is
honoured
by both Blink and WebKit;
* the descriptor and its value are matched case-insensitively;
* only `auto`, `contain` and `cover` are copied over, so nothing unknown
can
reach the tag the engine writes.
Because the tag the engine writes carries the descriptor, the value also
survives hot restart: the tag read at the start of
`_applyViewportMeta()` on the
next run is the `flt-viewport` tag left behind by the previous one.
The "this tag will be replaced" warning now fires only when the engine's
tag
really does say less than the app's — it lists the descriptors being
dropped —
so following the template's own advice below no longer provokes a
warning on
every debug run.
**Layer 2 — feed `env(safe-area-inset-*)` into the framework.**
`DimensionsProvider` gains `computeSafeAreaInsets()`.
`FullPageDimensionsProvider` implements it with a `display: none` probe
element
whose four paddings are `env(safe-area-inset-*, 0px)`; the browser
substitutes
`env()` at computed-value time, so `getComputedStyle` returns absolute
lengths
without the element ever being laid out or painted. Every declaration on
the
probe is written with `important` priority, so an ordinary
`* { padding: 0 !important }` reset in the host page cannot silently
zero the
measurement. The probe is created up front, in the constructor, so
reading the
safe area is a pure measurement and never a DOM mutation in the middle
of a
frame; it is re-attached if the host page ever empties `<body>`, and
removed in
`close()`.
**The insets are gated on the app's own opt-in.**
`computeSafeAreaInsets()`
returns `ViewPadding.zero` unless the viewport meta tag the engine wrote
carries
`viewport-fit=cover`, i.e. unless the app declared it in its
`index.html`. The
gate reads that tag back with `readViewportFit`, the same function that
wrote
it, so the two halves are not coupled through an exact spelling:
changing how
`_applyViewportMeta` joins its descriptors cannot silently switch the
feature
off.
`EngineFlutterView.viewPadding` is now backed by those insets, computed
lazily
and recomputed by `_handleBrowserResize` on the same events that
recompute the
physical size. `padding` is `viewPadding` minus `viewInsets`, clamped at
zero
(`ViewPadding.minus`), which is the relationship the other platforms
use: when
the on-screen keyboard covers the bottom safe area, the bottom padding
goes to
zero. No framework-side change is needed — `MediaQuery.fromView` already
reads
`view.padding` and `view.viewPadding`.
`systemGestureInsets` is deliberately left at zero. `env()` describes
the parts
of the viewport that the device obstructs, not the parts the system
reserves for
its own gestures, and browsers do not expose the latter.
**Tooling.** `packages/flutter_tools/templates/app/web/index.html.tmpl`
gains
the tag, commented out, with an explanation, next to the guidance it
already
carries for `<base href>`. New projects are not opted in by default; the
comment
tells developers how to opt in.
**Cleanup.** `ViewConfiguration.viewInsets`, `.viewPadding` and
`.padding`
(`platform_dispatcher.dart`) are removed. `viewInsets` was already dead,
and the
other two become dead with this change; `ViewConfiguration` is only ever
instantiated as `const ViewConfiguration()`.
## Backwards compatibility
The gate is what keeps this from being a breaking change, and it is
there
because the naive version is one.
* **Apps that never declared `viewport-fit`** — including everything
`flutter create` produces, since the web template ships no active
viewport meta tag —
are unchanged. The engine writes a byte-identical viewport meta tag, and
`viewPadding`, `padding` and `MediaQuery.paddingOf` stay `zero`.
This is not automatic. iOS Safari reports `env(safe-area-inset-bottom) =
20px`
in landscape *with no `viewport-fit` at all*, so an implementation that
simply
forwarded `env()` would have given every existing Flutter web app on iOS
an
uninvited `bottom: 20` logical pixels, shrinking the child of every
`SafeArea`
in an app that asked for nothing. The `20px` is a measured reading (row
3 of
the table above); the resulting layout shift is the arithmetic
consequence,
not a second measurement.
`FullPageDimensionsProvider.computeSafeAreaInsets()` therefore returns
zero
unless the page opted in, and the doc comment on
`DimensionsProvider.computeSafeAreaInsets` says so explicitly.
* **Apps that declared `viewport-fit=cover` in their `index.html` do
change**,
and this is the fix working rather than a side effect. Today the engine
deletes the descriptor, so those apps are laid out inside the safe area;
after
this change they are laid out full-bleed. On the device above, that is
the
difference between the Flutter page's 750 logical pixels and the
control's
874 in the same orientation, and content that is *not*
wrapped in a `SafeArea` moves under the cutout and the rounded corners.
This population matters: `viewport-fit=cover` in `index.html` is the
most
repeated workaround in issue flutter#84833 itself and in five years of blog
posts
about it. Many authors added the tag, saw nothing happen, and never
wrapped
anything in `SafeArea`. For them this is a visible layout change. It is
the
behaviour the tag has always requested, and the tag is the app's own
explicit
opt-in, but it should be called out in the release notes and it is the
reason
the PR does not carry `Fixes flutter#84833` on its own.
* **Embedded (`hostElement`) and multi-view apps** are untouched.
`_applyViewportMeta` only exists in `FullPageEmbeddingStrategy`, and
`CustomElementDimensionsProvider.computeSafeAreaInsets()` returns zero,
so
`padding == zero.minus(viewInsets) == zero` exactly as before.
* **Browsers without `env()` support** degrade to zero rather than to
`NaN`: an
unsupported `env()` leaves the padding at its initial value, which reads
back
as `0px`.
If the team would rather not move the `viewport-fit=cover` population in
a
single release, the cover pass-through in `_applyViewportMeta` is the
one place
to put a `FlutterConfiguration` flag; the rest of the change is inert
without
it.
## Tests
42 new unit tests, run with `felt test --browser chrome --compiler
dart2js` over
the whole `test/engine` directory. The engine suite goes from 1190 to
1232
passing, 14 skipped, no failures and no regressions.
A new `viewport_fit_test.dart` covers the parser directly: every
specification
value, unknown values, a descriptor that merely *ends* in
`viewport-fit`, `,`
`;` and whitespace separators, `=` spacing, case-insensitivity,
last-declaration-wins, and a round trip between what `ViewportFit`
writes and
what `readViewportFit` reads. `parseViewportContent` is held to the same
tolerance, so the two functions cannot disagree about what a `content`
attribute
says. The rest extend the four existing suites: the
descriptor surviving `_applyViewportMeta` in each of those spellings;
the gate
staying shut for `auto` and `contain`, which the engine preserves but
which must
not unlock the insets; the probe's structure, its `important` priority
beating a
`* { padding: 5px !important }` rule in the host page, its re-attachment
and its
removal on `close()`; `viewPadding` refreshed by a real `resize` event
rather
than only by `debugForceResize`, so `_handleBrowserResize` is covered;
zero for
an embedded view; and `ViewPadding.minus` at no, partial and full
clamping.
Two of them run a real `FullPageEmbeddingStrategy` over a page declaring
`viewport-fit=cover`, hand the page it leaves behind to a real
`FullPageDimensionsProvider`, and assert a non-zero result (and a zero
one for
the negative twin). That seam between the two halves of the fix is where
a
hand-written `content` string would have hidden a break.
Two mutations were run to check the tests bite. Making the gate accept
any
`viewport-fit` rather than only `cover` fails the `auto`/`contain` test.
Changing
how `_applyViewportMeta` joins its descriptors from `', '` to `';'`
leaves the
provider suite green — which is the point of sharing the parser, and
would not
have been true of an earlier revision of this patch that matched the
joined
string exactly.
## Not covered, left for follow-up
* **Embedded and multi-view apps still get zero.** The engine could
derive their
insets from the intersection of the host element's bounding rect with
the
page's `env()` values; there is a `TODO` on
`CustomElementDimensionsProvider.computeSafeAreaInsets` for it. Issue
flutter#84833
should stay open until that lands, which is why this PR references the
issue
rather than closing it.
* **Safe-area changes that do not resize the viewport are not
observed.**
`_viewPadding` is refreshed only from `_handleBrowserResize`. On iOS the
status bar grows during a call, screen recording or personal hotspot
without
changing the viewport size, so `env(safe-area-inset-top)` changes with
no
`resize` event. A `ResizeObserver` on a probe whose
`top`/`left`/`width`/
`height` are the `env()` values would close this; the limitation is
documented
on both `DimensionsProvider.computeSafeAreaInsets` and
`EngineFlutterView._viewPadding`.
* **`viewport-fit` injected from JavaScript after bootstrap** is not
re-read.
`_applyViewportMeta` runs once, in the strategy's constructor.
* **`systemGestureInsets`** stays zero; browsers do not expose the
information.
* **`env(safe-area-inset-top)` has unit coverage but no on-device
coverage.**
It was zero in all 11 measured configurations, standalone PWAs included,
and I
have no explanation for that. It should be measured on a configuration
that
does report a non-zero top inset before this ships.
* **Docs.** A companion flutter/website change should document the
`viewport-fit=cover` opt-in on the web display-modes/initialization page
and
add a web caveat to the `SafeArea` API docs.
## Pre-launch Checklist
- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [AI contribution guidelines] and understand my
responsibilities, or I am not using AI tools.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [x] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.
Notes on the checklist:
* On the breaking change policy: the change is gated so that no app that
did not
declare `viewport-fit=cover` sees any difference in
`MediaQuery.padding`,
`MediaQuery.viewPadding` or its viewport meta tag. Apps that did declare
it
move from a safe-area-contained layout to a full-bleed one, with the
measured
numbers above. `customer_testing` / flutter/tests should be run against
this
branch before landing, and if anything moves, a migration guide from the
flutter/website template should land with it.
* No Data Driven Fixes apply: there is no API rename or removal on the
framework
side.
<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[AI contribution guidelines]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
---------
Co-authored-by: Mouad Debbar <[email protected]>
1 parent 974341b commit 0748e48
15 files changed
Lines changed: 947 additions & 34 deletions
File tree
- engine/src/flutter/lib/web_ui
- lib/src
- engine
- view_embedder
- dimensions_provider
- embedding_strategy
- test/engine
- view_embedder
- dimensions_provider
- embedding_strategy
- packages/flutter_tools/templates/app/web
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
174 | 174 | | |
175 | 175 | | |
176 | 176 | | |
| 177 | + | |
177 | 178 | | |
178 | 179 | | |
179 | 180 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
831 | 831 | | |
832 | 832 | | |
833 | 833 | | |
| 834 | + | |
| 835 | + | |
834 | 836 | | |
835 | 837 | | |
836 | 838 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1882 | 1882 | | |
1883 | 1883 | | |
1884 | 1884 | | |
1885 | | - | |
1886 | | - | |
1887 | 1885 | | |
1888 | | - | |
1889 | 1886 | | |
1890 | 1887 | | |
1891 | 1888 | | |
| |||
1895 | 1892 | | |
1896 | 1893 | | |
1897 | 1894 | | |
1898 | | - | |
1899 | | - | |
1900 | 1895 | | |
1901 | | - | |
1902 | 1896 | | |
1903 | 1897 | | |
1904 | 1898 | | |
| |||
1907 | 1901 | | |
1908 | 1902 | | |
1909 | 1903 | | |
1910 | | - | |
1911 | | - | |
1912 | 1904 | | |
1913 | | - | |
1914 | 1905 | | |
1915 | 1906 | | |
1916 | 1907 | | |
| |||
1920 | 1911 | | |
1921 | 1912 | | |
1922 | 1913 | | |
1923 | | - | |
1924 | | - | |
1925 | 1914 | | |
1926 | | - | |
1927 | 1915 | | |
1928 | 1916 | | |
1929 | 1917 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
99 | 99 | | |
100 | 100 | | |
101 | 101 | | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
102 | 117 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
50 | 50 | | |
51 | 51 | | |
52 | 52 | | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
53 | 80 | | |
54 | 81 | | |
55 | 82 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| 7 | + | |
7 | 8 | | |
8 | 9 | | |
| 10 | + | |
9 | 11 | | |
10 | 12 | | |
11 | 13 | | |
12 | 14 | | |
| 15 | + | |
13 | 16 | | |
14 | 17 | | |
15 | 18 | | |
| |||
34 | 37 | | |
35 | 38 | | |
36 | 39 | | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
37 | 46 | | |
38 | 47 | | |
39 | 48 | | |
| |||
51 | 60 | | |
52 | 61 | | |
53 | 62 | | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
54 | 70 | | |
55 | 71 | | |
56 | 72 | | |
57 | 73 | | |
58 | 74 | | |
| 75 | + | |
59 | 76 | | |
60 | 77 | | |
61 | 78 | | |
| |||
112 | 129 | | |
113 | 130 | | |
114 | 131 | | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
| 187 | + | |
| 188 | + | |
| 189 | + | |
| 190 | + | |
| 191 | + | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
115 | 208 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| 10 | + | |
10 | 11 | | |
11 | 12 | | |
12 | 13 | | |
| |||
68 | 69 | | |
69 | 70 | | |
70 | 71 | | |
71 | | - | |
72 | | - | |
73 | | - | |
74 | | - | |
75 | | - | |
76 | | - | |
77 | | - | |
78 | | - | |
79 | | - | |
80 | | - | |
81 | | - | |
82 | | - | |
83 | | - | |
84 | | - | |
85 | | - | |
86 | | - | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
87 | 98 | | |
88 | 99 | | |
89 | | - | |
90 | | - | |
91 | 100 | | |
92 | 101 | | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
93 | 118 | | |
94 | 119 | | |
95 | 120 | | |
96 | | - | |
| 121 | + | |
97 | 122 | | |
98 | 123 | | |
99 | 124 | | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
100 | 129 | | |
101 | 130 | | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
102 | 166 | | |
0 commit comments