Jason Karns wrote:
> I've had this idea brewing in my head for a while now concerning user
> style sheets and I thought I'd run it by the list and get some
> feedback on the idea.
This is a neat idea. I have no input at all on the technical side of
things, but usability-wise I would love to see
> This first one uses list, while the second one uses table.. I want
> to know
> how to get the table-based look using list...
adding this may get you started ...
#content ul li {
clear: both;
padding-top: .5em;
}
best,
jason
--
http://jasondas.com
__
> I think the Css approach for forms very difficult to implement for
> complex forms :-(
Sometimes difficult things are worth doing anyway. Once you do a few,
it gets easier! Complex sets of nested tables are pretty hard, too,
as I recall.
I highly recommend writing out forms in very clear an
I put a Son of Suckerfish menu as the top menu of this site:
http://www.alpinist.com/
( And here's the homepage for SoS menus: http://www.htmldog.com/
articles/suckerfish/dropdowns/ )
My menu behaves fine in all the browsers that matter except IE6. In
IE6, the dropdowns appear, but do not rem
I put a Son of Suckerfish menu as the top menu of this site:
http://www.alpinist.com/
( And here's the homepage for SoS menus: http://www.htmldog.com/
articles/suckerfish/dropdowns/ )
My menu behaves fine in all the browsers that matter except IE6. In
IE6, the dropdowns appear, but do not rem
After years of css+standards+"tables must die"purity I started using
tables again for certain specific layout issues.
I tend to favor less code. So if I can do something instantly with a
table that would take many extra lines of containing blocks and css,
(not to mention extra math and numbe
> (However, note that and are *not* deprecated and are fine
> to use
> when we do not MEAN strong or emphasis. For example it is proper
> to use
> for the title of a magazine article, or for foreign terms. In
> these
> cases we use italics not to suggest stress, but just because that
>
On Aug 24, 2007, at 12:49 AM, WEZ! wrote:
>> I've looked in vain for some kind of CSS hack that would target
>> Safari 2 but not Safari 3. Any ideas?
>
> Only thing I can recommend is finding the largest line height in a
> browsers and formatting the areas for that sizedd browsers.
Adjusting
On Aug 23, 2007, at 10:48 AM, Nick Fitzsimons wrote:
> Safari 2 doesn't really support much in the way of styling for form
> elements. Note that (contrary to some people's beliefs) it is acting
> entirely in accordance with the spec in this:
Fair enough. I guess I'm really open to any ideas that
I'm having a problem with the search box at the top of this page:
http://dev.alp1.deasil.com/
It renders just fine in FF, IE, and Safari 3 (and the nightly build
of Webkit) but is wrong in Safari 2.
In Safari 2, the input #topnavsearchq is too tall, and breaks through
the bottom boundary of
10 matches
Mail list logo
