Comments on: New “comments preview” function, plus bleg

By: jennhi

jennhi — Thu, 01 Mar 2007 17:07:34 +0000

Sure. Feel free to email me if you have questions on rendering bugs in HTML. I do this for a living and would like to contribute.

By: Ampersand

Ampersand — Thu, 01 Mar 2007 09:20:34 +0000

Oh, I get it - you were looking at the source html, not at the php file! No wonder I was confused.

Anyway, you got me going in the right direction, and I think I’ve got it fixed now. Thank you!

By: jennhi

jennhi — Thu, 01 Mar 2007 07:17:59 +0000

The rest of the url was trimmed out so my post wouldn’t overflow across your page. It’s the preview button you’re using right now. Just add the ‘id=”previewbutton”‘ (no single quotes) to that tag.

Sorry, ignore what I said about the slash. I checked the source code and it was just fine — stupid debugging tools were telling me otherwise.

Nevertheless, you may want to get Firebug, which is a genius HTML/CSS/JS debugging tool. I only use it for CSS and HTML and it works wonderfully. It’s a Firefox add-on.

By: Ampersand

Ampersand — Thu, 01 Mar 2007 05:47:14 +0000

Jennhi, thanks!

Two questions.

One, how do I figure out what the rest of the URL is?

And two, where is the “input’s closing slash and the closing bracket”? I mean, there are lots of closing slashes followed by closing brackets; which one did you mean specifically? Or do they all need a space between?

By: jennhi

jennhi — Thu, 01 Mar 2007 02:28:31 +0000

Ah, I see your problem: you removed the top margin for the submit button but the 5px top margin for the preview button inherited for all input fields still remains. You need to assign an id to the preview button then set a style for it. So the HTML output will read:

In the CSS:

#previewbutton { margin-top: 0; }

I noticed in the existing output there was no space between the input’s closing slash and the closing bracket. That might break some people’s browsers, so when you make the edit, can you do that too, please?