1.5 what.? [EMAIL PROTECTED] 6/06/2006 3:35:42 pm
Hi all
Is this valid css and if not what's wrong with it:
font: 2.2em/1.5;
Regards
Bojana
Global Summit 2006: Technology Connected Futures -- 17-19 October, Sydney, Australia.
Visit our website http://globalsummit.educationau.edu.au
Hi All,
I'm trying to implement a CSS/_javascript_ dropdown navigation (as shown at the seminars recently) and all's well in IE7, firefox and safari, though in IE6 the navigation div pushes the content of the adjoining div over to the right by a few pixels. I've tried to adjust the padding,
Hu Andreas,
Cool tool, but, just in case if somebody miss this out, there is another
great offline tool http://www.michelf.com/projects/sim-daltonism/
Only for Mac.
Cheers,
Dmitry
Andreas Boehmer [Addictive Media] wrote:
Hi guys,
I found this nice little tool on the web which simulates the
GIMP also has a tool for this http://gimp.org/
--
R. Potter
Design and Development Lead
Midnight Oil Design: http://www.midnightoildesign.com
Pragmatic Programming Principle #59:
Costly Tools Don't Produce Better Designs.
**
The
Read: http://www.positioniseverything.net/explorer/threepxtest.html
-Original
Message-
From:
listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED] On Behalf Of David Sam Butler
Sent: Tuesday, 6 June 2006 4:00 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] CSS navigation
Also, if you want some great inspiration
for designing a wine website, check out:
http://www.palliser.co.nz/
S
-Original
Message-
From:
listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED] On Behalf Of David Sam Butler
Sent: Tuesday,
6 June 2006 4:00
PM
To:
Well I have tried most of the WYSIWYG editors (open source and commercial) and have settled on http://www.innovastudio.com/This one was simply the easiest to use, and whilst its commercial, by far the least expensive.
Works great for FF and IE, and most importantly you can create XHTML compliant
Hi,I have never seen that value for font size before. However, if you wish to have it at that size, you can put 1.5em, rather than the math function you have. I'm guessing you are trying to get the value of 2.2/1.5 as the font size, which equals to 1.4666, round that up and you get 1.5, which is a
Bojana Lalic wrote:
Is this valid css and if not what’s wrong with it:
font: 2.2em/1.5;
the 2.2em/1.5 bit is okay and says font-sze 2.2em line height 1.5
times that...
(see:
http://www.meyerweb.com/eric/thoughts/2006/02/08/unitless-line-heights/
Eric's Archived Thoughts: Unitless
Hi all
This is the css I used to display the url at the bottom of the page:
display: block;
font-weight: bold;
font-size: 150%;
bottom: 45px;
position: absolute;
However, I've got a slight problem now. When printing out the article
that is three pages long
Hi Bojana! On 6/6/06, Bojana Lalic [EMAIL PROTECTED] wrote:
Is this valid css and if not what's wrong with it:font: 2.2em/1.5;In terms of syntax you are correct... (if you mean to indicate font-size and line-height respectively), as per my generic example of 'font' shorthand below:
body {font:
Bojana Lalic wrote:
However, I've got a slight problem now. When printing out the article
that is three pages long (when printed out) the url appears on the first
page. How do I force it to display only on the last page?
Why not put the url for the article at the end of the source code and
I have never seen that value for font size before. However, if you
wish to have it at that size, you can put 1.5em, rather than the
math function you have. I'm guessing you are trying to get the
value of 2.2/1.5 as the font size, which equals to 1.4666, round
that up and you get 1.5, which
Just trying to gauge how important it is for all of your
colors to be 100% web safe. Is this a thing of the past or still very
important?
Ryan
**The discussion list for http://webstandardsgroup.org/ See
B,
Make sure the div that is appearing at the bottom of the page appears after
your content in the HTML. Then in a print only style sheet format that block
to be position : static;
This will cause the footer to be pushed down from the content on the page
again. IE may still use the bottom CSS
From what I understand, to use 'font' as a shorthand property you have to
include the size and font-name as a minimum (in that order).
I thought the order of properties was important?
for example, isn't weight listed first?
i.e
{font: weight style variant size/line-height font-name}
or do
Ryan Moore wrote:
Hopefully this is not off-topic,
It is. Go to the WSG site and subscribe to the CMS list. This was
discussed - and moved over to that list - just a few days ago!
C'mon, people. Too many posts recently have been OT, or simple thanks
messages which would be better sent
On 6/5/06 11:15 PM Stephen Neate [EMAIL PROTECTED] sent this out:
Hope that helps :)
Even while this discussion moves off to the CMS list, could everyone please
post text-only format to this list please?
I can't read all that tiny type and I just have to delete those posts!
Please cooperate!
David Sam Butler wrote:
Hi All,
I'm trying to implement a CSS/javascript dropdown navigation (as shown
at the seminars recently) and all's well in IE7, firefox and safari,
though in IE6 the navigation div pushes the content of the adjoining
div over to the right by a few pixels. I've tried
Google Colour blindness simulator and you get over 300 results. Can
we look there, and not list them here one at a time?
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some
On Jun 5, 2006, at 11:12 PM, Nick Gleitzman wrote:
Ryan Moore wrote:
Hopefully this is not off-topic,
It is. Go to the WSG site and subscribe to the CMS list. This was
discussed - and moved over to that list - just a few days ago!
C'mon, people. Too many posts recently have been OT, or
If you float div#pagebody the border will returnAn element that contain floated elements must be floated to retain their height. Hopefully somebody can explain it fully (and better than that).
-- Nick Cowiehttp://nickcowie.com
**The discussion
On Jun 6, 2006, at 4:02 PM, Herrod, Lisa wrote:
From what I understand, to use 'font' as a shorthand property you
have to
include the size and font-name as a minimum (in that order).
I thought the order of properties was important?
for example, isn't weight listed first?
i.e
{font:
Works Great, good enough for me.
Cheers.
From:
listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED] On Behalf Of Nick Cowie
Sent: Tuesday, June 06, 2006 4:41
AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Why is Border
Getting Eaten
If you float div#pagebody the
On 6/6/06, Herrod, Lisa [EMAIL PROTECTED] wrote:
>From what I understand, to use 'font' as a shorthand property you have toinclude the size and font-name as a minimum (in that order).Yep!
I thought the order of properties was important?for example, isn't weight listed first?i.e{font: weight
Jan Brasna
Right. Nowadays you should have no problems with colors
I think that, as always, this will come down to your target audience.
If you know for a fact that there are still a sizeable proportion of
your users on 800x600 with only 256 colours or similar, it's obviously
worth
On 6/6/06, Patrick Lauke [EMAIL PROTECTED] wrote:
avoid that a foreground and background colour resolves to
the exact same safe colour.
And, obviously, if this is happening there's probably already enough
wrong with your design's contrast that safe colours should be the
least of your concerns.
actually, the order is as I stated before:
font-style font-variant font-weight font-size/line-height font-family
or do you guys find it works in any order?
I've never used it out of order, so I can't tell you, sorry!
Pulling out my copy of Eric Meyer (Definitive Guide) (incredibly
They do come into it if you print things any other way - many users
don't trust 'print links' for various reasons, and the appearance of the
full page is not exactly great if all frames are printed on one page -
scroll bars aren't very useful on paper!
Mike
-Original Message-
snip
Joshua Street
On 6/6/06, Patrick Lauke [EMAIL PROTECTED] wrote:
avoid that a foreground and background colour resolves to
the exact same safe colour.
And, obviously, if this is happening there's probably already enough
wrong with your design's contrast that safe colours should be the
just test, test, test and test on as many computers as possible and you should be okOn 6/6/06, Patrick Lauke
[EMAIL PROTECTED] wrote: Joshua Street On 6/6/06, Patrick Lauke
[EMAIL PROTECTED] wrote: avoid that a foreground and background colour resolves to the exact same safe colour. And,
[EMAIL PROTECTED] wrote:
They do come into it if you print things any other way - many users
don't trust 'print links' for various reasons, and the appearance of the
full page is not exactly great if all frames are printed on one page -
scroll bars aren't very useful on paper!
Mike
Fair point
On 6/6/06 3:52 AM Ryan Moore [EMAIL PROTECTED] sent this out:
Address: http://www.rockitdevelopment.com/haley/
Tiny text. Deleted 'cause I can't read the text.
**
The discussion list for http://webstandardsgroup.org/
See
Yo,
Has anyone developed a method for working in the ff css editor that keeps
the background images on the page from doing a disappearing act when the
editor window is opened. I thought it was solved by keeping my bg images at
the same root as the stylesheets during development but that's not
Herrod, Lisa wrote:
Wow, That's fontastic!
thanks lachlan hardy
you're a fontain of knowledge
Fonting hell, Lisa! I think you may be endangering the fontamental
nature of this list. Posts of this type rarely carry the weight we're
accustomed to and we wind up being cursive towards the
Hi Ryan,
If you notice at the bottom of my mock up banner, “helping hand” you’ll
notice a white space that has been added to the bottom of its div. the
div is the div id=”banner”. There’s a red border at the bottom of it
that will be removed upon final, but just trying to figure out what is
On 6 Jun 2006, at 10:13 PM, Mark Harris wrote:
Herrod, Lisa wrote:
Wow, That's fontastic!
thanks lachlan hardy
you're a fontain of knowledge
Fonting hell, Lisa! I think you may be endangering the fontamental
nature of this list. Posts of this type rarely carry the weight we're
On 6/6/06 8:50 AM, Nick Gleitzman [EMAIL PROTECTED] wrote:
Fonting hell, Lisa! I think you may be endangering the fontamental
nature of this list. Posts of this type rarely carry the weight we're
accustomed to and we wind up being cursive towards the poster. You
must be working from a
Nick Gleitzman wrote:
Google Colour blindness simulator and you get over 300 results. Can we
look there, and not list them here one at a time?
Indeed.
Also, I am slightly red/greeen color blind, so if anyone wants a real
person look at your site, i'd be happy to check it out.
Yesterday I have connected PDA to the Internet and have looked as sites
under web-standards are well looked.
http://whale-zx.livejournal.com/8498.html
Not so well...
--
Kit
http://www.zamyteam.com/
**
The discussion list for
Leskinen N.
Yesterday I have connected PDA to the Internet and have
looked as sites
under web-standards are well looked.
http://whale-zx.livejournal.com/8498.html
Not so well...
So...the mobile version of IE tries half-heartedly to apply some
screen CSS and fails? Quelle surprise!
Hi, I'd like to take you up on your offer, and the same goes to any other members who may have a visual impairment.
I'm looking for some volunteers to pilot my questionnaire available at www.roboneill.co.uk/research.htmwhose eventual audience will be the visually impaired.
I'm looking for
To any WSG members who could use some Web standards-compliant Web sites can
and do work successfully:
Don't be discouraged with what you may have so far encountered, namely,
rather poor representations of Web site pages, particularly on small screen
rendering devices such as Portable Digital
Robert O'Neill wrote:
Hi, I'd like to take you up on your offer, and the same goes to any
other members who may have a visual impairment.
Hi Rob,
The large text toggle has some issues Some border and height
elements are set in fixed pixel height, so when the text is expanded, it
Robert O'Neill wrote:
Hi, I'd like to take you up on your offer, and the same goes to any
other members who may have a visual impairment.
On second look (I didn't get this far before I sent the last message)
http://www.roboneill.co.uk/first_questionnaire.htm
The dark red on pink and yellow is
To any WSG members who could use some encouragement by way of examples of
Web standards-compliant Web sites that can and do work successfully on PDAs,
SmartPhones, etc.:
Don't be discouraged with what you may have so far encountered, namely,
rather poor representations of Web site pages,
Mobile appliances are notoriously difficult to program for. Cell phone and
PDA manufacturers are still stuck in the Wild West days of browser wars. You
just have to do the best you can and hope the majority of people can view
your stuff.
I'm not on the Yahoo! mobile project, but from what I
www.roboneill.co.uk/research.htm
http://www.roboneill.co.uk/research.htm
1. the wording of questions
2. the ordering of questions
3. the suitability of questions
4. if instructions are adequate.
Give all the options e.g. Firefox etc., if it needs to be for the
general user. Spell it
Hi,I normally use a name="section1" to identify a particular section for linking within the same document. However, XHTML Strict won't allow the attribute "name". Is there another way to do this?Thanks, Minh __Do You Yahoo!?Tired of spam?
Use IDs a id=section1
Minh D. Tran wrote:
Hi,
I normally use a name=section1 to identify a particular section for
linking within the same document. However, XHTML Strict won't allow the
attribute name. Is there another way to do this?
Thanks,
Minh
Minh D. Tran wrote:
Hi,
I normally use a name=section1 to identify a particular section for
linking within the same document. However, XHTML Strict won't allow the
attribute name. Is there another way to do this?
a id=section1/a
or the better method,
h1 id=section1This is a header/a
A
oh duh! why didn't i think of that. Thanks!Mark Sheppard [EMAIL PROTECTED] wrote: Use IDs Minh D. Tran wrote: Hi, I normally use to identify a particular section for linking within the same document. However, XHTML Strict won't allow the attribute "name". Is there another way to do this?
Minh D. Tran wrote:
oh duh! why didn't i think of that. Thanks!
Actually, I believe you should use both (id *and* name).
Also, you should make sure your jump links work with keyboard navigation:
http://juicystudio.com/article/ie-keyboard-navigation.php
---
Regards,
Thierry | www.TJKDesign.com
Thierry Koblentz wrote:
Minh D. Tran wrote:
oh duh! why didn't i think of that. Thanks!
Actually, I believe you should use both (id *and* name).
Not in XHTML 1.1, where name doesn't exist. And it's deprecated in XHTML
1.0, so you shouldn't use it there either.
--
We have become so
In XHTML 1.1, name doesn't validate but id does. So we should just do away with name altogether."Rev. Kalle Räisänen" [EMAIL PROTECTED] wrote: Thierry Koblentz wrote: Minh D. Tran wrote: oh duh! why didn't i think of that. Thanks! Actually, I believe you should use both (id *and* name).Not in
Rev. Kalle Räisänen wrote:
Thierry Koblentz wrote:
Minh D. Tran wrote:
oh duh! why didn't i think of that. Thanks!
Actually, I believe you should use both (id *and* name).
Not in XHTML 1.1, where name doesn't exist. And it's deprecated in
XHTML
1.0, so you shouldn't use it there either.
From: Brian Cummiskey
or the better method,
h1 id=section1This is a header/a
Surely that can't be right?
Something that opens as a h must surely close as a h.
--
Peter Williams
**
The discussion list for http://webstandardsgroup.org/
hm. OK, so I've given my content div a margin-left: 160px; (10 more than the width of the leftNav div) but although it stops the problem it moves that whole div to the right 10px and obviously that's not what i want. I take it there's something I'm not quite getting with this, any more
Rev. Kalle Räisänen wrote:
Yes, the name attribute is deprecated in XHTML 1.0, not removed. It
is, however, removed in XHTML 1.1. Deprecation is enough to make me
avoid something.
I'll give you a point on better backwards (though not forwards)
compatibility, but why would name attributes
Ryan Moore wrote
Address: http://www.rockitdevelopment.com/haley/
If you notice at the bottom of my mock up banner, helping hand
you'll notice a white space that has been added to the bottom of
its div. the div is the div id=banner.
For future reference, Firefox displays images vertical
Thierry Koblentz wrote:
Rev. Kalle Räisänen wrote:
I'll give you a point on better backwards (though not forwards)
compatibility, but why would name attributes offer richer anchor
names? What does name give you that id doesn't?
For example one can use:
a name=1st_Section/a
but not:
a
It looks like youve got things
backwards on it, your overriding the * html #content hack with the rule
underneath it.
Move the #content up above the * html
hacks so it is directly below the #leftnav rule, that way IE will read the
hacks and overrule the original #content margins etc.
Rev. Kalle Räisänen wrote:
Thierry Koblentz wrote:
Rev. Kalle Räisänen wrote:
I'll give you a point on better backwards (though not forwards)
compatibility, but why would name attributes offer richer anchor
names? What does name give you that id doesn't?
For example one can use:
a
Set the image to display : block; to fix this.
-Original Message-
From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED]
On Behalf Of Scott Swabey
Sent: Wednesday, 7 June 2006 9:34 AM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] Haley White Space Nav
Ryan Moore wrote
Also, your company homepage has a doc title of Untitled Document
-Original Message-
From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED]
On Behalf Of Scott Swabey
Sent: Wednesday, 7 June 2006 9:34 AM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] Haley White Space Nav
Ryan
thanks for that. I'm really getting more confused as I've played around and now although it 'works' it looks nothing like the 'original' hack. I've had to put a -3px margin to the floated div to pull the content div back over to the leftNav div, whereas the hack said to set this to margin-right:
Peter Williams wrote:
From: Brian Cummiskey
or the better method,
h1 id=section1This is a header/a
Surely that can't be right?
Something that opens as a h must surely close as a h.
I'm sure Brian meant:
h1 id=section1This is a header/h1
Kat
Prefix: Does anyone have an elegant solution for this input caret problem?
I have a basic CSS dropdown menu (nested UL's). Works a treat, I've
built a heap of them.
However, when I have the menus go over the TOP of an input text field
that has focus, the caret displays through the menu.
I
HiAny chance of an exampleThanksOn 6/7/06, Ned Collyer [EMAIL PROTECTED] wrote:
Prefix: Does anyone have an elegant solution for this input caret problem?I have a basic CSS dropdown menu (nested UL's).Works a treat, I've
built a heap of them.However, when I have the menus go over the TOP of an
unfortunately, you wont be able to fix this problem in IE. In IE, select elements are drawn using the native window library widgets and are thus sitting on top of the html page layer. Therefore, no html element can go above these decorations.
Take a look at this example that actually hides a
URL? I've only seen the select form element showing through dropdowns, and
the iframe shim you've described below is the solution for that.
-Original Message-
From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED]
On Behalf Of Ned Collyer
Sent: Wednesday, 7 June 2006 11:01 AM
To:
Youve got a whole bunch of hacks in
there now, Id say theyre conflicting with each other. Strip it
out and replace with:
#floatbox {
float: left;
width: 150px;
}
#content {
background-color :
#fff;
margin-left :
150px;
padding : 5px 5px 5px
10px;
}
/* Hide from
Ya, it's a work in progress. We're trying to have the new version up for
the first of the week.
Appreciate the assistance though.
-Original Message-
From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED]
On Behalf Of Samuel Richardson
Sent: Tuesday, June 06, 2006 9:26 PM
To:
yeah, i tried that earlier and it gives me a 3px gap between the leftNav (floated div) and the content (adjoining div), that's when I set the hack for the leftNav to:
* html #leftNav {margin-right: -3px }
which brings the #content back next to the floated #leftNav.
sam
[EMAIL PROTECTED]
John S. Britsios wrote:
[trim...we would appreciate to get pointers to Accessibility problems
you might discover on our new web site http://www.webnauts.net/
John
xp_sp2 ie, ff, moz, opera
Although I am an accessibility novice, I find your site difficult to
fault. It is easy to read at
Incorrect, you can place an iframe shim behind
the popup layer to make it appear over the top the select element.
Example here: http://developer.yahoo.com/yui/examples/container/panel.html
-Original
Message-
From:
listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED] On
Title: Out of Office AutoReply: digest for wsg@webstandardsgroup.org
I'm out of the office until 9 June.
If you have any urgent matter please contact Alistair Tegart via email on: [EMAIL PROTECTED]
**The discussion list for
Testing our site http://www.webnauts.net with the W3C validator here
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.webnauts.net%2Fcharset=%28detect+automatically%29doctype=Inlineoutline=1
I got the message:
Outline
Below is an outline for this document, automatically generated from the
Peter Williams wrote:
From: Thierry Koblentz
For example one can use:
a name=1st_Section/a
but not:
a id=1st_Section/a
Then rhere's the issue that class/id names can't start with
a numeric character, so you'd be wiser to use something like
name=firstsection or id=firstsection.
The whole
I do have a print stylesheet and this is what's in it:
.framework_url {
display: block;
font-weight: bold;
font-size: 150%;
bottom: auto;
position: static;
}
I've also got another stylesheet which has the following:
.framework_url {
display: none;
John S. Britsios wrote:
While we strive to comply to WCAG 1.0 AAA and to the Communication
Technologies Branch of the United States National Cancer Institute
guidelines for accessible and usable web sites: Observing Users Who
Work With Screen Readers, we would appreciate to get pointers to
81 matches
Mail list logo
