2011-06-13 6:50, Bob Rosenberg wrote:
I would have loved to knock it out in a table, but the widgets
necessary by the third party are not set up for tables... at least I
don't believe that are.
[...]
When you talk about widgets I assume that you are using something to
generate the HTML code for the page.
There might be widgets that operate on elements of the page, expecting
to find specific element types, ids, names, etc. The page design has
some oddities that suggest such features - for one thing, if you turn
CSS off, you see lots of error messages ("hidden" with display: none,
presumably to be turned on with JavaScript).
The styling issue would indeed be much simpler (or turn to a non-issue)
if simple table markup were used. There's so much play with floating on
the page that things get risky, partly because floating rules often
surprise human intuition, partly due to bugs in implementation of
floating in browsers.
Things would also be easier if the markup errors on the page were fixed
first, just to make sure they don't cause some of the problems.
> If each entry is being generated
individually, you might still be able to slip a <br /> before each
<label> which will give you the wrapping that I suggested as an
alternative to a table.
You can more or less achieve the same effect in CSS by making an element
displayed as a block element, e.g.
#postalCode { display: block; }
I think the page also needs
#submitArea { clear: left; }
--
Yucca, http://www.cs.tut.fi/~jkorpela/
______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
