On Wed, 22 Oct 2014 13:19:54 -0400
Alexandre <ac586133(a)hotmail.com> wrote:
Date: Tue, 21 Oct 2014 19:04:25 -0400
From: ejlddll(a)googlemail.com
To: trinity-devel(a)lists.pearsoncomputing.net
Subject: Re: [trinity-devel] TDE site glitch on iOS
On Tue, 21 Oct 2014 00:07:22 -0500
"Timothy Pearson" <kb9vqf(a)pearsoncomputing.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA224
>
> Hi E. Liddell,
>
> Not sure if there's anything you can do about this but I was
browsing
the
> TDE site on iOS and got the attached
glitch.
>
> Is there any way to force the horizontal scrollbar to show up in
this case
> instead of overlaying the left hand menu bar
on top of the text?
This is
> one of the very few cases where horizontal
scrolling is preferable
to what
> we have now.
There's no way I know of to get a scrollbar in, no, but it's possible
to
make
that page better-behaved at narrow widths with a
couple of tweaks.
Since
webdev has moved on from this version of the
site, I'll explain them
here.
First, add white-space:pre-line; to the style for the PRE element in
the
main stylesheet. This will allow the fixed-size
blocks of text in the
top-
posting example to word-wrap themselves if there
isn't enough space
for them. (This is one of the most obscure style attributes in CSS, I
suspect--it took me a while to find it.)
Secondly, liberally salt the displayed list email addresses
(optionally
also the archive URLs) with the <WBR> tag,
which will allow
line-breaks
to optionally take place at those locations.
trinity-devel-<WBR>unsubscribe(a)lists.<WBR>pearsoncomputing.net
can become
trinity-devel-
unsubscribe@lists.
pearsoncomputing.net
which takes up much less horizontal space than the entire thing
without
line-breaks. The catch is, I'm not sure
iOS's browser (Mobile Safari?)
understands this tag--Konqueror just ignores it. Still, it can't
hurt.
E. Liddell
Hi,
Just a word to say that it works as it should on Firefox for Android. No
Firefox on iOS?
No Firefox on iOS. Apple won't let them use any rendering engine other
than the one that came with the operating system, and the Mozilla
Foundation won't agree to do that. It was all over the tech news last
year.
The built-in rendering engine for iOS browsers is vanilla Webkit. I only
tested on Chrome's Webkit fork (where everything worked much the
same as it did in Firefox). It'll probably be all right, but without
checking
I'm not willing to guarantee that. (And I don't know the age/size of the
device or the version of iOS, either.)
E. Liddell