Freeway does some truly stupid crap with regard to Markup Items that I don’t have any good advice on how to overcome.
###Paragraph much?
When you insert a DIV object (an HTML object) into your Freeway page, Freeway automatically fills it with a paragraph tag <p> even when you put no text into it. In fact, specifically because you put no text into it. So you are left with an empty paragraph <p></p> tag pair that the browser tries to make sense of-- and usually fails. Since paragraph elements (empty or not) still have font-size, line-height and margin characteristics, they tend to take up some vertical space. There are some heavy-handed methods for countering this, not the least of which is the Remove Paragraph action which does just that.
###Span abominations
When you insert a Markup Item in Freeway, specifically as an inline or inflow item, Freeway wants to wrap it in a span tag. Span tags highlight a portion of code, usually to identify it for a style. The span will retain the ID you’ve given the markup item in the Workspace, though not a class.
The problem with this unintended markup on top of your already intended markup is that it produces validation nightmares and more malformed code for your user’s browser to wade through. For example, any div elements in your markup become de-facto children of the enclosing span…
<p class="f-fp"><span id="freeway-generated-unnecessary-code">
<div id="markup-code">
contents…
Fortunately, browsers are very forgiving-- which is still no excuse for serving them bad code. Unfortunately, there is no easy way to fix this, the program itself must be corrected. Good luck with that.
freewaytalk mailing list
email@hidden
Update your subscriptions at: