I’ve made a html graphic box with a border around it and put html text boxes over it. When viewed in a browser, the border breaks up. When the text size is made bigger it gets worse.
Why doesn’t the border grow? Is there a solution to this?
I’ve used “frame a page” method to avoid this with the background image, but I’d hate to redo all that to incude the border, because I’d also have to include another graphic also.
I’ve made a html graphic box with a border around it and put html text boxes over it. When viewed in a browser, the border breaks up. When the text size is made bigger it gets worse.
Not sure what the issue is since an html box and a graphic box are two different things. Did you put a border around an html box, or did you put a border around a graphic box?
Why doesn’t the border grow? Is there a solution to this?
In order to do this, the html item you want to grow must be in-line inside the html item with the border. To do this double click inside the html box with the border until you get a flashing cursor, them from the Insert menu insert an html item. Now click on the height button in the Inspector pallet for the html item with the border so that height will shrink to fit content. Now add your text content to the inline html box.
The border ios around the graphic box. Then I just drew two html
boxes over that and added text to them.
No CSS, just regular html stuff.
If you are using Freeway Express OR if your items are not indicated
as being layers in the Inspector palette - then they are not
positioned using CSS. Otherwise they are. CSS positioning isn’t some
bleeding-edge geek thing, it is something that Freeway Pro users get
automatically just by using layered items in their page designs.
What IS a bit more challenging is the box-model approach to layout, a
very particular technique that uses CSS to produce certain kinds of
arrangements and layout behaviours. This is just one particular
flavour of CSS.
Now, it sounds like you are either using Freeway Express or your
items are not layered. That would explain why your HTML objects are
cutting up your graphic and pushing the parts around as things grow.
One simple solution, if you’re using Freeway Pro, is to make the HTML
boxes layered; just go to the Inspector palette and click the Layer
checkbox for each item. Then they won’t try slicing your graphic into
different parts.
HTML items are never sliced into discrete jigsaw puzzle parts that
can them be pushed apart, so another solution is to use an HTML box
instead of a graphic box for your large bordered item.
But don’t delete and start from scratch: you can actually change a
graphic box to an HTML one by using the Inspector palette; use the
third icon along (the Item Output Settings tab) and change the Type
from whatever it is now (probably GIF) to HTML. Easy, eh?
Other approaches including inserting HTML objects in various ways can
also help and they can allow more sophistication and control, but
those are definitely NOT approaches I’d recommend until you’re more
confident and understand in detail about the different kinds of
objects you use in Freeway layouts and how they behave. (Gives a
stern look to the box-model fans…)
I’m using Pro and am not using layers, right now. I did see that by simply remaking the graphic box as a layer, it doesn’t break apart, though the text over flows it from the html boxes I have over the layered graphic box.
Some of these things I realize are out of my hands once people start fiddling with their browser settings.
I still haven’t gotten the box model to work and so haven’t used it.
OK. Changed my graphic boxes to html boxes and solved the problem.
I tried doing that at one point, but that option didn’t show up. I then found out that it was part of a Combined Graphic, which I guess happens automatically, because I don;t know how it happens.
In fact, once you start “uncombining” graphics, you can run into some problems.
I updated my masters which didn;t update my pages correctly for some reason, so I just dropped down new masters to make new pages. not that big a deal at this point…
