Hi Robert,
got the example - thanks.
the "most columns" in the browse is on the last row - there are 5 columns there. So ideally the other "rows" need to span
5 columns as well. the root of your problem is that they don't, and that causes different browsers to display the block in different ways. (not surprisingly IE is the most brain-dead of them.)
Ldq:Qestion, changed from loc:columns to 4
LDQ:QUESTION_NOTIFICATIONS changed from 3 to 2
LDQ:ANSWER changed from loc:columns to 4
That way all 4 "rows" that make up a single browse record, have the same amount of columns - and that means the browser doesn't need to guess anything.
Incidentally, a quick word on loc:columns.
when the first "line" of the browse row is being created, it counts the number of columns used, and puts that answer in loc:columns. This means that if the second, or later rows, need to "span the whole way across" then loc:columns can be used. this can be particularly useful if some columns on the top "line" are optional, and might end up being hidden.
In your case it's the bottom line of the row which has the fixed number (and the most) columns, so this technique is not applicable to this browse.
cheers
Bruce