Re: [WSG] xhtml strict break tag bug?

2006-11-18 Thread sharron

Thank you all for the help and your time.
The site owner has instituted a list format for the menu.

I'd like to know why the break tags as she was attempting to use them would 
not work correctly, when I use xhtml strict on my own site and don't have 
that issue.


I was conviced her problem was related to the css, but the css was validated 
as was the html, but as soon as you added the strict doc type it went 
haywire.



Again Thank you all!

ps I also pass on the reccomendation to remove the tabindex stuff.





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread sharron
 
  Maybe should mention that these are menu links that she.





  having a go trying to help a friend figure out why, in xhtml strict 1.0 the 
br / that are styled in the css style sheet  as follows:  .sidemenu br 
{line-height: 3px; .

  However in FF, Netscape and Mozilla it would appear the css style is being 
ignored. The space is too high

  IE and Opera seem to render it the way she intended. Have googled xhtml 
strick break tags bugs but have not found anything so far.

  This does not happen in her xhtml transitional version.

  Side note: I've noticed in her html she is using tabindex, is that standard?

  ps Thanks for all the responses to the form question I had asked. 

  Sharron

  ***
  List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
  Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
  Help: [EMAIL PROTECTED]
  *** 


--


  No virus found in this incoming message.
  Checked by AVG Free Edition.
  Version: 7.0.409 / Virus Database: 268.14.6/536 - Release Date: 11/16/2006


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***


Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread David Dorward
On Fri, Nov 17, 2006 at 08:19:17AM -0600, [EMAIL PROTECTED] wrote:
having a go trying to help a friend figure out why, in xhtml strict 1.0
the br / that are styled in the css style sheet  as follows:  .sidemenu
br {line-height: 3px; .
 
However in FF, Netscape and Mozilla it would appear the css style is being
ignored. The space is too high

It doesn't make much sense to set a line-height on a line break, which
is just a point at which one line ends and another begins. Setting
line height on the paragraph (or whatever) the break is inside would
make more sense.

Side note: I've noticed in her html she is using tabindex, is that
standard?

http://www.w3.org/TR/html4/index/attributes.html

-- 
David Dorward  http://dorward.me.uk



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread David Dorward
On Fri, Nov 17, 2006 at 08:36:32AM -0600, [EMAIL PROTECTED] wrote:
  Maybe should mention that these are menu links that she.

Menu links separated by line break elements?

But a menu is a list of links isn't it?

http://css.maxdesign.com.au/listamatic/

-- 
David Dorward  http://dorward.me.uk



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread ~davidLaakso

[EMAIL PROTECTED] wrote:
having a go trying to help a friend figure out why, in xhtml strict 
1.0 the br / that are styled in the css style sheet  as follows: 
 */.sidemenu br {line-height: 3px;/* */./*

*//* [trimmed]
Sharron

A clickable link to this page would help. Otherwise it is a guessing game.
With a simple list /one/ alternative is to assign line-height to the ul. 
No br  / needed. And, either way, using px for line-height is not a 
good idea. Try a raw number.

ul {
 line-height: 1.75;
}
ul
lia href=#stuff/a/li
lia href=#more stuff/a/li
lia href=#even more stuff/a/li
/ul

If the goal is to have a one of /unique/ space, I suppose you could use:
br.lead {line-height: 3.5;}
br class=lead /
Best,
~dL

--
http://chelseacreekstudio.com/



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread sharron


I've asked the site owner if I can submitt a link. I will if she gives 
permission. However I did try this and it seems to work.


.sidemenu {
font-size: 13px;
font-weight: bold;
width: 100%;
display:block;
margin-top:0;
padding-top: 0;
margin-left: 0;
line-height:20px;
}
.sidemenu br {line-height: 3px;margin-bottom: 
2px;margin-top:2px;display:block; }





[EMAIL PROTECTED] wrote:
having a go trying to help a friend figure out why, in xhtml strict 1.0 
the br / that are styled in the css style sheet  as follows: 
*/.sidemenu br {line-height: 3px;/* */./*

*//* [trimmed]
Sharron

A clickable link to this page would help. Otherwise it is a guessing game.
With a simple list /one/ alternative is to assign line-height to the ul. 
No br  / needed. And, either way, using px for line-height is not a good 
idea. Try a raw number.

ul {
 line-height: 1.75;
}
ul
lia href=#stuff/a/li
lia href=#more stuff/a/li
lia href=#even more stuff/a/li
/ul

If the goal is to have a one of /unique/ space, I suppose you could use:
br.lead {line-height: 3.5;}
br class=lead /
Best,
~dL

--
http://chelseacreekstudio.com/



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread Mel

on 17/11/2006 14:36 [EMAIL PROTECTED] said the following:


Maybe should mention that these are menu links


If this is a menu, she should be using a list - not line breaks - for a 
whole host of reasons. Styling the padding/margins on the list elements 
then becomes a lot easier.


I'm not convinced that br / *should* be stylable in the way she sems 
to want. It's not a page element as such, merely a signal to perform a 
carriage return and line feed when redenring. As such the line height 
should be the same as that set for the rest of the paragraph.



This does not happen in her xhtml transitional version.


It could be that FF and Moz are being thrown into 'almost standards' mode:

http://developer.mozilla.org/en/docs/Gecko%27s_Almost_Standards_Mode


Side note: I've noticed in her html she is using tabindex, is that
standard?


Yes - it's compliant and valid markup but unless there are *really* good 
reasons for specifying tab indexes, I suggest she removes them and 
checks that the natural, unindexed, tab order is intuitive (ie 
top-to-bottom, left-to-right for a Western page). If the page has been 
manually checked for keyboard navigation accessibility, any warnings 
from accessibility parsers can be safely ignored.


Mel






***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread sharron

http://www.webado.net/webado-net-tpl.php is transitional
http://www.webado.net/webado-net-tpl-strict.php is strict

the above are links to her two pages. These are on her server and do not 
reflect any of the playing I've done. lol


I wonder too why the breaks and not a list for the menu? I will advise about 
the possible tabindex interference with browser tabindex or whatever you 
might call it.












***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread Thierry Koblentz
[EMAIL PROTECTED] wrote:
   Maybe should mention that these are menu links that she.

Unless I'm missing something, these BR elements could be replaced with a
simple display:block declaration.
On the other hand, I have a question regarding accessibility: is a BR
element as good as a printable character when it comes to separate these
links?

---
Regards,
Thierry | www.TJKDesign.com



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread Thierry Koblentz
[EMAIL PROTECTED] wrote:
 http://www.webado.net/webado-net-tpl.php is transitional
 http://www.webado.net/webado-net-tpl-strict.php is strict

Now that I've seen the links in context, I wonder why are the BR for?
I guess they are here in case the document shows without styles applied. But
that would be more reason to use a UL :)

---
Regards,
Thierry | www.TJKDesign.com



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread sharron

http://www.designbyatfb.com/temp-images/xhtml/index3.html
above is the best I can do, remember I am an amatuer. Netscape and Mozilla 
are ignoring a few br / tags in the html between the Webado shop and 
Policy links, have no idea why.






[EMAIL PROTECTED] wrote:

http://www.webado.net/webado-net-tpl.php is transitional
http://www.webado.net/webado-net-tpl-strict.php is strict


Now that I've seen the links in context, I wonder why are the BR for?
I guess they are here in case the document shows without styles applied. 
But

that would be more reason to use a UL :)

---
Regards,
Thierry | www.TJKDesign.com



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread Niels Fröhling
 having a go trying to help a friend figure out why, in xhtml strict 1.0 the 
 br / that are styled in the css style sheet  as follows:  .sidemenu br 
 {line-height: 3px; .
 
 However in FF, Netscape and Mozilla it would appear the css style is being 
 ignored. The space is too high
 
 IE and Opera seem to render it the way she intended. Have googled xhtml 
 strick break tags bugs but have not found anything so far.
 
 This does not happen in her xhtml transitional version.

 'line-height' changes the height of lines inside an element. The ambigous
case where an element is the content too (img, br, hr, ...) it only changes
it's own 'line-height', not the one of it's parent or sisters:

 span style=line-height: 1em;
   white-spacebr style=line-height: 0.5em; /
 /span

 does not affect the span's line-height, and not the 'white-space' string,
and in effect does nothing at all.

 Which I count as good behaviour, because it's really uggly if you put
for example:

 span style=line-height: 4em;
   img src=bla.png style=display: inline; line-height: 2em; /
   img src=bla.png style=display: inline; line-height: 3em; /
   img src=bla.png style=display: inline; line-height: 4em; /
   img src=bla.png style=display: inline; line-height: 5em; /
 /span

 What's the line-height in XHTML Trans (where the line-height bleeds to
it's parent and neighbours)? [rethorical question]

 My suggestion is not to use it _in_ the text, but _on_ the text (p, div).
Favourably, and if you can, only on block-elements.

 Ciao
Niels


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread Thierry Koblentz
[EMAIL PROTECTED] wrote:
 http://www.designbyatfb.com/temp-images/xhtml/index3.html
 above is the best I can do, remember I am an amatuer. Netscape and
 Mozilla are ignoring a few br / tags in the html between the Webado
 shop and Policy links, have no idea why.

That's because you have *3* BRs in between these two links instead of one.

But as I said, I don't see the purpose of these elements unless in the case
the document would appear unstyled.
So I think an easy way to take care of the whole thing is to use CSS to get
rid of them rather than trying to style them.
Try this:
.sidemenu br {display:none}
.sidemenu a {margin-bottom:2px}

That way, you can even keep the three BRs :)

---
Regards,
Thierry | www.TJKDesign.com



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread Mel

on 17/11/2006 16:46 Thierry Koblentz said the following:

snip



On the other hand, I have a question regarding accessibility: is a BR
element as good as a printable character when it comes to separate these
links?


No. As far as I am aware, it's equivalent to use whitespace to separate 
links - which means that it could create probems for some users. I'm not 
sure if JAWS 7 can audibly separate the links itself. Certainly, older 
screen readers will have problems and, probably, anyone using a braille 
display.


Mel



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] xhtml strict break tag bug?

2006-11-17 Thread Thierry Koblentz
Mel wrote:
 No. As far as I am aware, it's equivalent to use whitespace to
 separate links - which means that it could create probems for some
 users. I'm not sure if JAWS 7 can audibly separate the links itself.
 Certainly, older screen readers will have problems and, probably,
 anyone using a braille display.

That's what I thought.
Thanks Mel.

---
Regards,
Thierry | www.TJKDesign.com



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***