In verbatim mode, we used to show a horizontal scroll bar. This seem gone now.

-- TW

I still have it.

-- KJL

Could you specify your browser, and provide an example page?

AC

---

Please see the following two examples:

In verbatim mode, we used to show a horizontal scroll bar. 

In verbatim mode, we used to show a horizontal scroll bar. This seem gone now.

In my browser (IE), there are no scroll bars. -- TW

---

Yes, it has disappeared on non-FF browsers. Looking into that.

AC

I see it now.

In normal text it works also in IE.

But not when the verbatim is in the form like in this bug report. Then it only works in FF.

I also tried in IE7 and it behaves like IE6.

KJL

I am not sure if that can be solved (has it ever?). pre inside tables causes browsers to render with unexpected results.

AC

I've delved a bit longer into this (as I recall also did previously) but there is no easy solution. The only browser that resolves pre inside a table is Firefox. Safari and Explorer calculate a wrong width. A solution would be to not use pre inside a table, or to not use a table fo a twiki form layout.

AC

I still don't see the scroll bar.... -- TW

---

There should be a scroll bar in the topic text. There is no scroll bar in the form table.

A solution would be to not use a table but divs to display form data.

AC

---

Aaah. I understand now. This is not the text area, but a form field.

I guess that points to that a text area in a form field should be treated no different from a text area otherwise.... we went out of our way to allow tables, bullet lists, etc. So we should also do the formatting the same way... -- TW

Why can we not use the table? Is there some magic with CSS that does not work?

---

Correct. Browsers need to know the width of a pre block, and this seems to be hard when inside a table. Because when you give the pre block a width of 100%, it will just expand the table, whereas outside of the table the browser understands that 100% is 100% of the containing div.

So I think that ditching the table layout for form content is the way to go. We just need to get used to a new layout.

AC

---

The problem has been fixed enough so that it affects only form fields, and that has been the situation before. Changing to enhancement, and also changing the topic name so that the problem is highlighted.

TW

---

Changed the title as it affects tables, not form fields.

AC

Changed the title as the problem is form fields, not tables in general. As you say, the solution could be not to render a form as a table. -- TW