Re: [WSG] Link spacing in UL

[Tony Crockford]

Paul Bennett wrote:

What about using a definition list?


Thanks, but 
A) it's a pig to style (I can't seem to get each di to display as a list item for a start

B) it's not really a definition list, semantically


is it really a list item?

given that you have a full paragraph of text and a link, I'd have 
thought it was more semantically a definition list (if you have 
several of these groups)  or more likely



  
  


and dl's don't have di's (if that isn't a typo)


  The paragraph
  
  The paragraph
  
  The paragraph
  
  The paragraph
  


would be much cleaner code. than a ul with list items containing two 
elements.


;o)






**
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] Image Replacement

[Thierry Koblentz]

Paul Bennett wrote:
>> Paul,
>> If you're using an img element already, you may want to try this:
>> http://www.tjkdesign.com/articles/tip.asp
>
> Thanks Thierry, but (unless I'm mistaken) I'd need a separate style
> rule for each page containing an H1, as all the images are a
> different size.

You could make all images the same width as the larger one so there is no
need to change the rules.
If you're using them for h1 that shouldn't make the page much heavier (one
h1 per page).
I'm not pushing for it, just giving a workaround for people who may be
interested in the technique.

> Thanks anyway,

You're welcome.

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



**
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] Link spacing in UL

[Paul Bennett]

>What about using a definition list?

Thanks, but 
A) it's a pig to style (I can't seem to get each di to display as a list item 
for a start
B) it's not really a definition list, semantically

I got the anchors in the ul to work using this:

ul#private li a {
display: block;
margin: 10px 0 10px 0;
width: 10%;
white-space: nowrap;
}

That way, the link pushes the width wider than 10% (due to not being able to 
wrap the text in the element, but the 'clickable' area of the link is only 
where the text is (i.e.: it doesn't stretch across the whole container).

Tested successfully on IE7, FF and Opera so far.

Paul


**
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] Image Replacement

[Paul Bennett]

>Paul,
>If you're using an img element already, you may want to try this:
>http://www.tjkdesign.com/articles/tip.asp

Thanks Thierry, but (unless I'm mistaken) I'd need a separate style rule for 
each page containing an H1, as all the images are a different size.

My current solution is working fine without any unnecessary jiggery-pokery.

Seeing an image outline when images are turned off isn't a big deal for this 
particular project.

Thanks anyway,
Paul


**
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] Image Replacement

[Thierry Koblentz]

Paul Bennett wrote:
> Hi all,
> 
> I'm fighting through the wads of info (and opinions) out there about
> CSS image replacement. 
> 
> I'm concerned that using CSS like:
> text-indent: -9000px;
> may get our site penalised by search engines.
> 
> Feeling overly pragmatic, I added the following to a page in
> development: 
> 
> 

Paul,
If you're using an img element already, you may want to try this:
http://www.tjkdesign.com/articles/tip.asp

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


**
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] Need help with vertical "accordian" menu

[Thierry Koblentz]

morten fjellman wrote:
> Hi,
> I need to make a menu (link to image:
> http://www.fjellman.no/test/meny.gif ) that does what the linked
> image describes. The idea is to have the id of the body determine
> what menu item is active and then reveal the links under that item. I
> was hoping to do this all in css, but can't get my head around where
> to start. Also, if this is not possible with css alone, what issues
> of accessebility are there? I have not made this kind of menu before
> so I'm kinda fumbling in the dark here. Source, tutorials or a push
> in the right general direction is appreciated.

I think building this type of menu using the pseudo-class :hover would
create usability issues.
These are not CSS menus, but they do the "accordian" thing:
http://www.tjkdesign.com/articles/TJK_SlideMenu/TJK_SlideMENU.asp
http://juicystudio.com/article/ecmascriptmenu.php
http://www.onlinetools.org/tools/puredom/index.html

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



**
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] Image replacement and printing

[Thierry Koblentz]

Ryan Sabir wrote:
> Hi all,
> 
> We've just been investigating using Fahrner Image Replacement, or one
> of its more accessibility friendly derivatives, when we came across
> the problem of printing.
> 
> It seems that in IE the default option is to not print background
> images and colours. So a person printing our web page will not be
> getting any of the headings that have been replaced with images.
> 
> Has anyone found a solution to this? I really like the idea of
> specifying heading text in a Hx tag and replacing it for the user, but
> most clients aren't going to go for it if the user has to fiddle with
> their settings to get it to print.

Ryan,
You may find this useful:
http://www.tjkdesign.com/articles/tip.asp
---
Regards,
Thierry | www.TJKDesign.com


**
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] Link spacing in UL

[Ben Wong]

On 20/07/06, Paul Bennett <[EMAIL PROTECTED]> wrote:

Hi all,

I'm trying to achieve the following:
-
* list item - loads of text here. loads of text here.loads of text here.
  loads of text here.loads of text here.loads of text here.loads of text here.

  http://link.here
--

(note the line break between the link and the list item text)

I want to have a visual break between the text and the link without having to add a 
pseudo-structural element to force the gap (eg: the awful ' ').

I have the following CSS:

ul#private li a {
display: block;
margin: 10px 0 10px 0;
}

This has the desired visual effect but unfortunately, setting the link to 
display block means I can run the mouse over text WAY to the right of where the 
link text ends and the link is activated.

Can anyone think of a pure CSS & structural html way of achieving this?


What about using a definition list?


  [list item] - [lots of text...]
  ...
  ...



--
Ben Wong
e: [EMAIL PROTECTED]
w: http://blog.onehero.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] Link spacing in UL

[Paul Bennett]

Hi all,

I'm trying to achieve the following:
-
* list item - loads of text here. loads of text here.loads of text here.
  loads of text here.loads of text here.loads of text here.loads of text here.

  http://link.here
--

(note the line break between the link and the list item text)

I want to have a visual break between the text and the link without having to 
add a pseudo-structural element to force the gap (eg: the awful ' ').

I have the following CSS:

ul#private li a {
display: block;
margin: 10px 0 10px 0;
}

This has the desired visual effect but unfortunately, setting the link to 
display block means I can run the mouse over text WAY to the right of where the 
link text ends and the link is activated.

Can anyone think of a pure CSS & structural html way of achieving this?

Thanks,
Paul


**
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] Preparing accessibility policies/standards in readiness for WCAG2.0

[Ben Buchanan]

I'm interested in the experiences of other universities/organisations
preparing internal accessibility policies or standards in readiness for
WCAG2.0.


At this stage I'm taking the "wait and see" approach.


If you were to update your policies/standards, what would be the major
changes?


Realistically our accessibility standards focus more on the
practicalities anyway, and mostly use references to WCAG 1.0 as a
benchmark or a way to add credence to what we're saying.

So, in some senses what we probably wouldn't change much anyway.


What sense have you made out of the guidelines and how would you interpret
them for you developer base? What resources would you provide?


None and I wouldn't try right now :)

We'd be most likely to provide code/snippet libraries to our
programmers and validation tools to everyone. Actual accessibility
checking needs to be taught in workshops or some similar format, so
again practical techniques would win out over expecting anybody else
to read a W3C document.


(I know all of this is a little premature given WCAG2.0 is still in draft
but if you were to start updating your existing policies/standards, what
would your priorities be?


Priorities would remain much the same:
1) provide the best possible result for the user, based on available
information.
2) conform to standards like WCAG
3) conform to legislation

They're all important so the order doesn't really matter, but our
intention is a good result and NOT just "ticking the box". I would
imagine that's the case for most readers on the list :)

cheers,

Ben

--
--- 
--- The future has arrived; it's just not
--- evenly distributed. - William Gibson


**
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] Adding css files from JavaScript?

[Geoff Pack]

 
Janette Girod
> 
> This is the code I tested:
> var new_ss = document.createElement('link');
> new_ss.setAttribute('href','extra.css');
> new_ss.setAttribute('rel','stylesheet');
> document.getElementsByTagName('head')[0].appendChild(new_ss);
> 
> It works in Win/IE5+, FF 1.5, Opera 9, Netscape 7+,
> Safari, & Camino.
> 
> It doesn't work in Mac/IE. 
>

Also works in Opera 7, 8, 8.5
and Netscape 6.2 (but not 6.0)

cheers,
Geoff.




==
The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments
==


**
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] Site check - take two !

[Joe]

Felix,

Why is it that every discussion with your name attached seems to contain a
rude comment?  Rachel had already stated the fact that it did not look right
in FireFox.  Please provide constructive criticism next time.

> -Original Message-
> From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED]
> On Behalf Of Felix Miata
> Sent: Tuesday, July 18, 2006 11:17 PM
> To: wsg@webstandardsgroup.org
> Subject: Re: [WSG] Site check - take two !
> 
> On 06/07/18 10:56 (GMT-0400) Rachel Cardinal apparently typed:
> 
> > HYPERLINK http://www.gcgs.ca/
> 
> Kinda messed up I think: http://mrmazda.no-ip.com/SS/rachca1.jpg :-p
> 
> HTH
> --




**
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] Preparing accessibility policies/standards in readiness for WCAG2.0

[Mike at Green-Beast.com]

Scott wrote:
>> WCAG2.0 is still in draft but if you were to
>> start updating your existing policies/standards,
>> what would your priorities be?

Mike wrote:
> At this point in time I have no intention of even
> acknowledging the existence of WCAG 2 [...]

No argument from me, Mike. To answer your question Scott I plan to do 
nothing. At some point I will adopt new practices that make sense, whether 
they are part of the WCAG 2 or not, but at this point I won't subscribe to 
the draft. Currently, unless I am compelled to change my mind, my priorities 
will be the same tomorrow as they are today: To try and make my sites as 
accessible and as usable as possible without foregoing the ever-important 
elements of appealing design and SEO and everything else that goes into 
making a marketable site.

In the US the speed limit on our highways was 55 miles per hour. Later it 
was upped to 65 on most major routes. Made sense. Most everyone, myself 
included, was driving about 65 anyway. Prior to the change people didn't 
drive to be within the letter of the law, they drove as they saw fit, and to 
stay with the flow of traffic, just like it is today. The lawmakers 
eventually saw it through the eyes of the drivers and met our needs instead 
of demonstrating belligerence. In my mind, the same applies here. I have 
little interest in compliance to the draft because it is the latest thing. 
>From what I've seen, there is little, if anything, that is better about it 
(unless word-count is a plus). I'd much prefer that the draft meet our needs 
instead of developers blindly going along. If fact, the W3C really needs to 
get together with the development community concerning this instead of just 
asking if a couple changes need to be made now that it's basically done. I'm 
completely in favor of web accessibility, but for every rule I adopt and 
implement, I do it because it makes sense, not because that's what the sign 
says.

I don't usually cite the guidelines in my accessibility statements, though 
on one site I did write: " This site was written in the spirit of W3C WAI, 
following the W3C WCAG guidelines as defined by the World Wide Web 
Consortium." But rather, in my statements, I go into more detail that will 
mean something to the user, such as explaining what was done and why. 
Features, barriers removed, etc. The other stuff doesn't mean much to users 
(unless it's some legal department itch that needs scratching). I don't 
think most users care what guideline I follow, but they do get some value 
from telling them I have a style changer, or explaining to them how their 
browser works.

For my own sanity, I have to take a more practical approach.

Sharing Mike's concern, I hope this response doesn't spark a wildfire. I 
wouldn't fault anyone for following the WCAG 2.0 implicitly. But I sure hope 
it makes their sites more accessible in the end. If it does, I will probably 
adopt the real improvements I see, whatever they may be, and continue to 
filter out the rest of the noise.

Disclaimer: IMO

Sincerely,
Mike Cherim








**
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] Adding css files from JavaScript?

[Janette Girod]

Sorry, I should have given a more complete reply. 
"Perfectly" doesn't really help!

This is the code I tested:
var new_ss = document.createElement('link');
new_ss.setAttribute('href','extra.css');
new_ss.setAttribute('rel','stylesheet');
document.getElementsByTagName('head')[0].appendChild(new_ss);

It works in Win/IE5+, FF 1.5, Opera 9, Netscape 7+,
Safari, & Camino.

It doesn't work in Mac/IE. 


--- Jan Brasna <[EMAIL PROTECTED]> wrote:

> > Can you not just create a new LINK element and
> give it an HREF, then
> > append it to the HEAD?
> 
> Doesn't work in Safari. For Safari you have to
> simply output the whole 
> '' strings to the document.
> 
> -- 
> Jan Brasna :: www.alphanumeric.cz |
> www.janbrasna.com | www.wdnews.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
>
**
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


**
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] Adding css files from JavaScript?

[Jan Brasna]

append it to the HEAD?


Doesn't work in Safari.


Sorry, this is true for appending JS files via DOM (don't know the 
situation with CSS files) ... my bad.


The next time I'll read the whole question properly ;)

--
Jan Brasna :: www.alphanumeric.cz | www.janbrasna.com | www.wdnews.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
**

RE: [WSG] Preparing accessibility policies/standards in readiness for WCAG2.0

[michael.brockington]

If no-one else is going to answer, then (at the risk of 
starting a war) I will: 
At this point in time I have no intention of even 
acknowledging the existence of WCAG 2
I don't understand the rationale behind the main changes, 
and don't think that anyone in WCAG understands how their guidelines are 
currently used. Some people will inevitably jump on this new 'standard' - once 
they have found their feet I will re-evaluate, but for now I see less that is 
wrong with version 1.0 than with version 2
 
Mike

  
  
  From: listdad@webstandardsgroup.org 
  [mailto:[EMAIL PROTECTED] On Behalf Of Scott 
  BryantSent: Wednesday, July 19, 2006 1:05 AMTo: 
  wsg@webstandardsgroup.orgSubject: [WSG] Preparing accessibility 
  policies/standards in readiness for WCAG2.0
  
  Hi all,
  I'm interested in the experiences of other 
  universities/organisations preparing internal accessibility policies or 
  standards in readiness for WCAG2.0.
  
  If you were to update your policies/standards, what 
  would be the major changes?
  
  What sense have you made out of the guidelines and 
  how would you interpret them for you developer base? What resources would you 
  provide?
  
  (I know all of this is a little premature given 
  WCAG2.0 is still in draft but if you were to start updating your existing 
  policies/standards, what would your priorities be?
  
  
  Scott

**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] Adding css files from JavaScript?

[Jan Brasna]

Can you not just create a new LINK element and give it an HREF, then
append it to the HEAD?


Doesn't work in Safari. For Safari you have to simply output the whole 
'' strings to the document.


--
Jan Brasna :: www.alphanumeric.cz | www.janbrasna.com | www.wdnews.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
**

Re: [WSG] are transitional doctypes quickmode

[Gunlaug Sørtun]

Tee G.Peng wrote:

I always thought transitional doctypes are quirkmode but today I  was
 told it's not, the quirkmode is when a page has no doctype declared.


All 'doctype vs. modes' are listed here:


Georg
--
http://www.gunlaug.no


**
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] Adding css files from JavaScript?

[Seb Frost]

I've got a feeling this won't work - not based on anything concrete,
but I'm sure I've tried it before (quite a while ago though) and had
no luck.  Let me know if it works out for you Janette!

On 19/07/06, Matthew Pennell <[EMAIL PROTECTED]> wrote:

On 7/19/06, Matthew Pennell <[EMAIL PROTECTED]> wrote:
> var new_ss = document.createElement('link');
> new_ss.setAttribute('href','css/extra.css');
> document.getElementsByTagName('head')[0].appendChild(new_ss);

...and a rel="stylesheet" attribute as well, of course...


**
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] Adding css files from JavaScript?

[Janette Girod]

Worked perfectly.  Thank you Matthew!

--- Matthew Pennell <[EMAIL PROTECTED]> wrote:

> On 7/19/06, Matthew Pennell
> <[EMAIL PROTECTED]> wrote:
> > var new_ss = document.createElement('link');
> > new_ss.setAttribute('href','css/extra.css');
> >
>
document.getElementsByTagName('head')[0].appendChild(new_ss);
> 
> ...and a rel="stylesheet" attribute as well, of
> course...
> 
> 
>
**
> The discussion list for 
> http://webstandardsgroup.org/
> 
>  See
> http://webstandardsgroup.org/mail/guidelines.cfm
>  for some hints on posting to the list & getting
> help
>
**
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


**
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] Anti-aliassing a font

[Hrvoje Markovic]

not at the moment.
"Anti-aliasing might have been added to CSS 3 (I haven't checked), but most 
browser vendors will probably be concentrating on finishing support for CSS 
2 (or 2.1)"



From: "Bas V" <[EMAIL PROTECTED]>
Reply-To: wsg@webstandardsgroup.org
To: wsg@webstandardsgroup.org
Subject: [WSG] Anti-aliassing a font
Date: Tue, 20 Jun 2006 19:30:07 +0800

Is it possible to anti alias a font using styles?




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

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



_
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/




**
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] Adding css files from JavaScript?

[Matthew Pennell]

On 7/19/06, Janette Girod <[EMAIL PROTECTED]> wrote:

Hi guys,

Is there a way add style sheets to a document from
within a JavaScript file?


Can you not just create a new LINK element and give it an HREF, then
append it to the HEAD?

var new_ss = document.createElement('link');
new_ss.setAttribute('href','css/extra.css');
document.getElementsByTagName('head')[0].appendChild(new_ss);

?


**
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] Adding css files from JavaScript?

[Matthew Pennell]

On 7/19/06, Matthew Pennell <[EMAIL PROTECTED]> wrote:

var new_ss = document.createElement('link');
new_ss.setAttribute('href','css/extra.css');
document.getElementsByTagName('head')[0].appendChild(new_ss);


...and a rel="stylesheet" attribute as well, of course...


**
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] Need help with vertical "accordian" menu

[Nello Lucchesi]

You may want to look a the JavaScript in the Suckerfish dropdown 
menus for ideas on getting the  hover pseudo class to work on IE:


  http://www.htmldog.com/articles/suckerfish/dropdowns/

You may also like to review these "canned" menus for ideas:

  http://css.maxdesign.com.au/index.htm

Hope that gets you started.

  - nello



On 7/18/06, morten fjellman < 
[EMAIL PROTECTED] > wrote:


Thank you :)
That got me started. I do think the main problem I face is how to 
make the menu expand. I was thinking maybe using display hidden to 
hide the links when not active. Am I on the right track here, or is 
JavaScript the only way to make this work?


regards

Fjellman




**
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] Adding css files from JavaScript?

[Janette Girod]

Hi guys, 

Is there a way add style sheets to a document from
within a JavaScript file?  I know that there is a
document.styleSheet array that I can access, but the
W3C specs say that document.styleSheet[i].href is a
read-only property, so I can't add an existing
stylesheet into this array.  Is there another way to
reach the same end?  

I realize this may sound like a bizarre question, so
here's the background:
A client of ours would like us to build a measures
conversion tool, for its partners to add as a feature
on their sites.  This tool would sit on pages with all
kinds of doctypes and sites on all kinds of server
platforms.  (A bit like AdSense.)

Obviously, the easier we make it to integrate our tool
into a partner site, the more likely the partner sites
are to take it up.  So, asking them to put one
javascript file in their page where they want the tool
to display is far better than asking them to add a
javascript file, a CSS file, and a choice of either an
html or an xhtml snippet, depending on what their page
is built with.

Creating the elements in the DOM also gets around the
problem of whether to use HTML or XHTML, since we are
creating the elements themselves, rather than writing
end brackets.  (For example, we are creating an image
element, not choosing whether to give it an "/>"
ending.) 

However, after being trained to meticulously separate
my content, presentation, and behavior, the prospect
of writing a whole bunch of "element.style.property =
..." rules makes me cringe.  One way of limiting the
damage would be to import a style sheet via the
JavaScript, so that I can set class names rather than
writing CSS rules in the JavaScript. I realize that
setting class names has a built-in risk with regards
to naming - what if I choose the same class name that
a site is using elsewhere?  I would need  to use a
bizarre combination for a prefix or suffix on the
class names if I want them to be unique but still
meaningful.

(I should mention that the Javascript and any
associated style sheets and images will be hosted
externally, on Amazon S3.  So even if we import styles
and images, the client will still only need to add one
line to their mark-up.)

This may all sound a bit obscure, but with the
increasing popularity of widgets, commonly
distributing widget-type tools on other people's web
pages may not be that far off (think flickr badges and
integrated google maps).  So figuring out best
practices early on seems like a good idea.

Many thanks for any suggestions, 
Janette

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


**
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] quirks mode and font size inheritance

[Felix Miata]

On 06/07/19 03:04 (GMT-0400) Tee G.Peng apparently typed:

> I came up with examples to prove my point.
> http://lotusseedsdesign.com/sapotek/group-px.gif
> and their respective pages:
> http://lotusseedsdesign.com/sapotek/xhtml-strict-dtd-px.html
> http://lotusseedsdesign.com/sapotek/xhtml-tran-dtd-px.html
> http://lotusseedsdesign.com/sapotek/html-strict-dtd-px.html
> http://lotusseedsdesign.com/sapotek/html-trans-dtd-px.html
> http://lotusseedsdesign.com/sapotek/nodtd-px.html

> In the original page, font-size only declared in a and body elements.
> In my five examples, the nodtd-px page, the headings and p tag  
> content, the font size appears bigger than those that have doctype  
> declared.

> Hence I wrote:
> As you can see clearly, the a tag linklist makes no different whether
> it has doctype declared or not, and it makes no different with strict
> or transitional (quirks mode) doctype or not, be it html or xhtml.

> With pages that have doctype declared, the font size was not declared
> in all headings and p, therefore they inherited from the body 12px
> font-size. The one with no doctype declared, the headings and p font
> size appears bigger, this I believe is that browser default takes
> precedence when it doesn't need to listen to doctype (or rather, no
> doctype tells her what to do). Why it does so?

No inheritance into tables in quirks mode:
http://developer.mozilla.org/en/docs/Fixing_Table_Inheritance_in_Quirks_Mode
-- 
"If you confess with your mouth, 'Jesus is Lord', and believe in
your heart that God raised him from the dead, you will be saved."
Romans 3:23 NIV

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://mrmazda.no-ip.com/


**
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] quirks mode and font size inheritance

[Tee G . Peng]

Hi, regarding my previous message, are transitional doctypes quirks  
mode - lo and behold! I finally got it collect, I would like to get  
enlightenment from you knowledgeable ones about quirks mode and font  
size inheritance.


The quest came from a discussion from a CSS study group. Someone  
posted a question why the font size in  particular section (link  
list) in her page appears much smaller than 12px.


In her CSS, she declared:

body {font-size: 12px}
a {font-size: 12px}

I answered it was because font-size is inherited and that "a" element  
inherited the 12 pixel font size from body, and suggested


body {font-size: 100.1% }

be used, I also suggested to change the pixel unit to em.

Someone else replied that the font size in link list appear smaller  
was because the page has no doctype, hence through browsers throw the  
page to quirks mode.


I disagreed - declaring doctype is important however on this  
particular case, it's the inheritance of font-size that causes the  
problem. Along the way, I said transitional doctype also throw the  
page to quirks mode - and I truly believed what I said when I said it.


I came up with examples to prove my point.
http://lotusseedsdesign.com/sapotek/group-px.gif
and their respective pages:
http://lotusseedsdesign.com/sapotek/xhtml-strict-dtd-px.html
http://lotusseedsdesign.com/sapotek/xhtml-tran-dtd-px.html
http://lotusseedsdesign.com/sapotek/html-strict-dtd-px.html
http://lotusseedsdesign.com/sapotek/html-trans-dtd-px.html
http://lotusseedsdesign.com/sapotek/nodtd-px.html

In the original page, font-size only declared in a and body elements.
In my five examples, the nodtd-px page, the headings and p tag  
content, the font size appears bigger than those that have doctype  
declared.


Hence I wrote:
As you can see clearly, the a tag linklist makes no different whether
it has doctype declared or not, and it makes no different with strict
or transitional (quirks mode) doctype or not, be it html or xhtml.

With pages that have doctype declared, the font size was not declared
in all headings and p, therefore they inherited from the body 12px
font-size. The one with no doctype declared, the headings and p font
size appears bigger, this I believe is that browser default takes
precedence when it doesn't need to listen to doctype (or rather, no
doctype tells her what to do). Why it does so? I have no knowledge to
explain it, but my assumption is such:
It takes 'two' in order for inheritance to work, and with criteria -
that is why you see the link list' font size appear the same in
different doctype because it's being declared to 12px in css, and it
inherited from the 12px font size from the body that is also declared
in css.

So, it seems the way it works is such:

When there are two elements declared font size in CSS and the two
elements have inheritance relationship, even without doctype, browser
smartly followed - and this maybe the criteria (or condition) browser
has.

So when criteria is not meet, without doctype, browser doesn't follow
and doesn' take the parent font size into account.

However, it seems that when there is doctype declared, criteria
partially meets, it takes parent font size as higher specificity , and
make the headings and p inherit to their parent font size, which is
the body.



Now I get confused, have little faith to what I thought was correct,  
and here I am, seeking for the correct answer from you who have more  
knowledge and experience in this area.


p/s. I know my English is difficult to understand. Please read it  
once, read it twice, read it thrice and read it few more time until  
you understand what I am trying to say :)


tee




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

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