Re: [WSG] Another plea for help: FF1.0 render problem

2005-02-07 Thread Andrew Krespanis
 Your problem occurs when you have the border-top: 0; after the border
 statement.

Is this a Gecko bug, I wonder?

I doubt it, more likely that border-top:0; is incorrect use of the
shorthand property.
'border-top' is supposed to receive 3 values, border-top-width is what
you would use to set the height to 0.
While it doesn't state either way in the W3C docs, it is my belief
that using '0' for a shorthand property which expects strings (eg: 3px
solid gray; as opposed to :1.5em 2em 1em 4em; for padding, margin or
border-width) is a practice worthy of stearing clear.
border:none; does the same thing, but in a string format.

Much like you could use 'none' as the sole value of the list-style
shorthand property.

Personal preference, but you wouldn't have lost any sleep if you had
used 'none' in the first place ;)

You should also note that using a shorthand declaration without
declaring all values will reset the undeclared values to their
defaults. Here's an example from the CSS2 Rec.:

BLOCKQUOTE {
  border-color: red;
  border-left: double;
  color: black
}

In the above example, the color of the left border is black, while
the other borders are red. This is due to 'border-left' setting the
width, style, and color. Since the color value is not given by the
'border-left' property, it will be taken from the 'color' property.
The fact that the 'color' property is set after the 'border-left'
property is not relevant.

That's another thing you wouldn't have to worry about if you used
border:none; instead of border:0;

hth,
Andrew.


http://leftjustified.net/

**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



[WSG] Another plea for help: FF1.0 render problem

2005-02-06 Thread Leslie Riggs
Hello,
I posted a few days ago, about this puzzler.  Didn't get a response.  I 
REALLY need some help with this from you gurus.

I primarily code for Firefox, then check other browsers, then IE6.  The 
majority of users who will view the pages on this site are IE users, 
however, the fact that I see this rendering problem on the Gecko 
browsers is really bothering me.  The pages validate XHTML 1.1; CSS 
validation comes back with no errors.

I use the same style sheet for both pages.  Both pages reference the 
same DIVs for navigation and the content area.  For some reason that I 
can't fathom, the events page shows a gap between the nav bar (nav) and 
the content area (containall).  The home page does not show this gap.  
I've checked and rechecked, changed this and that, to no avail. 

This only appears to be a problem with Firefox and other Gecko browsers 
(Opera too).  IE6 renders fine.

Can anyone please help me figure this out? 

URL for problem page:
http://www.theonlineworks.com/test/wiscrad/events.html
URL for CSS:
http://www.theonlineworks.com/test/wiscrad/css/mainstyles.css
The links for the dates on the calendars are not working yet; I haven't 
set them up -- I'm too hung up on this issue right now.

If anyone can help, I'd be s thankful.
Leslie Riggs
**
The discussion list for  http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**


Re: [WSG] Another plea for help: FF1.0 render problem

2005-02-06 Thread Jeff Lowder - Accessibility 1st
Hi Leslie

Your problem occurs when you have the border-top: 0; after the border
statement.

If you take this out, it then works the same as in other browsers, strange I
know.

Hope this helps.

Cheers

Jeff Lowder
Accessibility 1st
Ph: 02 9570 9875
Mobile: 0419 350 760
E-mail: [EMAIL PROTECTED]
Website: http://www.accessibility1st.com.au


 From: Leslie Riggs [EMAIL PROTECTED]
 Reply-To: wsg@webstandardsgroup.org
 Date: Sun, 06 Feb 2005 18:35:58 -0600
 To: wsg@webstandardsgroup.org
 Subject: [WSG] Another plea for help: FF1.0 render problem
 
 Hello,
 I posted a few days ago, about this puzzler.  Didn't get a response.  I
 REALLY need some help with this from you gurus.
 
 I primarily code for Firefox, then check other browsers, then IE6.  The
 majority of users who will view the pages on this site are IE users,
 however, the fact that I see this rendering problem on the Gecko
 browsers is really bothering me.  The pages validate XHTML 1.1; CSS
 validation comes back with no errors.
 
 I use the same style sheet for both pages.  Both pages reference the
 same DIVs for navigation and the content area.  For some reason that I
 can't fathom, the events page shows a gap between the nav bar (nav) and
 the content area (containall).  The home page does not show this gap.
 I've checked and rechecked, changed this and that, to no avail.
 
 This only appears to be a problem with Firefox and other Gecko browsers
 (Opera too).  IE6 renders fine.
 
 Can anyone please help me figure this out?
 
 URL for problem page:
 http://www.theonlineworks.com/test/wiscrad/events.html
 
 URL for CSS:
 http://www.theonlineworks.com/test/wiscrad/css/mainstyles.css
 
 The links for the dates on the calendars are not working yet; I haven't
 set them up -- I'm too hung up on this issue right now.
 
 If anyone can help, I'd be s thankful.
 
 Leslie Riggs
 
 **
 The discussion list for  http://webstandardsgroup.org/
 
  See http://webstandardsgroup.org/mail/guidelines.cfm
  for some hints on posting to the list  getting help
 **
 


**
The discussion list for  http://webstandardsgroup.org/

 See http://webstandardsgroup.org/mail/guidelines.cfm
 for some hints on posting to the list  getting help
**



Re: [WSG] Another plea for help: FF1.0 render problem

2005-02-06 Thread Leslie Riggs
Thank you!!
That is a really bizarre quirk, even more so that it works without 
rendering issues popping up in the other browsers.

I shall sleep much better tonight, and have a good report for the client 
in the morning.  Is this a Gecko bug, I wonder?

Thanks again.
Leslie Riggs
Hi Leslie
Your problem occurs when you have the border-top: 0; after the border
statement.
If you take this out, it then works the same as in other browsers, strange I
know.
Hope this helps.
Cheers
Jeff Lowder
Accessibility 1st
Ph: 02 9570 9875
Mobile: 0419 350 760
E-mail: [EMAIL PROTECTED]
Website: http://www.accessibility1st.com.au
 

**
The discussion list for  http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**