If we had the <tr> in the issue list reading the bug status as class <tr
class="resolved">, we could probably have rejected or resolved issues
differently coloured for easier recognition.

In the screenshot, you see the <td> table cell reading the status highlighted.
If classifying of <tr> isn't possible, I could try to make the  <td> differently
coloured if it is marked by a class.

Done. Please get back to me if you're unhappy.

<tr>
  <th>
    <br>
    <br>
  </th>
  <form action="issue422" class="second_comment_box"
enctype="multipart/form-data" onsubmit="return submit_once()"
name="itemSynopsis" method="POST">
  </form>
</tr>


<tr>
  <td colspan="3">
    <textarea cols="80" rows="5" wrap="hard" name="@note">
    </textarea>
  </td>
</tr>



This doesn't look right. :-)

I'm pretty sure this is unrelated to this ticket! Can you check your report?

Well, he problem is that there is nothing inside the <form></form>

So I can set padding or margin as I want, but in the end, there is nothing to
add a margin, padding to.

form {
  min-height: 1337px; /* or whatever */
}

give girth to an empty form

instead of 


	<tr></tr>
	<tr></tr>
	<th><br /><br /></th>
	<form method="POST" name="itemSynopsis"
       onsubmit="return submit_once()"
       enctype="multipart/form-data"
       class="second_comment_box" action="issue422">

	<tr>

	 <td colspan="3">
	  <textarea name="@note" wrap="hard" rows="5" cols="80"></textarea>
	 </td>
	</tr>
	<tr>
	 <td>
	  <input type="hidden" name="@template" value="item">
	 </td>

	 <td colspan="3">
	  <input type="hidden" name="@lastactivity" value="2011-08-04.13:49:10">
<input type="hidden" name="@action" value="edit">
<input type="submit" name="submit_button" value="Add Comment">




, something like


	<tr></tr>
	<tr></tr>
	<tr>

	 <td colspan="3">
	  <textarea class="second_comment_box" name="@note" wrap="hard" rows="5"
cols="80"></textarea>
	 </td>
	</tr>
	<tr>
	 <td>
	  <input type="hidden" name="@template" value="item">
	 </td>

	 <td colspan="3">
	  <input type="hidden" name="@lastactivity" value="2011-08-04.13:49:10">
<input type="hidden" name="@action" value="edit">
<input type="submit" name="submit_button" value="Add Comment">



may do it (I hope).

Shouldn't there be a <form> somewhere?

I'm not sure if I necessarily need it.

With my proposal from above, I'd try

[...] tr td textarea[class="second_comment_box"] {
    padding: bla
    margin: bla
    bla bla
}

I don't see how the comment box will work without a form input... ?!

If you submitted the form with some Javascript on the button then I supposed you 
wouldn't need the <form> (<input type="button" onclick="function_to_send()" />), 
but I don't see how else it would get submitted, and I can't imagine Javscript 
would really be preferable over a form?

You're right, Javascript isn't preferable.
-- 
Greetings, 
A. Huillet

Too old, and not needed (RoundUp is to be replaced...)