I’ve two left-floated divs inline inside the main page body. They behave as expected in Preview or in a Browser, however they overlap each other in the Workspace - which makes them impossible to work with.
Am I wrong if I say that, if you overtake the “Master-settings” for those two buddies they work as expected (even in the workspace?
If so, this is one of the mystic approaches of master/child relations where I’m not sure yet how to exact deal with it.
But on the other hand:
Positioning is maybe the real issue of master-setting while box-content (master-content) isn’t for each case.
But what if I don’t mind about master-pages (cause I never used them how they are supposed to use)?
Just had a try and can confirm, that this works as expected.
You see that I’m talking to myself during typing
After seeing this, I have to review my attitude towards master-pages and have to really dive into them cause I see really much possibilities in this that we haven’t had in the past.
i’ve just downloaded your fw-file … it opened with the “damaged” workspace, but after looking to the master-page and coming back to the “untitled page” this misbehaviour was gone - the workspace is like the masterpage again …
I’ve not considered any Master Page issues in this problem. When I try
Dieter’s switching solution, it does not clear up on my iMac…
I’ve gone back and tried to insure there are no Master issues affecting the
page and updated my example. Is there anyone else using floated inline
items and having issues?
–
Ernie Simpson
On Wed, Apr 3, 2013 at 4:43 AM, Dieter email@hidden wrote:
hello ernie,
i’ve just downloaded your fw-file … it opened with the “damaged”
workspace, but after looking to the master-page and coming back to the
“untitled page” this misbehaviour was gone - the workspace is like the
masterpage again …
I just quick tried to rebuild the situation with no further problems.
But If I remove ALL your extra styles - everything works as expected even in your example.
I am more than sure, that one of those extra styles (Do you remember the stair issue a couple of months ago? There it had been a line-height in the body) are affecting some strange appearances in Freeway’s workspace.
But honestly I can’t tell you neither which nor sadly enough why.
Indeed, removing the “space after” attribute (margin-bottom) from the p tag
restored the normal workspace view. Also, changing the measurements for
that value from ems to px also restores the view.
As a work-around, I have input a px value into the attribute, then
over-ridden it with the original em value through the Extended interface.
Hopefully SP will continue to improve their support of relative units.
That must have been a good waste of your afternoon Thank you for
digging out the true problem.
Best, always…
–
Ernie Simpson, aka The Big Erns
On Wed, Apr 3, 2013 at 10:10 AM, Thomas Kimmich email@hidden wrote:
… it is btw the “paragraph space after” that is influencing the
Freeway’s construction view - so this seems buggy?
I’ve gone back to my working project, which is more complex than my example
file, and fixed all the instances of relative sizing in the top and bottom
margins. It is still mis-behaving, so some other issue is still at work.
–
Ernie Simpson
On Wed, Apr 3, 2013 at 10:30 AM, Ernie Simpson email@hidden wrote:
Bravo, Thomas!
Indeed, removing the “space after” attribute (margin-bottom) from the p
tag restored the normal workspace view. Also, changing the measurements for
that value from ems to px also restores the view.
As a work-around, I have input a px value into the attribute, then
over-ridden it with the original em value through the Extended interface.
Hopefully SP will continue to improve their support of relative units.
That must have been a good waste of your afternoon Thank you for
digging out the true problem.
Best, always…
–
Ernie Simpson, aka The Big Erns
On Wed, Apr 3, 2013 at 10:10 AM, Thomas Kimmich email@hiddenwrote:
… it is btw the “paragraph space after” that is influencing the
Freeway’s construction view - so this seems buggy?
Thank you for