Quote:
Originally Posted by alheva
As I said before, it is not only a <div> but a <p> problem as well, when some margin definition is involved.... I guess...  |
Yes, I believe you. As far as I'm aware, even Marvin 2 wasn't perfect in capturing all the margin (etc.) nuances, and it appears that Marvin 3 has some catching up to do so that it at least reaches Marvin 2's levels of rendering of those style properties. I can confirm that during Marvin 3 beta-testing, Kris ironed out some rendering bugs in this area, but, apparently, not all of them as of today.
Quote:
Originally Posted by JSWolf
Turtle91, it is not Marvin overriding the CSS. It's a bug.
|
Definitely. Let's not mention "publisher layout" in this connection at all – in my years of using Marvin, I haven't touched that button
once. The whole point of using Marvin, as I understand it, is to
get away from publisher's layout, thanks to all the wonderful Marvin customization options, right?
But the type of style properties that Alheva talks about definitely should be preserved even when using Marvin's default presentation mode (the customizable one).