[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: js-info disabling sidebar for narrow windows (experimental)
|
From: |
Raymond Toy |
|
Subject: |
Re: js-info disabling sidebar for narrow windows (experimental) |
|
Date: |
Thu, 18 Feb 2021 14:02:00 -0800 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1.90 (gnu/linux) |
>>>>> "Gavin" == Gavin Smith <gavinsmith0123@gmail.com> writes:
Gavin> On Thu, Feb 18, 2021 at 08:05:42AM -0800, Raymond Toy wrote:
>> >>>>> "Per" == Per Bothner <per@bothner.com> writes:
>>
Per> A goal was to automatically switch to "narrow" mode on
Per> smartphones, that isn't working yet. (Smartphone browsers tend
Per> to do magic things with "viewport" and zooming, and dealing
Per> with that needs some more research and experimentation.)
>>
>> Yeah, that would be awesome. When I view the html version of
>> some texinfo docs, the display is rather messed up with tiny
>> fonts in some cases. For example,
>> https://cmucl.org/docs/cmu-user/html/index.html looks great on
>> desktop, but the stuff at the very bottom renders in super tiny
>> fonts on my phone.
Gavin> This the font "boosting" issue.
Gavin> This issue should have been dealt with in two ways. First,
Gavin> in the current development version, a <table> element is not
Gavin> used to lay out a menu by default (set with the FORMAT_MENU
Gavin> option).
Gavin> I had also thought it had been fixed after this discussion.
Gavin> https://lists.gnu.org/archive/html/bug-texinfo/2020-03/msg00007.html
I'm pretty sure that page was generated using texinfo 3.7.
>> I suggest adding <meta name="viewport"
>> content="width=device-width,initial-scale=1"> to the standard
>> HTML <head>...</head> block. This will make the result noticeably
>> better on mobile/pads and is, so far as I have seen, harmless on
>> larger screens.
Gavin> It would be worth checking that both of these changes have
Gavin> happened properly.
Yes, the viewport ought to be set.
Still, while I'm dreaming, texinfo could do these for me since it's
generating the html files. Ideally, texinfo would produce ok results
by default, and let the author fine tune things as needed.
But since I'm not actually contributing to fixing these issues, feel
free to ignore me. :-)
--
Ray