Code / PHP boxes saga
 

Well i've seen some code in iframes and some codes not in iframes. But it doesn't solve the problem IMO. Not only is it hard to read but you have to copy and paste the code into a text editor before you can read the code.

But at least whole thread display is not ruined by extending to right because of such codes.. :) Expecially Full Releases sections threads were affected very badly.

Well why not actually "wrap" the text instead of putting it in a frame?

That would look ugly and I think someone requested it not to be wrapped.

It would be better if the iframe were bigger

wrapping isn't a solution, as it breaks the code sometimes.

bigger iframes: if we'd do that it'll break the main table again for smaller resolutions, for now i made it so it's combatible with 800x600 and above.

i'll try to make it more dynamical in future, as said it's not final yet

can i just say i hate the iframe and i hate the white, especially when you been smoking and drinking and it's the middle of the night and you're looking thru threads and theirs some bright white thing to blind you :confused: :lol: but seriously can't we get the old ones back, ppl have been using vb for years, surely they've gotten used to the extended pages by now, why make everyone suffer for one or two picky ppl?

the old way isn't possible anymore as vb3 has changed the whole templates so postbits aren't in their own table anymore.

and as i've said several times now, and i don't want to say it just one time more from now on:
vb.org's vb3 style isn't final

granted and i know that but i still felt i should give you my opinion as a vb dev might pop over and see it and fix it.

I find the iframe code tags quite a good idea really.

i have to agree with Erwin.
i wanted iframes in vb2, too, but always were to lazy to do :)

now in vb3, i was forced to do so :)

@sabre:
a) they won't "fix" it as they don't see it as a bug
b) vb.devs don't read that much on vb.org, talking to them on vb.com is the easier way