From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.emacs.devel Subject: Re: html manual +css Date: Fri, 27 Dec 2019 01:53:42 +0900 Message-ID: <6D83441F-B5E3-4513-B008-87AAC0DF151F@traduction-libre.org> References: <05A866DB-4211-476E-9107-14E5F9BE9232@gmail.com> <53DA475D-B063-470A-BB87-D3FFC9A7CF79@gmail.com> <834lvyct3t.fsf@gnu.org> <01B655FC-51F0-4A33-ADBF-3E1268E9E0EA@gmail.com> <3D282E00-27F3-451A-9895-5BCEEE0B7FA8@gmail.com> <227383E4-BF11-4655-AFDD-CBE25D426A85@traduction-libre.org> <29E540AC-0DE4-40A5-AAD6-58FE0178B830@traduction-libre.org> <77EFA561-E2F9-4BFB-831F-F83B6F05964E@traduction-libre.org> Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="253008"; mail-complaints-to="usenet@blaine.gmane.org" To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 26 17:54:04 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ikWOi-0013iW-1W for ged-emacs-devel@m.gmane.org; Thu, 26 Dec 2019 17:54:04 +0100 Original-Received: from localhost ([::1]:55004 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ikWOg-0003m1-Tg for ged-emacs-devel@m.gmane.org; Thu, 26 Dec 2019 11:54:02 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43791) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ikWOa-0003lu-Ml for emacs-devel@gnu.org; Thu, 26 Dec 2019 11:53:57 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ikWOY-0001Lr-PS for emacs-devel@gnu.org; Thu, 26 Dec 2019 11:53:56 -0500 Original-Received: from relay4-d.mail.gandi.net ([217.70.183.196]:48423) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ikWOY-0001LI-G6 for emacs-devel@gnu.org; Thu, 26 Dec 2019 11:53:54 -0500 X-Originating-IP: 182.251.133.105 Original-Received: from [172.20.10.3] (KD182251133105.au-net.ne.jp [182.251.133.105]) (Authenticated sender: jean.christophe.helary@traduction-libre.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 8EDF3E0002 for ; Thu, 26 Dec 2019 16:53:51 +0000 (UTC) In-Reply-To: X-Mailer: Apple Mail (2.3608.40.2.2.4) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 217.70.183.196 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243655 Archived-At: > On Dec 27, 2019, at 0:50, Stefan Monnier = wrote: >=20 >>> The MDN doc on viewport is here: >>> = https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag >>>=20 >>> The W3C is trying to port that directly to CSS but the spec is only = a draft: >>> https://drafts.csswg.org/css-device-adapt/#the-viewport >=20 > So, IIUC in the long run we don't need to change the HTML because this > `meta` element is only a hack added by Safari and the corresponding > standard feature is not yet standardized but will likely put the > corresponding info in the CSS. Not really. The feature was added by Apple/mobile Safari because it was = the first to provide a full-browser application on a small screen but = other vendors are now using the feature and as the MDN site says: > A typical mobile-optimized site contains something like the following: >=20 > So it's not targeting mobile Safari anymore but any standard browser on = the existing mobile platforms. i.e., you'd see the same with Chrome on Android as you'd see on = Safari/iOS. For ex. this site gives screen sizes for all sorts of devices: https://mediag.com/blog/popular-screen-resolutions-designing-for-all/ Regarding the "long run" remark, the CSS property has been proposed in = 2011 and the document is still a working draft with Firefox and Safari = not supporting the features (Chrome/Edge/Internet Explorer do). Also, = the implementation seems to try to copy Apple's original proposal... = Politics !!! So it looks like we're in for some time. Although I just asked extra = info on reddit regarding the state of the spec. >>> = https://medium.com/@elad/understanding-the-difference-between-css-resoluti= on-and-device-resolution-28acae23da0b >=20 > This page is pretty poor, not explaining what the "CSS pixel" is > supposed to represent; taking "browser provided data" as gospel ;-) :) >> Ok, it should work now, with the extra bonus that if your desktop = browser >> window is not high enough, the behavior will be the same as landscape >> mobile: the menu will stay at the top of the page in "summarized" = mode. >>=20 >> @media (max-width: 40em), (max-height: 40em) and = (orientation:landscape) { >=20 > It's indeed better but with one regression: now in landscape on my > phone, the top-line is spread as a "vertical menu" whereas it used to > fit on a single line. You're right. I split the query in two: @media (max-height: 40em) and (orientation:landscape) { div.header { position: static; border-color: brown; width: fit-content; } =20 } @media (max-width: 40em) { div.header { position: static; border-color: brown; width: fit-content; } and if the landscape mode has enough width then it won't get the extra = menu modifications that are set by max-width. Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune