From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: html manual +css
Date: Thu, 26 Dec 2019 09:45:27 -0500 [thread overview]
Message-ID: <jwv36d788am.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <227383E4-BF11-4655-AFDD-CBE25D426A85@traduction-libre.org> (Jean-Christophe Helary's message of "Thu, 26 Dec 2019 23:09:14 +0900")
> 1) to have mobile browsers recognize media queries related to the display
> size it is necessary to add a <meta> tag to the <head> that contains
> a reference to the "viewport" of the display:
>
> https://www.reddit.com/r/css/comments/eft71n/iphone_safari_does_not_respond_to_maxwidth_media/
I wonder why the HTML needs this and what it really means.
[ E.g. the name "device-width" makes it sound like it intends to reflect
the physical size of the screen, whereas people watch their phone
screen from a much shorter distance than their desktop screen, so we
should pay attention to the "apparent size" rather than the physical
size. ]
> 3) then I put all that online and now the sample that I presented yesterday
> works perfectly well on a small mobile device, as you wanted.
Portrait mode now looks great, indeed, thanks.
In landscape mode, tho, the browser is wide enough that the top-header
fits on a single line and hence "sticks around" when you scroll, thus
eating up a lot of screen real estate (especially since phones nowadays
have an appalling aspect ratio, very far from the beloved 4:3).
Stefan
next prev parent reply other threads:[~2019-12-26 14:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 13:49 html manual +css Jean-Christophe Helary
2017-06-02 14:28 ` Paul Eggert
2017-06-02 14:45 ` Jean-Christophe Helary
2017-06-02 14:56 ` Jean-Christophe Helary
2017-06-02 15:14 ` Yuri Khan
2017-06-02 15:22 ` Eli Zaretskii
2017-06-02 15:29 ` Jean-Christophe Helary
2017-06-05 14:44 ` Jean-Christophe Helary
2017-06-06 22:41 ` Richard Stallman
2017-06-06 23:47 ` Jean-Christophe Helary
2017-06-07 14:27 ` Jean-Christophe Helary
2019-12-23 16:54 ` Jean-Christophe Helary
[not found] ` <jwvr20v6jug.fsf-monnier+emacs@gnu.org>
2019-12-24 9:06 ` Jean-Christophe Helary
2019-12-24 14:37 ` Jean-Christophe Helary
2019-12-24 14:43 ` Jean-Christophe Helary
2019-12-25 22:03 ` Stefan Monnier
2019-12-26 0:08 ` Jean-Christophe Helary
2019-12-26 14:09 ` Jean-Christophe Helary
2019-12-26 14:45 ` Stefan Monnier [this message]
2019-12-26 15:08 ` Jean-Christophe Helary
2019-12-26 15:22 ` Jean-Christophe Helary
2019-12-26 15:50 ` Stefan Monnier
2019-12-26 16:27 ` Yuri Khan
2019-12-26 18:17 ` Stefan Monnier
2019-12-26 16:53 ` Jean-Christophe Helary
2019-12-30 11:53 ` Jean-Christophe Helary
2020-01-15 11:20 ` Gavin Smith
2020-01-15 12:12 ` Jean-Christophe Helary
2020-01-15 13:43 ` Patrice Dumas
2020-01-15 13:52 ` Jean-Christophe Helary
2020-01-15 14:18 ` Patrice Dumas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv36d788am.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).