Chromium already supports dynamic edge-to-edge viewports. This change
opts-in by default, making the gesture navigation bar (chin) invisible
without needing scroll interaction.
No other changes were necessary, as no content relied on specific
viewport insets.
Command used:
```
sed -i 's/<meta name="viewport" content="width=device-width, initial-scale=1"\/>/<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover"\/>/g' **/*.html
```
We moved from signify to OpenSSH on 2024-02-14. These instructions were
useful but are consistently causing confusion for people who are missing
that this is an optional step for people who had the signify public key
saved from previous usage. We provide multiple ways to get the current
public key and don't really need this.
Our optimized factory images currently don't mark this script as
executable because there's no API for it in the zip library used by
fastboot. For now, just run it directly with the shell.
After installation, the user may want to dive into more information
about the new system they got (=> "Further information"). This should
have a higher priority than the section "Replacing GrapheneOS with the
stock OS."
Debian 10 no longer receives official security support and has an
OpenSSH version predating file signing support. We plan to move away
from signify to OpenSSH for more portability so this has to go.
The changes summarized:
* Use angle brackets (`>`) instead of arrow symbols (`➔`).
* Put a non-breaking space (` `) before each angle bracket.
* Wrap sequences and elements in bold element (`<b>`).
* Accessibility: Wrap angle bracket in a span tag with an aria-label.
References:
* https://developers.google.com/style/procedures#multi-action-procedures
* https://developers.google.com/style/ui-elements#angle-brackets
I use the entity number ` ` for the non-breaking space instead of
the named character entity ` ` because `xmllint` produces a linting
error (which is to be expected).
```
parser error : Entity 'nbsp' not defined
```
Ideally we want to use the named character entity (` `), but I
couldn't find a reasonable solution. In order not to block this change,
I've opted for the entity number (` `). If a reasonable solution is
found, the entity number can be easily replaced by the named character
entity.
The changes require more than just replacing the currently used arrow.
The surrounding context should be checked to determine whether a change
is appropriate at this point and whether it requires further changes in
the context itself.
The paragraphs are wrapped with the currently used 98 characters. If
using vim:
```
:set tw=98
```
Vim's wrapping is weird when applied several times. To work around this,
we can unwrap the paragraph first. To select a paragraph, unwrap and
rewrap: Point to the line of the paragraph, and type `vipJgqq` in normal
mode.
