| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
This reverts commit 3b4701b240f55b4e97edee7fdc13fec35a76fc5a.
|
|
The FAQ page already unabbreviates the FAQ abbreviation. This aids
screen readers to pronounce the abbreviation correctly to increase
comprehension and adds semantics.
Acked-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Sync with Pomf 2.0.x maint branch.
- pages: Add a non-breaking space before "MiB"
Corrects a typo and adds the missing space character to index.
|
|
Fixes a typo where the unit symbol was missing a space character before
it.
To avoid automatic line breaks in text "128 MiB", a non-breaking space
character is used instead of a regular space character. If the text
doesn't fit at the end of a line it is moved in its entirety to the next
line.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
I have a belief that Swig banners are a Grunt only thing, and they don't
really integrate very well into Swig anyway. It's kind of a hack, and a
bad one because we don't need it anymore.
By deprecating Swig banners, we should have easier time replacing
Grunt/npm with Make in a future release.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
The <header> element represents a group of introductory or navigational
aids. It is semantically incorrect to use it with only one element
inside.
The <header> element was introduced in commit 87014fa08f. That commit
describes the correct usage of <header> element with multiple elements
inside <header>.
This bug was introduced in commit fd566d3d7f.
|
|
|
|
|
|
Silly ewhal@, that's not how you indent pages.
Fixes a code style violation introduced in commit 87014fa08f.
|
|
|
|
|
|
W3C's HTML5 specification instructs a standard way to create
subheadings in "4.12.1 Subheadings, subtitles, alternative titles and
taglines". [1]
A `<h2>` element is not appropriate here as a subheading, because the
subheading "Roppa interior~" is not part of the document outline but a
Catalonian translation of the `<h1>` heading.
Adding a `lang="ca"` attribute to the Catalonian subheading increases
screenreader compatibility and semantics even further. Screenreaders
will then use Catalonian pronounction instead of English if supported.
[1]: http://www.w3.org/html/wg/drafts/html/CR/common-idioms.html#sub-head
|
|
|
|
|
|
|
|
|
