RE: [WSG] .box breaks up on feedback page.
Kathleen R Dery wrote: [...] I am puzzled because the boxes for the lists on other pages are fine with my CSS. It is just the feedback page with the links, the bullets, and the external link icons. This is a good example where using a *logical* debugging process can help immensely, especially when working with CSS and potential browser bugs, and even if you aren't a CSS expert. Based upon your statement above, have you confirmed that the feedback page is in fact ok by removing all the aforementioned content to confirm? Strip it back to the basic template with an empty content column and only your list with the rounded corners and see what happens. If everything is ok, then add the links, bullets etc back in one at a time until you are able to re-create the problem. Once you know which item is the offender, you can better deal with it. FWIW I see the rounded corners just fine in FF 3.015 and FF 3.5. HTH Mark *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
RE: [WSG] CSS list-style
Chris F.A. Johnson wrote:
ul
li class=blackcontent/li
/ul
ul {
color:#380;
list-style-type:disc;
}
ul li.black {
color:#000;
}
Then apparently Michael Brockington wrote:
Chris,
I am not sure what system you tested this on, but it doesn't work on
any system I tried, and indeed it shouldn't: the marker is a part of
the LI not of the UL.
I believe the problem with this is that the list-style-type is inherited
(it's fine to place it on the UL/OL), so with that last rule you find
both the text and the bullet are black. IIRC there's no easy way around
this apart from using an image or a span, as you are already aware.
HTH
Mark
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
RE: [WSG] working with line-height
Joseph Taylor wrote:
David,
What form elements / what browsers do you mean? I'm curious as I
haven't seen
anyone make comments against reset stylesheets as of yet.
To reiterate David's point, I sent the below earlier (but due to server
updates many months ago my *true* email was changed, so it never made
it).
**
Ben,
On the spacing, the spaces you're fighting with are a combination of
line-height, margin and padding.
Each browser will implement their own defaults, so resetting the
defaults with a reset stylesheet has become a popular technique.
Agreed, and there are various implementations out there that do the job,
such as:
http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/
although I personally find that to be slight overkill.
For example, if you apply a line like this to your page:
* {
margin: 0 !important;
padding: 0 !important;
}
You should see everything collapse.
Follow that with a:
line-height: XXpx;
and you should see the results you're looking for.
That's a very big negative, given the use of !important on the global
reset (* {}) such an approach cannot be recommended. Actually, unless
I'm mistaken (and it is possible), the global reset has some issues with
forms and various other elements that once set cannot be undone, and has
since fallen by the way. There are other methods of achieving similar
results however (see Eric Meyer's reset link above). At the very least,
if the global reset is your preferred choice, do *not* use !important
with it or all your margins and paddings are going to disappear on all
elements, and you are in for a world of hurt. Maybe you're a masochist
and that isn't such a bad thing :-P.
HTH
Mark
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
RE: [WSG] working with line-height
Joseph Taylor wrote:
David,
What form elements / what browsers do you mean? I'm curious as I
haven't seen
anyone make comments against reset stylesheets as of yet.
To address the question (oops, forgot about that one) this is all I
could find in my bookmarks, but it is only in regard to the global reset
*{} but that is what David was referencing:
http://www.sitepoint.com/forums/showthread.php?t=517016
And it looks like Georg (as per usual) has a decent working solution for
the problem.
Mark
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
RE: [WSG] Accessible headline 'scroller'
Nick Roper wrote on Saturday, 14 July 2007 at 7:46 p.m. Hi All, A customer has asked for a region of a page to display 'scrolling' news headlines. The example site that they have given is: http://www.imeche.org/ They would like something similar but with the following modifications: 1) Slower rate of traverse 2) Less vertical space so that only one headline is read at a time. 3) Headline pauses momentarily to allow reading and clicking of link. $64K question: is there a way of doing this that is accessible and compliant? I know the specs say to avoid scrolling text, but thought I'd ask anyway. You could take a look at the following: http://onlinetools.org/tools/domnews/ It's fully accessible and meets *most* of the requirements you outlined above. HTH Mark -- This message has been scanned for viruses and dangerous content by ISPNZ's automated virus detection system, and is believed to be clean. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
