duplicate line in IE7

Spelling errors are not it. I have simply dumped in the content from a
document and have not gotten around to spell checking or editing, and
many other things for that matter.

Now that is surely the wrong way to go about developing a page/site.
What's to say that when you do get around to using "real" text, you
don't introduce more/other errors?

What do you mean by this? I like to have at least some dummy text of
some sort as a place holder to give me an idea of what it's going to
look like. When I know the content is not going to change(something
that has happened here), then I'll run it through a spell checker,
then it will be the "real" content. How will that introduce new
errors? And your method would be...?

On 26 Sep, 23:26, alice <al... (AT) fearofdolls (DOT) com> wrote:

Can anyone tell me how to fix this-
On this page -http://s195679515.onlinehome.us/emorys/dinner.php

Write better code. What you have isn't "wrong" that we can point a
finger at, but it's low-grade coding style that relies of freaky
behaviours to look right on one browser at a time. When you combine
freaky and IE, you can no longer predict what might happen.

<h2>MENUS</h2>
<p>
<a href="menu.php">A</a>
<a href="dinner.php">B</a>
<a href="catering.php">C</a>
</p>

<a> is an inline element and doesn't cause linebreaks. As you want
each one on a separate line, you've done something freaky in the CSS
to make it look like you want, for one browser, one time. Whatever
this was, obviously didn't travel well to IE.

The fix is to fix your HTML markup. It's a list of block things, so
mark it up as a list of things instead. Just like you'd already done
on the other menus:

<ul>
<li><a href="index.php">Home</a></li>
<li><a href="menu.php">Menus</a></li>
<li><a href="banquets.php">Banquets</a></li>
</ul>


Once you've made the HTML reflect the reality of your content, then
worry about adjusting the CSS to get your look right. If you rely on
freaky CSS, IE will keep biting you whenever it can.

Also ditch the XHTML in favour of HTML 4.01 Strict. Much less to go
wrong.

alice wrote:

Thanks. I'll try that. But what is the lesson here, that in IE you
can't have things float left without extra characters appearing? I
mean, how can this specifically be avoided.

Ask Mr. Bill, it's MS that does not want to play nice with standards.

In all seriousness, MSIE has and *still* has issues with floats. You
want a fun one? Float a block next to some test that as some inline
element within styled italic and poof! Watch as everything that follows
on the page disappears! It's great for those reports there you have to
explain to the higher-ups that the project is in the tank. Just float a
little image of a graph or something an make sure the critical comments
*follow* a bit of text emphasized <em>...</em>!!!

Now to your page. avoid XHTML unless your *really* need it, which do
don't. Use HTML 4.01 *strict*. Avoid using 'px' in your style except for
elements dimensioned with pixels, i.e., images. Use % and em's for
the rest. Start minimally and only add want you need to get the effect
you want, prevents DIViditus and CLASSitus. Be flexible, don't try to
make a page pixel-perfect and exact for everybody...it won't happen,
example is pages with forms. The controls look different on different
desktops...Win2K > WinXP, Win > Mac > Linux, Gnome > KDE!

Well that should be a good start.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Sep 27, 12:53 pm, "Jonathan N. Little" <lws4... (AT) centralva (DOT) net>
wrote:

alice wrote:
Thanks. I'll try that. But what is the lesson here, that in IE you
can't have things float left without extra characters appearing? I
mean, how can this specifically be avoided.

Ask Mr. Bill, it's MS that does not want to play nice with standards.

In all seriousness, MSIE has and *still* has issues with floats. You
want a fun one? Float a block next to some test that as some inline
element within styled italic and poof! Watch as everything that follows
on the page disappears! It's great for those reports there you have to
explain to the higher-ups that the project is in the tank. Just float a
little image of a graph or something an make sure the critical comments
*follow* a bit of text emphasized <em>...</em>!!!

Now to your page. avoid XHTML unless your *really* need it, which do
don't. Use HTML 4.01 *strict*. Avoid using 'px' in your style except for
elements dimensioned with pixels, i.e., images. Use % and em's for
the rest. Start minimally and only add want you need to get the effect
you want, prevents DIViditus and CLASSitus. Be flexible, don't try to
make a page pixel-perfect and exact for everybody...it won't happen,
example is pages with forms. The controls look different on different
desktops...Win2K > WinXP, Win > Mac > Linux, Gnome > KDE!

Well that should be a good start.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIOhttp://www.LittleWorksStudio.com

Thanks. And thanks for actually making sense. I've read books that
imply I should start using xhtml, but I guess that's not so accurate
after all. It's hard to tell who the 'experts' are.

alice wrote:

Thanks. And thanks for actually making sense. I've read books that
imply I should start using xhtml, but I guess that's not so accurate
after all. It's hard to tell who the 'experts' are.

Agreed. For most applications XHTML offers no real advantage and if
applied strictly breaks MSIE. So one can correctly conclude that if you
don't need the added features, don't us it. It will just needlessly
complicate your project.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Spelling errors are not it. I have simply dumped in the content from a
document and have not gotten around to spell checking or editing, and
many other things for that matter.

Now that is surely the wrong way to go about developing a page/site.
What's to say that when you do get around to using "real" text, you
don't introduce more/other errors?


I'm still curious about what you mean by this? Do you care to explain?

What should I have done instead?