little CSS tweaks, as req. by Justin & Alfred

Dada Mail » Dada Mail Developers » Archives » little CSS tweaks, as req. by Justin & Alfred

From: "Shane Clintberg" ...@telus.net>
Subject: little CSS tweaks, as req. by Justin & Alfred
In-Reply-To: Re: regarding additional CSS classes
Date: July 31st 2005

> > are you *sure* you don't want me to
> > add [redundant input-type classes]
> > in?

> Yes :)

...And it's a good thing you said that, too: I've since realized there are easier & far less bloated ways of dealing with the IE radio button/checkbox border problem, Alfred's vert-align bug, ...and hopefully anything else we come across.

First up: I clued into the fact that the checkbox-border thing can be written out with only one IE expression hack:

/* for IE 5.0+: */
input {
    border: expression(this.type=="checkbox"? 'none':
                       this.type=="radio"?    'none':
                       'default');
}

Easy-cheesy, so I've added it into rev. 1.20 of "default_css.css" ...which I now highly recommend. :-)

And the vert-align fix is easier still: just don't specify any padding in the CSS file's input selector. I haven't changed this on the CVS, however, because I have a feeling Justin may disapprove of the aesthetics. [N.B. - I'm an artist too...which almost guarantees we're going to disagree here. :-) ]

First, here's how things currently look (wth 3px of padding) in the main browsers I test with:

Firefox/Win pads the buttons & text fields but not <input type="file">:

Whereas IE6/Win pads the buttons & file-upload widget, but not the text fields:

Incidentally, you can test these yourself by using the latest version of "test_layout_screen.tmpl".

Okay, now here's what you get when you remove "input {padding:3px;}" from the CSS:

Firefox/Win:

And IE6/Win:

Personally, I like this latter, svelte (and a little more consistent with the default Web buttons) option. But, hey, the big, bulbuous buttons are good too.

> If you can figure out a better way to get the same/similar layout to
> tables in regards to the admin screens and their preferences, I think
> we'd be in awesome shape

Yup, that sounds like enough of a challenge. :-) I'll see what I can do....

Attachments:

<< Previous: Re: regarding additional CSS classes

| Archive Index |

Next: spelling conventions: opinions welcomed! >>

(archive rss , atom )

This mailing list is to discuss the nerdy programming development of Dada Mail -

If you are *just* looking for support Dada Mail, consult the message boards at:

http://mojo.skazat.com/support/boards

To post to this list, send a message to:

dadadev@dadamailproject.com

All subscribers of this list may post to the list itself.

Some on topic... topics include:

* Positive Crits on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
* Bug/Error reports
* Bug fixes
* Request For Comments on any changes to the program
* Help customizing Dada Mail for your own internal needs
* Patches
* Language Translations
* Support Documentation/Doc editing, FAQ's, etc.
* Discussion of any changes that you would like to be committed to the next version of Dada Mail -

At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.

Please, please please familiarize yourself with the documentation at:

http://mojo.skazat.com/support/documentation/

Since no one wants to answer the same question twice.

Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.

*NOTE* - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.