I am really getting mad at HTML.?

@Reserved: I'll be replying to this in a bit.

@Edit: Sorry about the wait :)

Here are things that you're doing incorrectly:

- Using Marquee.

- Using in-line styles.

- Using a table based layout. (Tables are used for tabular data, i.e: graphable data. There is nothing graphable about this data.)

- Using table@width. (The fact you set it to 100% is a hint that you didn't need a table.)

- Abusing the <b> element.

- Unnecessarily using <span>.

- Non contextual label for an anchor like "here". (Copy the link into notepad. Now guess: Where are you going?)

@Edit: (2nd though, I missed that last part, you may want to do the other answerer's NbSp thing combined with mine. I might be able to come up with a solution, but it'll take a while, and I've ran out of space.)

Don't ever use Marquee. It's not part of HTML. It isn't well supported. It was made by browser vendors, and it was a huge mistake. This is actually the first time I've seen some one seriously suggest that they used it :P (Where did you even learn to use that?)

Use HTML for content, structure and meta-data.

Use CSS for styling. Keep all style here.

Use Javascript for behaviour. Keep all behaviour here.

Marquee is somewhat like a blend of style and behaviour.

This is what that HTML should look like: http://pastebin.com/gbedNs8h

This is clean, simple, and maintainable. I used a footer because it sounded like it was a footer, but if it's something else, just replace <footer> with that something else. The ID I used was "support" because it sounds like support information.

Then you can use CSS style sheet (put it in a separate file and link to it) to style it: http://pastebin.com/w4RHKXxw

Note: I assumed 16px font. However, the padding should be specified with ems for vertical units, percentages for horizontal units.

Generally use ems for vertical units and upper limits on widths; percentages for all remaining horizontal units; ems or pixels for borders and outlines (it really depends on what they're for), pixels for the root element's margins (keep them small, 8px is usually enough), lower limits on widths, heights.

Your main content should have an explicit max-width which your percentage units are going to be based on. It should be about halfway between 2 and 3 upper-case alphabets in a font of your choosing. Try out different sizes and pick the one that looks best to you.

Pixels are rarely used, but come in handy with some animations.

Last, I really really really recommend against it, but you can use Javascript to marquee. The big advantage of JS is it keeps your mark-up legible and clean, and can be turned off if it gets annoying. As a rule do NOT animate any thing on your page without the user's permission. In my example, I speed up the scroll until it's all visible then stop when the user hovers over it. I also provide a start/stop button.

The script is in three parts:

- A library: http://pastebin.com/bqvTu8Fm (place as last line in the document head)

- A closure: http://pastebin.com/embz2e47 (place as last line in the document body)

- A style sheet: http://pastebin.com/0NNAEFbA (holds all static styles, should name "marquee-style.txt" and in same directory as the closure.)

Always put library scripts as the last line of the head. Always put closures and things that operate on the body of the document as the last line of the body. This ensures that priority scripts are defined before needed, but low priority scripts don't load too early.

The library makes a namespace comYahooAnswersPuckettTim .base for all of your common commands to minimize polluting the global namespace. I picked a long name that can be identified back to you. You can pick a different name if you want. Generally, it's the reverse URL of your website according to Java practices.

The style sheet is very barebones. You can add things to it, just make sure they're things that will only be part of the marquee(s). Use your general style sheet for every thing else. E.g: You can use "marquee-style.txt" to style the start/stop button.

This can easily be adapted to operate on multiple elements by doing these things:

- Make the closure into a library with a name space, perhaps comYahooAnswersPuckettTim .marquee.

- Add a parameter, el, to accept any element and replace document.getElementById("support") with (el).

- Rename variables for clarity of code.

- Edit the style sheet, maybe make the script add a className to each marquee parent and use that instead of #support in the style sheet.

- Make a closure that calls addMarquee for every element by ID that needs a marquee.

If you would like explanations, be sure to email me :)

You should see the advantages right away. This is opt in and useable for the user, and infinitely more customizable by the admin. Hope this helps! :)

http://pastie.org/8616047