What do you want from CSS3?

have your say to help them prioritise

[SuzyUK]

Tell the CSS WG what you want from CSS3 [webstandards.org]

The CSSWG plans to discuss its charter at our next face-to-face meeting in March. If groups like CSS3.info, the CSS Eleven, and the WaSP and/or individuals like Jeffrey Zeldman and Eric Meyer could organize a collectively-written list of priorities and submit it to us before then, we could take that into account when writing our charter for 2008+.

also see: css3.info [css3.info]

Note that they are not looking for feedback on syntax, and would like you to try to check the latest draft modules to see if your proposal is already possible. What they are looking for is for people who use CSS extensively to let them know if there is some functionality that is missing, and would be useful, but is not in current specs.

[swa66]

Multiple background images can be useful beyond borders.

e.g.:

Have a patterned background repeated in e.g. 5% grey.

Next have a company logo in e.g. 7% grey on top of it centered (are centered backgrounds both vertically and horizontally in the spec? [never needed to use it so far, so I don't have a clue, might be available already])

Have a slanted text (rotate text in the standard , generated text as background?) stating DRAFT in 20% grey across it all.

[HelenDev]

You're right Dabrowski - only just read that bit :)

It looks like there will be border-edge images as well as border-corner images, which is good because I was thinking that as soon as rounded corners become available everyone will want even more fancy corners!

[carsten888]

some more I thought of:

- style including

.blue{
background: blue;
}

.sky{
font-size: 0.8em;
include-style: .blue;
}

- no_javascript pseudoclass
for accesability it would be usefull to make it possible to overwrite styles when javascript is not active. I use a workaround for this:
with unobtrusive javascript onload put a class to the container so I can then overwrite the styles like:

div#container.no_javascript div.header div.text_enlargement{
display: none;
}

just having a no_javascript class would be sooo much easyer:

div.text_enlargement:no_javascript{
display: none;
}

- accessible build in class. only visible when css is disabled.
for accesability you want to include skiplinks and headers to particular parts of content on a page. Those are only visible for users who use browsers without css (like braille-browsers and such). workaround I been using so far:

.off_screen{
position: absolute;
left: -9999px;
}

would be nice to have this build in css so the above does not need to be in stylesheet anymore. so code on page would be:

<ul class="accessible">
<li><a href="#content">content</a></li>
<li><a href="#menu">menu</a></li>
</ul>

(just if you are bored: try calculate how many bytes of traffic that would save worldwide!)

[vincevincevince]

It would be great to be able to combine absolute positioning and float commands. This would mean that the element is putatively positioned at the position:absolute location; but then floats in the direction(s) specified until it is able to find a space.

This would mean true separation of semantics and presentation as you could write your menu, ad block, title, text, etc. in the same order for all the sites you make; and use CSS to have them arrange themselves as closely as they can to your absolute positioning. i.e. if you wanted a menu on the right; then fix a x coordinate somewhere to the right of where you set the main content, and it will float itself out until it passes the main content. Footers likewise would be pushed to the bottom just by setting a y coordinate lower than the y coordinate of the main content.

[Clark]

I wish there were some simple ways to do what tables does in an easier way. For example a left and right float on the same line, vertically aligned, without testing and testing and testing...

Something they should add is a "clear" property that applies to the area AFTER that same element when a float is declared.

Because if you do not want elements below a floated element to wrap around it, you must apply the clear property to the following element using "clear: left", "clear: right" or "clear: both".

This means that you can't fully semantically separate sections because if you have 3 sections, the middle one being floated, then the following one needs a clear, and if it's just switched with the first section, you may need to remove the clear on one, and add it on the other. Why should the location of a section cause you to change the markup?

I hope I explained it well enough to be understood.