Re: [WSG] hiding legend tag

[Philippe Wittenbergh]

On 11 Nov 2005, at 7:47 am, Alexander Jerabek wrote:


So I came up with this:

legend{margin:-1em; font-size:0px;}

In Mozilla the 0px makes the text invisible, but only miniscule in IE 
so

I used margin:-1em; is to push it under the drop down menu in the form.


My question is: does anybody know if this will have adverse affects on
accessibility or if there are any other weird problems with using this
technique?


In my copy of Firefox, your legend will be 12px in size (minimum 
font-size set, us older people really do like that little preference in 
the browser ;-))


visibilty:hidden or text-indent:-1px !important are some options.

Philippe
---
Philippe Wittenbergh


**
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] Divs over Flash in Safari

[Al Sparber]

From: "Tom Livingston" <[EMAIL PROTECTED]>



Hi listers,

Just thought I'd check with you guys on this. I've googled it for a 
few hours...


Has anyone successfully implemented a drop down menu (or similar) 
that drops down *over* a Flash element and had it work in Safari 
(2.0.2)?


Hi Tom,

I wouldn't compromise or risk problems by using markup hacks. This is 
a known bug in Safari's Flash Player implementation and Macromedia has 
filed a bug report with Apple.


Al Sparber
PVII
http://www.projectseven.com

"Designing with CSS is sometimes like barreling down a crumbling 
mountain road at 90 miles per hour secure in the knowledge that 
repairs are scheduled for next Tuesday".



**
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] Divs over Flash in Safari

[Terry Bunter]

I have successfully been able to get dropdowns to work in Safari by using the 
Multi-level Suckerfish Dropdowns from
http://www.htmldog.com/articles/suckerfish/dropdowns/

For some reason if you create the dropdown and then add an extra blank level to 
each item it tricks safari into displaying properly.

Eg


Top Level

Item
 

Item
 

Item
 




You can see this in action at 
http://www.investaustralia.gov.au/index.cfm?menuid=3D5D8296-EB77-C709-36153CFE42024159

TB

**
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] Divs over Flash in Safari

[Adam Burmister \(DSL AK\)]

Air New Zealand uses a system where the navigation renders an iframe
behind a drop down menu, this blocks the flash as the frame takes
precedence in the rendering pipeline.

Can't quite remember where we got it from, but check it out @
http://www.airnz.co.nz
http://www.airnz.co.nz/NR/AirNZ/includes/scripts/nav.js

- A


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zulema
Sent: Friday, 11 November 2005 4:02 p.m.
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Divs over Flash in Safari

I've had success with adding this to the html code:
 

and this to the embed tag:
 wmode="transparent"

It has limitations tho:
http://www.kirupa.com/developer/mx/transparency.htm

hope that helps or at least sheds some light?

ciao,
Zulema

--

Z u l e m a  O r t i z
w e b  d e s i g n e r
email : [EMAIL PROTECTED]
website : http://zoblue.com/
weblog : http://blog.zoblue.com/
browser : http://getfirefox.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
**

**
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] Divs over Flash in Safari

[Zulema]

I've had success with adding this to the html code:
 


and this to the embed tag:
wmode="transparent"

It has limitations tho:
http://www.kirupa.com/developer/mx/transparency.htm

hope that helps or at least sheds some light?

ciao,
Zulema

--

Z u l e m a  O r t i z
w e b  d e s i g n e r
email : [EMAIL PROTECTED]
website : http://zoblue.com/
weblog : http://blog.zoblue.com/
browser : http://getfirefox.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] Naked metadata - RDF in HTML

[Andy Kirkwood|Motive]

Title: Re: [WSG] Naked metadata - RDF in
HTML


Hi Terrence,

It feels like we're talking at cross-purposes?

I'm approaching the subject with the idea
that metadata is
important in order for people to find
(related) information at some later
time.

Interesting and valid point, unfortunately not the point being
discussed.

I think the issue being addressed by
Jonathon was not how-to in a WYSIWYG
editor, rather that metadata is not front-of-mind when editing an
existing
resource.'

I equate front-of-mindness with visibility, hence reference to an
editing interface that will *show* the metadata records--a wysiwyg
editor. Jonathan's focus was on the author and not the reader. From
the original post:

** The problem **
People updating Web pages often doesn't update the
metadata in the header.

The method presents an elegant solution
for metadata that is important for
an external audience/end users (who wrote it, when, what's it about,
what
else is there, where am I with regard to related documents), as
opposed to
the internal management of a collection (similar but slightly
or
significantly different to the
above).

I was not advocating a separate metadata collection, but rather
that metadata within a single document may be more elegantly
edited/updated if all contained within the  of the
document, than when the records are mixed-in with the content.

The leading WSIWYG editor can be
extended, with much gnashing of the teeth
and swearing, to provide this type of functionality. In fact, that is
a
major selling point.

Moving away from specifics of which tool, the issue is still
educating authors on a practice that is peripheral to writing the
content. To create and maintain metadata requires the author to either
care about metadata it also helps if they *see* the metadata when
editing/updating the content.

The RDF approach requires the author to have access either to the
source code or the means by which they can assign classes to
s. Wysiwyg editors have *not been created to include a
work flow that is optimised for adding metadata records to content in
this manner*.

I think the opposite. Sure, the finer
points of the machine readable part
of the record is invisible,

If the incorrect class value is assigned, the meaning of the
record changes. Say for example I accidentally markup the author's
name as the title:
Andy
Kirkwood

At a visual level (i.e. without viewing the name value) it is not
possible to spot the error. It would also be easy to accidentally add
content to a record when editing, e.g.

Andy Kirkwood will be out
of the office until next week

Authors have the opportunity to
administer the metadata for their own
content in a simple, relevant way. Again, the popular WSYIWYG editor
can
be extended to help less-savvy
people.

As far as I'm aware, the cutomisation available does not replace
the need for the author to care about metadata :).

That the RDF method is simple is definitely debatable. How is
adding s to content more or less relevant to an author
than adding records to the ?

>The example provided,
<
>
http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml >,
> re-purposes content as metadata. If the content is edited, the
record
could (unintentionally) be deleted, or the content rewritten to
> included the records required

I'm missing something here... this reads like an argument in favor of
both
sides: you can delete the metadata or add it?

At a visual level, that the word 'Anna' is a metadata record for
the first name of the author would not be apparent. I might re-edit
the copy from "Anna spoke to Susan on the phone" to
"She spoke to Susan on the phone". By removing 'Anna', I've
remove a metadata record from the document. To maintain the metadata
record I would then need add 'Anna' to somewhere else.

Keeping track of which records have and haven't been entered
would be a nightmare. It's enough as an author to keep an eye on
structure, grammar, spelling, etc.

> -if metadata records are split
between the  and  of a
document, review would likely require a greater degree of
> concentration/quality assurance and/or additional supporting
> technologies (such as a metadata record 'viewer' that would
reveal both
conventional and class-based records)
> -etc.
>
> A custom-built CMS,  as a companion to a well-supported
publishing
process, is still your best bet.

For enterprise sized endevours with a
huge budget or significant inhouse
savvy, sure.

Savvy enough to care about metadata, not savvy enough to edit it
when all the records are in the , but savvy enough to pick
through the content and assign classes to spans to approximate
metadata records AND keep track of which records have and haven't been
completed?

An author that is comfortable with adding  elements
with class values corresponding to the DC standard is not the
'problem'. It's the person who forgets to add metadata records when
authoring content. Embedding the records within the content does not
make it any more likely that the r

Re: [WSG] hiding legend tag

[*.gtf]

Dnia piątek, 11 listopada 2005 00:43, Adam Burmister (DSL AK) napisał:
> I think you'll find that you can successfully hide the legend off canvas
> with
>
> .hide {
>   position: absolute;
>   left: -999px;
>   width: 9px;
> }
>
> Regards,
> - A

imo :

.hide {
display:none;
 }

is much better

-- 
*.gtf
**
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] hiding legend tag

[Adam Burmister \(DSL AK\)]

Opps, cancel that last reply...

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexander Jerabek
Sent: Friday, 11 November 2005 11:48 a.m.
To: wsg@webstandardsgroup.org
Subject: [WSG] hiding legend tag

Hi everybody,

I'm working on an accessible form the has all fieldset, legend, label
elements properly included. 
But I'd also like the form to be styled in a minimalist fashion with the
option of toggling the labels on and off.

I can hide the label elements using the  'off stage' technique
(position:absolute; left: -100em; width: 100em;), but the legend element
cannot be repositioned or easily manipulated, and I don't want to use
display:none; or visibility:hidden;. 

So I came up with this:

legend{margin:-1em; font-size:0px;}

In Mozilla the 0px makes the text invisible, but only miniscule in IE so
I used margin:-1em; is to push it under the drop down menu in the form.


My question is: does anybody know if this will have adverse affects on
accessibility or if there are any other weird problems with using this
technique?


You can see the form here:
http://132.206.197.7/labels/


css is here:
http://132.206.197.7/labels/labelsoff.css
and here:
http://132.206.197.7/labels/labels.css

Thanks for any help or insight.

Best,
Sacha
**
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] hiding legend tag

[Adam Burmister \(DSL AK\)]

I think you'll find that you can successfully hide the legend off canvas
with

.hide {
position: absolute;
left: -999px;
width: 9px;
}

Regards,
- A

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexander Jerabek
Sent: Friday, 11 November 2005 11:48 a.m.
To: wsg@webstandardsgroup.org
Subject: [WSG] hiding legend tag

Hi everybody,

I'm working on an accessible form the has all fieldset, legend, label
elements properly included. 
But I'd also like the form to be styled in a minimalist fashion with the
option of toggling the labels on and off.

I can hide the label elements using the  'off stage' technique
(position:absolute; left: -100em; width: 100em;), but the legend element
cannot be repositioned or easily manipulated, and I don't want to use
display:none; or visibility:hidden;. 

So I came up with this:

legend{margin:-1em; font-size:0px;}

In Mozilla the 0px makes the text invisible, but only miniscule in IE so
I used margin:-1em; is to push it under the drop down menu in the form.


My question is: does anybody know if this will have adverse affects on
accessibility or if there are any other weird problems with using this
technique?


You can see the form here:
http://132.206.197.7/labels/


css is here:
http://132.206.197.7/labels/labelsoff.css
and here:
http://132.206.197.7/labels/labels.css

Thanks for any help or insight.

Best,
Sacha
**
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] CSS filesize and selector names

[Lloyd]

It is a double edged sword. If you split your CSS sheet into multiple
sheets for each page then you will only be making the user download
what they need, but if they visit all the pages they will probably
need to download more in total. That 10k will add about 2 seconds to
the initial load of your page on 56k though...

The best bet is to make a main style sheet with a specialised style
sheet for each page.

Lloyd

On 11/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hey folks!
>
> I'm working on a project where nearly every web page differs from each
> other in layout. Due to the nature of the project, it is a blend of admin
> and report system, with a lot of configurations and various styled
> reports. This has made my CSS file nearly 10kb large and consists of
> nearly 600 rows of CSS code. Is this a problem in general? Are there any
> issues regarding large CSS files? Any recomendations for CSS file sizes
> both in KB and rows.
>
> This is my first larger project, so maybe it is just me that's not used
> to, what I consider extremly large CSS files.
>
> My second question is about CSS selector naming and problems regarding
> various naming styles. Are there any problems with the naming styles below
> or is this just something I've got totally wrong? I've heard that you
> should avoid underscore and mixing small (lower case) and large letters
> (upper case).
>
> #btn_save
> .row_color1
>
> #btnSave
> #salesTable
>
> #btnsave (always work, but is just so hard to read)
>
> Thanks in advance!
>
> Best regards
> Jorgen Nilsson
> **
> 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] hiding legend tag

[Alexander Jerabek]

Hi everybody,

I'm working on an accessible form the has all fieldset, legend, label
elements properly included. 
But I'd also like the form to be styled in a minimalist fashion with the
option of toggling the labels on and off.

I can hide the label elements using the  'off stage' technique
(position:absolute; left: -100em; width: 100em;), but the legend element
cannot be repositioned or easily manipulated, and I don't want to use
display:none; or visibility:hidden;. 

So I came up with this:

legend{margin:-1em; font-size:0px;}

In Mozilla the 0px makes the text invisible, but only miniscule in IE so
I used margin:-1em; is to push it under the drop down menu in the form.


My question is: does anybody know if this will have adverse affects on
accessibility or if there are any other weird problems with using this
technique?


You can see the form here:
http://132.206.197.7/labels/


css is here:
http://132.206.197.7/labels/labelsoff.css
and here:
http://132.206.197.7/labels/labels.css

Thanks for any help or insight.

Best,
Sacha
**
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] Naked metadata - RDF in HTML

[Terrence Wood]

Andy Kirkwood|Motive said:
> An interesting application of the technology, although I'm not sure that
is addresses how to make it *easier* for administrators to
> maintain metadata records.

and

> (Assuming the ideal solution would be a wysiwyg editing environment for
non-technical content authors.)

Andy, I see value in all the points you raise -  I'd like to offer some
counterpoint. I'm approaching the subject with the idea that metadata is
important in order for people to find (related) information at some later
time.

I think the issue being addressed by Jonathon was not how-to in a WYSIWYG
editor, rather that metadata is not front-of-mind when editing an existing
resource.

The method presents an elegant solution for metadata that is important for
an external audience/end users (who wrote it, when, what's it about, what
else is there, where am I with regard to related documents), as opposed to
the internal management of a collection (similar but slightly or
significantly different to the above).

> -adding DC class values to  elements is not a mark-up behaviour
likely to be supported by wysiwyg editors

The leading WSIWYG editor can be extended, with much gnashing of the teeth
and swearing, to provide this type of functionality. In fact, that is a
major selling point.

> -administrators will still not entirely 'see' the metadata they've
added, as it is the combination of the name and content values that
creates a meaningful record, and this would only be visible at a code
level

I think the opposite. Sure, the finer points of the machine readable part
of the record is invisible, but the metadata itself become recognisable
patterns that are contained within the document, *are* visible, and not
abstracted to another level. How many people do you know who save adequate
(any?) metadata with their word documents? Out of sight out of mind.

Authors have the opportunity to administer the metadata for their own
content in a simple, relevant way. Again, the popular WSYIWYG editor can
be extended to help less-savvy people.

> -the benefit of metadata is that it can be used to classify content to a
significant degree of detail *without encroaching upon the
> visible page content itself*.

Agreed. Though see my point earlier re: external and internal metadata.

>The example provided, <
> http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml >,
> re-purposes content as metadata. If the content is edited, the record
could (unintentionally) be deleted, or the content rewritten to
> included the records required

I'm missing something here... this reads like an argument in favor of both
sides: you can delete the metadata or add it?

> -if metadata records are split between the  and  of a
document, review would likely require a greater degree of
> concentration/quality assurance and/or additional supporting
> technologies (such as a metadata record 'viewer' that would reveal both
conventional and class-based records)
> -etc.
>
> A custom-built CMS,  as a companion to a well-supported publishing
process, is still your best bet.

For enterprise sized endevours with a huge budget or significant inhouse
savvy, sure.

> The metadata records can be entered
> at the same time as the content, with values selected from a
> controlled vocabulary, etc. and then output either into the  or
 as required. After all, it's more than just the ability to add or
edit metadata records, its also the relevance of the values
> entered to the content, end-use of the records and the intended
> community.

One word: Tags.

Bottom up, ad-hoc, and eventually convergent labelling seems to have a lot
more traction in the wider audience than thesauri, and controlled vocabs.

Problem is the latter are usually not revealed to end users, and thus run
the risk of being pretty meaningless as a tool to help them find stuff. Of
course, the opposite is true in a closed community (i.e where people know
the vocab).

Lastly, naked metadata will be indexed by (public) search engines, used to
determine relevance, and returned in SERP's.


kind regards
Terrence Wood.




**
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] Font resizing

[Jared Smith]

Building this functionality into the page is something I've struggled with 
for some time. There's no way to add text resizing functionality without 
DECREASING accessibility and usability for a large group of other users. 
It does no use to screenreader users. And we expect users to understand 
what a little and big A are supposed to mean? What about the added 
complexity we introduce for those with cognitive disabilities, let alone 
the several extra elements in the tab order of the page. And then we often 
require JavaScript to do this kinda stuff. And most people that MUST have 
enlarged fonts are going to have them anyways.


In my opinion, the only time this is an issue is when you break your page 
by using too small of fonts to begin with. The problems introduced with 
this built-in functionality, in my opinion, outweigh the added benefits. 
Make a solid, accessible design decision and stick with it. I tend to 
prescribe to the "user preferences are for sisses" camp - 
http://www.yourtotalsite.com/archives/usability/user_preferences_are_for_/


Jared Smith
WebAIM.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
**

Re: [WSG] CSS filesize and selector names

[Vishwam Annam]

You could use, these CSS optimizers to reduce the file size a little bit,

http://cdburnerxp.se/cssparse/css_optimiser.php

http://flumpcakes.co.uk/css/optimiser/


Vishwam

Anders Nawroth wrote:


Hejsan!

[EMAIL PROTECTED] skrev:


This has made my CSS file nearly 10kb large and consists of
nearly 600 rows of CSS code. Is this a problem in general?


No.


Are there any
issues regarding large CSS files? Any recomendations for CSS file sizes
both in KB and rows.
 

When hitting 40 KB I think it's time to figure out if the CSS also is 
overly complex. Such CSS also use to be hard to develop and maintain 
across different browsers.


If you strip whitespace and (more important) use server-side 
compression the filesize shrinks a lot. My latest main stylesheet is 
8kb, stripped and compressed it's less than 2kb that's actually sent!!



should avoid underscore and mixing small (lower case) and large letters
 

Mixing lower/uppercase enhances readability, just remember to write it 
the same way everywhere, class names and ID's are case sensitive. I 
tend to prefer hyphens, like #btn-save


Underscores can cause some trouble, better avoid them. (hyphens are OK)

/AndersN
**
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] CSS filesize and selector names

[Anders Nawroth]

Hejsan!

[EMAIL PROTECTED] skrev:


This has made my CSS file nearly 10kb large and consists of
nearly 600 rows of CSS code. Is this a problem in general?


No.


Are there any
issues regarding large CSS files? Any recomendations for CSS file sizes
both in KB and rows.
 

When hitting 40 KB I think it's time to figure out if the CSS also is 
overly complex. Such CSS also use to be hard to develop and maintain 
across different browsers.


If you strip whitespace and (more important) use server-side compression 
the filesize shrinks a lot. My latest main stylesheet is 8kb, stripped 
and compressed it's less than 2kb that's actually sent!!



should avoid underscore and mixing small (lower case) and large letters
 

Mixing lower/uppercase enhances readability, just remember to write it 
the same way everywhere, class names and ID's are case sensitive. I tend 
to prefer hyphens, like #btn-save


Underscores can cause some trouble, better avoid them. (hyphens are OK)

/AndersN
**
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] CSS filesize and selector names

[felix . zapata]

hi, about your first question sometimes I do some css files; one with de
principal layout and the other with the specific of each page.

About the second question, i think that there is no problem about use 
underscore

in the name, but sometimes css validator tell me warnings about that.




Quoting [EMAIL PROTECTED]:


Hey folks!

I'm working on a project where nearly every web page differs from each
other in layout. Due to the nature of the project, it is a blend of admin
and report system, with a lot of configurations and various styled
reports. This has made my CSS file nearly 10kb large and consists of
nearly 600 rows of CSS code. Is this a problem in general? Are there any
issues regarding large CSS files? Any recomendations for CSS file sizes
both in KB and rows.

This is my first larger project, so maybe it is just me that's not used
to, what I consider extremly large CSS files.

My second question is about CSS selector naming and problems regarding
various naming styles. Are there any problems with the naming styles below
or is this just something I've got totally wrong? I've heard that you
should avoid underscore and mixing small (lower case) and large letters
(upper case).

#btn_save
.row_color1

#btnSave
#salesTable

#btnsave (always work, but is just so hard to read)

Thanks in advance!

Best regards
Jorgen Nilsson
**
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] CSS filesize and selector names

[jorgen]

Hey folks!

I'm working on a project where nearly every web page differs from each
other in layout. Due to the nature of the project, it is a blend of admin
and report system, with a lot of configurations and various styled
reports. This has made my CSS file nearly 10kb large and consists of
nearly 600 rows of CSS code. Is this a problem in general? Are there any
issues regarding large CSS files? Any recomendations for CSS file sizes
both in KB and rows.

This is my first larger project, so maybe it is just me that's not used
to, what I consider extremly large CSS files.

My second question is about CSS selector naming and problems regarding
various naming styles. Are there any problems with the naming styles below
or is this just something I've got totally wrong? I've heard that you
should avoid underscore and mixing small (lower case) and large letters
(upper case).

#btn_save
.row_color1

#btnSave
#salesTable

#btnsave (always work, but is just so hard to read)

Thanks in advance!

Best regards
Jorgen Nilsson
**
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] Sydney WSG meeting

[russ - maxdesign]

Tonight's WSG meeting in Sydney was a huge success with 55 people attending.
A huge thanks to Maxine Sherrin and Janet Parker for their presentations -
very informative!

The podcasts and presentation slides will be available soon.

Some Flickr photos:
http://www.flickr.com/photos/russweakley/sets/1336647/

Thanks
Russ

**
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] Divs over Flash in Safari

[kvnmcwebn]

hello,
im not sure if this will help and im not sure if it would validate but read
this

http://www.flashkit.com/board/showthread.php?p=3284355#post3284355

-best
-kvnmcwebn


**
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] Divs over Flash in Safari

[Tom Livingston]

Hi listers,

Just thought I'd check with you guys on this. I've googled it for a  
few hours...


Has anyone successfully implemented a drop down menu (or similar)  
that drops down *over* a Flash element and had it work in Safari  
(2.0.2)?


Everything I have found indicates that it doesn't work, and it's up  
to Apple to fix Safari. Has anyone on the list found different?


We are attempting the following:
absolute positioned divs containing menu lists. Javascript showing  
and hiding of these divs (captive audience). When the divs are over  
any Flash swfs, they are messed up.


TIA

-
Tom Livingston
Senior Multimedia Artist
Media Logic
www.mlinc.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] Character encoding mismatch

[Paul Collins]

That seems to work, thanks heaps 
Rimantas

  - Original Message - 
  From: 
  Rimantas 
  Liubertas 
  To: wsg@webstandardsgroup.org 
  Sent: Thursday, November 10, 2005 12:01 
  PM
  Subject: Re: [WSG] Character encoding 
  mismatch
  2005/11/10, Paul Collins <[EMAIL PROTECTED]>:>> 
  I am getting the following warning when I validate my pages:>> 
  --> Character Encoding mismatch!>> The 
  character encoding specified in the HTTP header (iso-8859-1) is> 
  different from the value in the  element (utf-8). I will use the 
  value> from the HTTP header (iso-8859-1) for this 
  validation.<...>> and so on. I thought this was the correct 
  way to add special characters for> XHTML, but what I am reading now 
  seems to contradict this. This is the part> of standards where I get a 
  bit confused. Does anyone have any advice or know> of some good 
  articles where they explain this in simple terms??The problem is not 
  with your XHTML but with your server. Most likelyyou are running Apache 
  with AddDefaultCharset in configuration. If youhave access to httpd.conf 
  youshould just comment out this directive, or change it to 
  utf-8.Regards,Rimantas**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] Character encoding mismatch

[Paul Collins]

Thanks Susanne, that's a really good 
reference.
 
Cheers,Paul

  - Original Message - 
  From: 
  Susanne Jäger 
  
  To: wsg@webstandardsgroup.org 
  Sent: Thursday, November 10, 2005 12:21 
  PM
  Subject: Re: [WSG] Character encoding 
  mismatch
  Paul Collins wrote, On 10.11.2005 12:44:> I thought 
  this was the correct way to add special> characters for XHTML, but what 
  I am reading now seems to contradict> this. This is the part of 
  standards where I get a bit confused. Does> anyone have any advice or 
  know of some good articles where they explain> this in simple 
  terms??Have a look at the material in W3Cs 
  internationalization-SectionW3C I18N Topic IndexI 
  like the Tutorial: Character sets & encodings in XHTML, HTML and 
  CSSAt 
  least they try to explain the rather complicated stuff for everyone. 
  ;-)HTHSusanne-- http://sujag.de - Webentwicklung und 
  -beratung[EMAIL PROTECTED]Lottumstr. 22, 
  10119 Berlin, Tel: 030 - 440 483 
  47**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] Character encoding mismatch

[Susanne Jäger]

Paul Collins wrote, On 10.11.2005 12:44:

> I thought this was the correct way to add special
> characters for XHTML, but what I am reading now seems to contradict
> this. This is the part of standards where I get a bit confused. Does
> anyone have any advice or know of some good articles where they explain
> this in simple terms??

Have a look at the material in W3Cs internationalization-Section
W3C I18N Topic Index


I like the Tutorial: Character sets & encodings in XHTML, HTML and CSS

At least they try to explain the rather complicated stuff for everyone. ;-)

HTH
Susanne


-- 
http://sujag.de - Webentwicklung und -beratung
[EMAIL PROTECTED]
Lottumstr. 22, 10119 Berlin, Tel: 030 - 440 483 47
**
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] Character encoding mismatch

[Lloyd]

Instead of:


Try:


This will match what your web server is sending, otherwise change your
web server config if you can :-)

Lloyd

On 11/10/05, Paul Collins <[EMAIL PROTECTED]> wrote:
>
> I am getting the following warning when I validate my pages:
>
> --
> Character Encoding mismatch!
>
> The character encoding specified in the HTTP header (iso-8859-1) is
> different from the value in the  element (utf-8). I will use the value
> from the HTTP header (iso-8859-1) for this validation.
>
> --
>
> My header code looks like this, which should validate fine:
>
>  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
> 
>  title
>  
>
> I have just started reading more about character encoding and special
> characters, is my problem that I have used decimal character refereces? For
> example
>
> - as -
>
> ' as '
>
> and so on. I thought this was the correct way to add special characters for
> XHTML, but what I am reading now seems to contradict this. This is the part
> of standards where I get a bit confused. Does anyone have any advice or know
> of some good articles where they explain this in simple terms??
>
> Cheers
**
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] Character encoding mismatch

[Rimantas Liubertas]

2005/11/10, Paul Collins <[EMAIL PROTECTED]>:
>
> I am getting the following warning when I validate my pages:
>
> --
> Character Encoding mismatch!
>
> The character encoding specified in the HTTP header (iso-8859-1) is
> different from the value in the  element (utf-8). I will use the value
> from the HTTP header (iso-8859-1) for this validation.
<...>
> and so on. I thought this was the correct way to add special characters for
> XHTML, but what I am reading now seems to contradict this. This is the part
> of standards where I get a bit confused. Does anyone have any advice or know
> of some good articles where they explain this in simple terms??

The problem is not with your XHTML but with your server. Most likely
you are running Apache with AddDefaultCharset in configuration. If you
have access to httpd.conf you
should just comment out this directive, or change it to utf-8.

Regards,
Rimantas
**
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] Character encoding mismatch

[Paul Collins]

I am getting the following warning when I 
validate my pages:
 
--
Character Encoding mismatch!

  
  The character encoding specified in the HTTP header 
  (iso-8859-1) is different from the value in the 
   element (utf-8). I will use the value 
  from the HTTP header (iso-8859-1) for this 
validation.
--
My header code looks like this, which should validate fine:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">http://www.w3.org/1999/xhtml" 
xml:lang="en" 
lang="en"> title 
I have just started reading more about character encoding and special 
characters, is my problem that I have used decimal character refereces? For 
example
- as -
' as '
and so on. I thought this was the correct way to add special characters for 
XHTML, but what I am reading now seems to contradict this. This is the part of 
standards where I get a bit confused. Does anyone have any advice or know of 
some good articles where they explain this in simple terms??
Cheers