RE: [WSG] Flexible Font sizes in tables in ie

2005-10-04 Thread Kara O'Halloran - Eduka

Thanks everyone for your help, I have a few resources to check out now
and some things to try :) 

Much appreciated, Kara
**
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] Flexible Font sizes in tables in ie

2005-10-04 Thread Kara O'Halloran - Eduka
>>You'll have to set font-size on td, for IE/win.

Either way I still have the problem of the table cell text either appearing too 
large in ie, or too small in ff.

Without resorting to setting text size in pixels in my table, I can't find any 
other way to prevent this from happening, I thought perhaps there might be a 
hack out there that will pass 0.8em to ie, but not to firefox?

Thanks :) 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gunlaug Sørtun
Sent: Tuesday, 4 October 2005 5:25 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Flexible Font sizes in tables in ie

Kara O'Halloran - Eduka wrote:

> I think if I set a base of 1em in the body it would solve my problems, 
> but then I have to apply font size 75% to make everything the size I 
> want it, and that would cause much the same problem as it cascades 
> down and potentially end up with really mini fonts throughout the 
> site...
> 
> Now, is there a way that I can cater for both browsers here?

You should at least start by setting the base in '%', to avoid a buggy IE/win. 
The rest can be '%' or 'em'.

The exact value is your choice, but browsers have different 'tip-over'
points for recalculating '%' and 'em' to 'px' which they have to make all 
font-sizes fit into. Experiment a bit to hit the middle ground down the cascade.

You'll have to set font-size on td, for IE/win.

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
**

**
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] Flexible Font sizes in tables in ie

2005-10-04 Thread Kara O'Halloran - Eduka
 hi guys,

Another possibly silly question but I've done quite a bit of searching
on this now and found nothing.

I'm setting my font size at 0.8em in my body class. In firefox this
works fine across the site, but in ie, the text inside my table cells
appears larger.

I've tried setting a font size to td but then it appears smaller in ff
(as it should).

I think if I set a base of 1em in the body it would solve my problems,
but then I have to apply font size 75% to make everything the size I
want it, and that would cause much the same problem as it cascades down
and potentially end up with really mini fonts throughout the site...

Now, is there a way that I can cater for both browsers here?
**
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] Width defaulting to 100%?

2005-10-03 Thread Kara O'Halloran - Eduka

You're a legend - thanks :) 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tatham Oddie (Fuel
Advance)
Sent: Tuesday, 4 October 2005 1:00 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] Width defaulting to 100%?

Kara,

Block elements (like ) always expand to the full width by default.

By the sounds of it you're after an inline element, so either:

A) use a  instead

or

B) set display:inline; on the DIV

You might find it helpful to read up on the difference between block and
inline elements.



Thanks,

Tatham Oddie
Fuel Advance - Ignite Your Idea
www.fueladvance.com


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Kara O'Halloran - Eduka
Sent: Tuesday, 4 October 2005 2:39 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] Width defaulting to 100%?

Hi guys,

I have 2 divs inside a container.

1: a relatively positioned div to contain and position an image
2: another div, absolute position, to contain a submenu. 

Image on left, menu on right.

For some reason, both divs are expanding horizontally to take up all the
available space, even when the content inside them is only 20 pixels
wide. I'm not specifying any widths because the content is dynamic so I
have no way of knowing what the width will be.

The only width I have specified is the container width of 60em. 

Why are they doing this? Shouldn't they only expand horizontally to make
room for whatever is contained in them - in this case only a few words?

Any help would be appreciated. :)
K

(ps this happens in both ff and ie.)
**
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
**

**
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] Width defaulting to 100%?

2005-10-03 Thread Kara O'Halloran - Eduka
Hi guys,

I have 2 divs inside a container.

1: a relatively positioned div to contain and position an image
2: another div, absolute position, to contain a submenu. 

Image on left, menu on right.

For some reason, both divs are expanding horizontally to take up all the
available space, even when the content inside them is only 20 pixels
wide. I'm not specifying any widths because the content is dynamic so I
have no way of knowing what the width will be.

The only width I have specified is the container width of 60em. 

Why are they doing this? Shouldn't they only expand horizontally to make
room for whatever is contained in them - in this case only a few words?

Any help would be appreciated. :)
K

(ps this happens in both ff and ie.)
**
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] WE05

2005-10-03 Thread Kara O'Halloran - Eduka
I noted that too, and I think that the issue may be in your
interpretation of "header" (well it was what confused me anyway until I
thought about it).

Using a div with class=header is fine when the div is actually a "box"
that contains  for example your logo/menu etc. Other people call it the
"masthead".

I *think* Tantek was referring to the use of "div class=header" when the
only contents of the div are text, and should therefore be using h1
instead.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alan Trick
Sent: Monday, 3 October 2005 8:28 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] WE05

There's nothing in the HTML specs that would indicate that the contents
of a header are limited to text. AFAIK you can put any inline level
content in a header. In my opinion using an image with alt text is much
better than using a background image with invisible text. In makes more
sense semantically (because the images *is* the content) and also
practically because trying to fake it can cause all sorts of
accessibility issues.

You should try to make sure you actually are using a header as a header.
This is quite a mess because many web pages don't really fit the simple
h1 > h2 > etc hierarchy. It works well for academic papers, but wenever
I go to to build a website I always find myself confused as to what
should be the . Many web pages that I make don't have one because
the user already knows what the pages is about and adding another title
just takes up valueable real estate.

Katrina wrote:
> Gday,
> 
> I was lucky enough to be able to attend WE05, and I was listening to 
> something Tantek Celik said and I've been mulling it over for a few 
> days, and I just thought I'd ask a group who'd know.
> 
> Context: I'm a uni student, so I don't know much.
> 
> Going back to Tantek Celik, he was referring to meaningful markup and 
> he said
> 
> "Who has ever seen a div with a class of header? Why not use a header
> (eg.) element?"
> 
> I may not have understood that. I may have misheard that. I'm sorry if

> I did.
> 
> Aren't the header tags reserved for text? Is it acceptable form to 
> place non-textual elements only inside of header tags? Eg.  src="image.jpg" alt="An image"> ?
> 
> Kat

**
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
**



[WSG] abs pos in safari & backgrounds

2005-09-21 Thread Kara O'Halloran - Eduka
Re using ems in your layout elements too (below) - Oh you legend - I was
wondering why my layout spat it when I increased the font size!!

On another note - I have a positioning problem in safari.  I am using
absolute positioning and I have a style that swaps my background image
on rollover. In safari the backgrounds are WAY out of whack.

Is there an obvious reason for this? I know very little about safari. 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Webmaster
Sent: Thursday, 22 September 2005 7:45 AM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] controlling font size in form text box

Janelle Clemens wrote:

> using em was way to inconsistent cross browser.

Janelle, another thing to consider when using ems and % for your
font-size is to also apply these units to your layout (header, columns
etc.). This way everything will flow just beautifully when resized.

You need to get your designer to think outside the box and not be so
precious. I've settled many an argument simply by throwing quotes from
the Web standards bible at people. At the end of the day, when it comes
to making a site accessible, they won't have a leg to stand on...
[cringe]

**
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] RE: Hot Topic: HTML design

2005-08-16 Thread Kara O'Halloran - Eduka
As far as sitemap pages go I believe there is a (beta) standard that
Google set in place for the sitemap page that gives suggested tags to
use etc.

I'm not a technical person so forgive me if this holds no relevance!

https://www.google.com/webmasters/sitemaps/login 

Seems like a step in the right direction...

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Patrick H. Lauke
Sent: Tuesday, 16 August 2005 3:18 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] RE: Hot Topic: HTML design

Paul Bennett wrote:

> As soon as there is consistent browser support for client side xslt,
we'll be able to deliver pure xml to the client and have it apply style
and layout as the / browser chooses. True accessibility and
universality.

The problem, though, would be that everybody will invent their own XML
based markup to suit their needs, which will make it impossible for
search engines to index properly (they wouldn't even know what is a
link, a heading, etc) and assistive technology such as screen readers
would not be able to provide any sophisticated methods of navigation. 
Web developers will need to agree to a certain extent to a common
standard, otherwise we'll have a very fragmented set of "my very own
markup format" which would be indistinguishable from plain, unstructured
text to any programmatic tools (unless we have a method to unequivocally
specify the semantics of any of our own made up formats...something like
a DTD or Schema, but with added options to define what is a link,
heading, etc, and their relative importance and relationship with each
other).

Hmm...hope that made some kind of sense...it's too early in the morning
for this sort of heavy talk ;)

--
Patrick H. Lauke
__
re*dux (adj.): brought back; returned. used postpositively [latin : re-,
re- + dux, leader; see duke.] www.splintered.co.uk |
www.photographia.co.uk http://redux.deviantart.com
__
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__
**
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
**