On 08/18/2014 10:55 AM, Ed Mullen wrote:
Patrick Turner pounded out :
I did post recently about how to set text size in SM so other
browsers like Chrome "got it right". By trial and error I managed to
fiddle with sizes so this occurs. Thanks to those who commented, and
suggested I used other WYSIWYG composer programs. None worked
properly, and had bigger bothers than SM. Thanks anyway.Even Front
Page is more awkward to use than SM. AL I WANT IS SIMPLE PLEASE.
Sea Monkey always inserts images where I want them but it always
enlarges them and no amount of trying to control image size by
zooming out in "compose page" or "browse page" makes any difference.
In Firefox, images appear the same, too big. But in Chrome, images
are exactly as I meant them to be, same as I made the images when I
saved them from an image program. The relative text size is also
correct.
Composer inserts an image at its original size. To do anything else
would be bad practice. And you really shouldn't "resize" an image using
HTML.
So it seems like SM and derivative stuff from Mozilla don't have
enough settable settings which are then recognized by SM and
derivatives. In other words, SM is like a man whose "left hand
doesn't know what the right hand does does"
What settings specifically are you talking about?
Also, SM or FireFox does not display text colors or background
colors.
Of course they do. Post a URL of a page exhibiting what you're describing.
The other trouble is with line wrapping while typing text to describe
my images at my pages. I have to do it manually after going over
text. I don't want to do that, and I don't wan the text to extend
right across wide screen before it line wraps, its a 41.5cm wide
screen x 25.5cm high.
You have no idea what screen size the visitors to your site will have.
Stop designing to your screen size.
As for wrapping, HTML text will, if necessary, use the entire width of a
user's viewport before wrapping. Unless you tell is to do something
else as in:
<div style="margin-left: 20%; margin-right: 20%;">
<p>Put a whole bunch of text here ...</p>
...
</div>
Example pages of my site are at http://www.turneraudio.com.au
I tried to see if there were major differences in html source which
instructed different browsers in different ways. But it seemed to me
the "view source" gave me what looked like enormously complex html
and I didn't know what to add or subtract to make it work AS I DAMN
WELL WANT IT TO and not to some vague recipe thought up by some dopey
nerd@somewhere.
Well, if you'd adequately describe exactly /what/ your problem is AND
post a URL we could look at it and help.
Additionally, as I mentioned up-thread, from a peek at your source code
it appears that you used Microsoft Word to edit that URL above. You
didn't mention that. Also, I see:
<meta name="GENERATOR" content="http://www.fg-a.com";>
which is indicative of heaven knows what since the reference is to a
free image site.
Looking at the source code of that site and some pages makes me want to
play with redoing it in HTML5 and CSS, but all those <big></big>(s) give
me a headache.
Site and pages look good to me in both Firefox 31.0 and SeaMonkey
2.26.1. Very easy to read, even at a 67% zoom setting.
--
P&G Gymnastics Championships
August 21-24, 2014
<http://pgchamps.com/>
GO Bucs! GO Steelers!
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
