- From: Charles McCathieNevile <charles@w3.org>
- Date: Wed, 21 Feb 2001 21:15:03 -0500 (EST)
- To: David Clark <david@davidsaccess.com>
- cc: "W3c-Wai-Ig@W3. Org" <w3c-wai-ig@w3.org>
first guess (wrong! see below) h1, h2, { margin-after: 0em } I think. (I'd need to look at the CSS spec for the various margin properties to be sure. (checks http://www.w3.org/TR/REC-CSS2/propidx.html and finds that it is actually margin-bottom I wanted). h2, h1 {margin-bottom: 0em} there is a bug in the way that this property is implemented in IE3, which means it lets everything start on the same line, like a typewriter that simply moves to the beginning of the line and doesn't do a line-feed. Best way around would be to check the User agent header, in the request for the page, and send a modified page. (Javascript sniffing won't work - there are people running styles but not javascript, and vice versa). (If you are making a modified page (fairly simple filtering) you might like to add a note to the top of it explaining that they are using a browesr that causes some problems and they might like to replace it... Cheers Charles On Wed, 21 Feb 2001, David Clark wrote: Hi, I know that I have done this before, but I am blanking on a way to implement I that will work in today's browsers. I am trying to satisfy WCAG 3.5 by using headers rather than font and size, but I need to remove the extra whitespace after the headers. Any ideas? Thanks, dc --------------- David M. Clark 16 Harcourt Street, #2I Boston, MA 02116 617-859-3069 : 401-679-0239 (eFax) : 617-290-3410 (cell) http://www.davidsaccess.com david@davidsaccess.com -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +1 617 258 5999 Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Wednesday, 21 February 2001 21:15:05 UTC