problem with code

thedarkman · Sep 13, 2010

No jokes please; on this page

http://www.infotextmanuscripts.org/limericks.html

the titles are in red all the way down but suddenly at Mork The
Pollack they've gone to black. I can't for the life of me see what
I've done wrong. Can someone enlighten me?

Thanks

rf · Sep 13, 2010

thedarkman said:
No jokes please; on this page

http://www.infotextmanuscripts.org/limericks.html

the titles are in red all the way down but suddenly at Mork The
Pollack they've gone to black. I can't for the life of me see what
I've done wrong. Can someone enlighten me?

You have one thousand three hundred and sixty three HTML errors, and 5
warnings. Not bad for a page that is 3500 lines long. That's an error to
line ration of 39%

The most notable one (and the one probably causing your problem) is that
font, apart from being deprecated, is an inline element and cannot contain
block elements. h1 and p are block elements. It's only by the grace of the
browsers error correction that you are getting any colour at all.

I suspect the browser has simply given up on its error correction. (Doesn't
happen with IE8 BTW).

BTW if you were to use CSS then you could eliminate all of those font
elements and be able to specify your colours in exactly one place.

h1 {color: red; background-color: white;}
p {color: black; background-color: white;}

dorayme · Sep 13, 2010

<[email protected]
m>,

thedarkman said:
No jokes please; on this page

http://www.infotextmanuscripts.org/limericks.html

the titles are in red all the way down but suddenly at Mork The
Pollack they've gone to black. I can't for the life of me see what
I've done wrong. Can someone enlighten me?

Yes, I would not dream of joking about this page, one of the best
pieces of markup I have seen in a long time. I am glad you asked
this instructive question thedarkman, the answer is to notice
that with Godiva, you have:

<h1><a name="davidfrost"></a><a
name="giraffe"></a><a name="hubble"></a><a name="judge_m"></a><a
name="lord_arse">Miss
Godiva</a></st
rong></fon

t> said:
</f

ont>
</stro
ng></s
trong>
</fo
nt></fon
t></h1>

whereas with Mork, you have:

<h1><a name="davidfrost"></a><a
name="giraffe"></a><a name="hubble"></a><a name="judge_m"></a><a
name="lord_arse">Mork The
Polack

</str

ong> said:
</f

ont>
</fo
nt></stron
g></st
rong></fon
t></h1>

Now to fix *just this business of Mork going black* substitute
for Mork:

<h1><a name="davidfrost"></a><a
name="giraffe"></a><a name="hubble"></a><a name="judge_m"></a><a
name="lord_arse">Mork The
Polack

</str

ong> said:
</f

ont>
</fo
nt></stron
g></st
rong></fon
t></h1>

and do similar for the rest below Mork.

dorayme · Sep 13, 2010

Ed Mullen said:
OMG. I got a huge headache just reading that, dorayme! Geez!

You tried to read it? Not even I did! But if this OP cum
prankster cum troll did what I suggested, his Mork would go red.
Trust me, Ed. <g>

Neredbojias · Sep 13, 2010

No jokes please; on this page

http://www.infotextmanuscripts.org/limericks.html

the titles are in red all the way down but suddenly at Mork The
Pollack they've gone to black. I can't for the life of me see what
I've done wrong. Can someone enlighten me?

Thanks

I think the problem is that you didn't concentrate sufficiently during
the 5 minutes you spent learning html. Congratulations, though; that
is the worst page I've seen this year (2010). Actually, I mis-speak to
some extent because the default background of my browser is black and
so is most of your text.

123Jim · Sep 13, 2010

thedarkman said:
No jokes please; on this page

http://www.infotextmanuscripts.org/limericks.html

the titles are in red all the way down but suddenly at Mork The
Pollack they've gone to black. I can't for the life of me see what
I've done wrong. Can someone enlighten me?

Thanks

There once was a guy called thedarkman
He did something bad with the web man
Oh Dog won't you save us from reading his markup
and tell him he needs to give up man.

I can't figure out how you created such a monstrous abortion of a page.
start again?

which editor are you using?

123Jim · Sep 13, 2010

dorayme said:
<[email protected]
m>,

Yes, I would not dream of joking about this page, one of the best
pieces of markup I have seen in a long time. I am glad you asked
this instructive question thedarkman, the answer is to notice
that with Godiva, you have:

<h1><a name="davidfrost"></a><a
name="giraffe"></a><a name="hubble"></a><a name="judge_m"></a><a
name="lord_arse">Miss
Godiva</a></st
rong></fon

ont>
</stro
ng></s
trong>
</fo
nt></fon
t></h1>

whereas with Mork, you have:

<h1><a name="davidfrost"></a><a
name="giraffe"></a><a name="hubble"></a><a name="judge_m"></a><a
name="lord_arse">Mork The
Polack

ont>
</fo
nt></stron
g></st
rong></fon
t></h1>

Now to fix *just this business of Mork going black* substitute
for Mork:

<h1><a name="davidfrost"></a><a
name="giraffe"></a><a name="hubble"></a><a name="judge_m"></a><a
name="lord_arse">Mork The
Polack

ont>
</fo
nt></stron
g></st
rong></fon
t></h1>

and do similar for the rest below Mork.

--

I'm a bit confused with this page .. when I check the markup using Firebug
... I find the markup you post above, but when I check the markup by.. right
click > view page source .. the markup is not at all monstrous .. it's
perfectly basic ..
what gives?

Beauregard T. Shagnasty · Sep 13, 2010

thedarkman said:
No jokes please;

That's gonna be tough...

on this page
http://www.infotextmanuscripts.org/limericks.html

Aside: limericks should not be aligned as "centered" .. the normal
display of the limerick poem is to be "text-align: left" with the third
and fourth lines indented about three spaces or so.

Do you know who G. Legman is?

(Most text should not be "centered.")

rf · Sep 13, 2010

123Jim said:
news:[email protected]...

I'm a bit confused with this page .. when I check the markup using Firebug
.. I find the markup you post above, but when I check the markup by..
right click > view page source .. the markup is not at all monstrous ..
it's perfectly basic ..
what gives?

View source is, well, er, what the server spat out to the browser.

The markup viewed with firebug is from the DOM, after the browsers error
correction has been applied. It's the browsers "view" of what the page looks
like.

This may differ from what the authors view of what the page looks like.

Jukka K. Korpela · Sep 13, 2010

123Jim wrote:

[ fullquote, a usual sign of cluelessness, though perhaps intentionally so,
given the nature of the thread ]

I'm a bit confused with this page ..

(Hint: " .." is a fairly strong cluelessness signal, too.)

You apparently mean the page
http://www.infotextmanuscripts.org/limericks.html
(Due to fullquoting, a reader has to scroll up a lot to guess what you are
referring to.)

when I check the markup using
Firebug .. I find the markup you post above,

Ditto when using Firefox Web Developer Extension.

but when I check the
markup by.. right click > view page source .. the markup is not at
all monstrous .. it's perfectly basic ..
what gives?

It's interesting indeed. Maybe we all should learn to do a simple View
Source every now and then.

The page contains no client side scripting, so what's the difference being
original source and "generated source". Well, Firefox, apparently. The
"generated source" contains the markup as modified by Firefox. You can see
that Firefox plays an interesting game here, if you just test with a
document containing

<h1>Hello world</h1>

in its body. Firefox turns it to

<h1>Hello world</h1>

And you may guess what happens if a page contains lots of tags and
relatives, without any closing tags for them.

If you look at the page on IE (don't you ever do that, guys?). Mork The
Pollack is red.

Apparently the Firefox rendering problem is caused by its second-guessing of
what the markup is supposed to be, generating bulky stuff that apparently
runs over some intrinsic limit.

The page markup is bad, but it really didn't reserve this. The problem
probably vanishes in a puff of logic if the author does this:
1) remove all FONT markup (a simple global replace would do this, as the
page seems to contain just fairly simple FONT tags)
2) add a stylesheet rule to make headings read if you really want that (you
have been implicitly warned), e.g. putting the following right before the
end tag </HEAD>:

<style type="text/css">
h1 { color: red; background: white; }
</style>

(Of course, I would never use h1 markup for something that is definitely
_second_ level headings, but that's just me and every sensible web author,
and beside the point.)

Raymond Schmit · Sep 13, 2010

View source is, well, er, what the server spat out to the browser.

The markup viewed with firebug is from the DOM, after the browsers error
correction has been applied. It's the browsers "view" of what the page looks
like.

This may differ from what the authors view of what the page looks like.

That's correct ...
That's a part of the source:

<h1>A Limerick For Everybody's Favourite Double Child
Killer</h1>


There once was a nonce name of <a href="marshall-images.html">Hunt-

 Ley</a> who said "I'm sure that knife is blunt",
 But alas, it was not,
 Now a scarred face he's got
 In Frankland gaol, the murdering ****.

 



<h1>A Nice Pair</h1>


There was once a young lady named Sam
 Who said: Brainless you may think I am,
 Just because I undress
 For the popular press,
 But I'm making a mint,
 (Not bad for a dumb bint),
 So I really could not give a damn.


 

You should notice that a lot of tags are not closed ....
Close it first

Doug Miller · Sep 15, 2010

"rf" said:
You have one thousand three hundred and sixty three HTML errors, and 5
warnings. Not bad for a page that is 3500 lines long. That's an error to
line ration of 39%

He's up to 1467 errors now... :-(

rf · Sep 15, 2010

Doug Miller said:
He's up to 1467 errors now... :-(

I get 1474, and he has fewer lines. The ratio is climbing: 45.3% now.

But I notice that absolutely none of the many solutions presented over the
several thread this google grouper started have been implemented. His page
is still broken. Oh, well, who bloody cares anymore

Phillip Jones · Sep 15, 2010

Doug said:
He's up to 1467 errors now... :-(

I downloaded the page and opened it with DreamWeaver. This is first time
I've ever received this warning when I ran the command fix html (errors).

"The document is nested so deeply, DreamWeaver has had to give up."

Jonathan N. Little · Sep 15, 2010

thedarkman said:
No jokes please; on this page

http://www.infotextmanuscripts.org/limericks.html

the titles are in red all the way down but suddenly at Mork The
Pollack they've gone to black. I can't for the life of me see what
I've done wrong. Can someone enlighten me?

I will try, but it is pretty clear that you are adamant in refusing to
be enlighten.

1) As you have already be told the reason the page breaks is that you
have made numerous errors in your markup. Browsers try to "fix" or
"error correct" these errors, but if you throw enough crap at them they
well eventually give up. IE is better at parsing crap. Other browsers
expect that the authors know at least something about HTML and give up
sooner.

2) You are not closing elements that *require* closing. If you don't
know what that means then you need to learn a little bit about web
authoring.

3) If you do not want to learn, your posts and your page does seem to
indicate such:

"If you are NOT viewing this page with Internet Explorer, you may see
....
This is because I am primarily a researcher and author, not a code warrior!"

Then I suggest you hire someone else to do it for you...

4) Contrary to what I perceive your impression of HTML and CSS to be
with a *simple* page as yours is it is not too difficult to implement.

5) A small possible template illustrates how very simple a working
solution could be:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>

<title>Fix it</title>

<style type="text/css">
h1, h2, p { text-align: center; }
h1 { color: red; }
h2 { color: red; font-style: italic; }
p.note { color: red; }
</style>
</head>
<body>

<h1>
LIMERICKS 
BY ALEXANDER BARON
</h1>


[This collection includes non-standard limericks: extended limericks and
limerick poems, etc].



Unlike the original website this page doesn't require the use of a
broken browser to view it


<h2>
A Limerick For Everybody's Favourite Double Child Killer
</h2>


There once was a nonce name of Hunt- 
Ley who said "I'm sure that knife is blunt", 
But alas, it was not, 
Now a scarred face he's got 
In Frankland gaol, the murdering ****.


<h2>
A Nice Pair
</h2>

There was once a young lady named Sam 
Who said: Brainless you may think I am, 
Just because I undress 
For the popular press, 
But I'm making a mint, 
(Not bad for a dumb bint), 
So I really could not give a damn. 



Now continue with the same pattern...if it is not too difficult for you.


</body>
</html>

Beauregard T. Shagnasty · Sep 15, 2010

Jonathan said:

There once was a nonce name of Hunt- 
Ley who said "I'm sure that knife is blunt", 
But alas, it was not, 
Now a scarred face he's got 
In Frankland gaol, the murdering ****.

I style limericks thusly, because I am a firm believer the 3rd and 4th
lines should be indented:

..limerick {
font-family: Georgia, serif; /* <- your font choice here */
}

<pre class='limerick'>
There once was a nonce name of Hunt-
Ley who said "I'm sure that knife is blunt",
But alas, it was not,
Now a scarred face he's got
In Frankland gaol, the murdering ****.
</pre>

Whoohoo! No s needed, spacing and indenting observed!

This however, will be beyond the skills of our darkman...

Jonathan N. Little · Sep 15, 2010

Beauregard said:
This however, will be beyond the skills of our darkman...

I guess he like being in the dark. ;-)

dorayme · Sep 15, 2010

"Beauregard T. Shagnasty said:
I style limericks thusly, because I am a firm believer the 3rd and 4th
lines should be indented

That's because of the Irish blood in you, there is a cute kink in
a crucial gene.

Beauregard T. Shagnasty · Sep 15, 2010

dorayme said:
That's because of the Irish blood in you, there is a cute kink in a
crucial gene.

Irish? <lol> The closest I can come to that is a grandmother who was a
scouse.

picayunish · Sep 15, 2010

I downloaded the page and opened it with DreamWeaver. This is first time
I've ever received this warning when I ran the command fix html (errors).

"The document is nested so deeply, DreamWeaver has had to give up."

Use dirt and pointy finger as editor. It never gives up.

problem with one file	7	Oct 27, 2011
Problem with code	2	Apr 18, 2023
problem with code - and code wariors	5	Sep 13, 2010
Problem with a login script, SESSION user rights and put this together so it works with the other pages and MySQL. Code examples.	2	May 5, 2023
Problem with codewars.	5	Dec 4, 2023
Problem with KMKfw libraries	1	May 11, 2023
Possible PHP/WP problem with code, trouble accessing custom archive links	1	Jan 5, 2023
Problem with displaying character that code number is 219 (after SetConsoleTextAttribute)?	3	Jan 9, 2023

problem with code

thedarkman

rf

dorayme

dorayme

Neredbojias

123Jim

123Jim

Beauregard T. Shagnasty

rf

Jukka K. Korpela

Raymond Schmit

Doug Miller

rf

Phillip Jones

Jonathan N. Little

Beauregard T. Shagnasty

Jonathan N. Little

dorayme

Beauregard T. Shagnasty

picayunish

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads