[WSG] Container Background Image Does Not Appear in Firefox

2007-06-19 Thread Joyce Evans
I'm new to this group, and I'm not sure if it's okay to post a question, but
here it is:

 

I've designed a website and am now creating the CSS for the home page.  This
is the CSS for my main container div:

 

#container {

width: 760px;

background-color: #00;

color: #00;

margin: 0 auto;

padding: 0;

text-align: left;

background-image: url(images/bg_container.jpg);

background-repeat: repeat-y;

}

 

The problem is that the bg_container.jpg image does not appear in Mozilla
Firefox; however it appears in IE 7.  bg_container.jpg is 760 px wide with
the first pixel and the last pixel being black.  All the pixels in between
are white, thus creating a thin black border on the left and right hand
sides of the 760 px container.  In the latest version of Firefox, I do not
see these two black lines.

 

Could someone please advise.

 

Thanks!



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

RE: [WSG] Container Background Image Does Not Appear in Firefox

2007-06-19 Thread Joyce Evans
Here is the link to the incomplete home page.  It's as far as I have gotten
with the CSS.  The CSS file name is brookgrooves_home.css, and it is an
external style sheet, which you'll be able to download.

http://www.nichemktghouston.com/bookgrooves/index.html

Notice that the dark lines appear to the left and the right in IE but not in
Firefox.

This is how the design sample looks prior to my programming.  This is simply
one jpg file:

http://www.nichemktghouston.com/bookgrooves/HomePageSample17e_ltGrnTitles.ht
ml

I can't even imagine how I'm going to handle the Topic and Members columns
with CSS, as well as the three columns for Popular Reads with the images of
the books.  It's been painful, but I'm trying not to use tables.

Nonetheless, I'm not using a border because I need to figure out how to get
the background image to appear in Firefox.  I use background images often,
and they usually aren't as simple as a border. 

Thank you.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of John Faulds
Sent: Tuesday, June 19, 2007 7:00 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Container Background Image Does Not Appear in Firefox

We need to see more of your code or a link to your page but I suspect your  
container probably contains floated content and you haven't cleared your  
floats properly.
I have to ask though, if your image is just creating black borders on  
either side of the container, why don't you use borders in CSS instead?

On Wed, 20 Jun 2007 09:40:15 +1000, Joyce Evans  
[EMAIL PROTECTED] wrote:

 I'm new to this group, and I'm not sure if it's okay to post a question,  
 but
 here it is:


 I've designed a website and am now creating the CSS for the home page.   
 This
 is the CSS for my main container div:


 #container {

 width: 760px;

 background-color: #00;

 color: #00;

 margin: 0 auto;

 padding: 0;

 text-align: left;

 background-image: url(images/bg_container.jpg);

 background-repeat: repeat-y;

 }


 The problem is that the bg_container.jpg image does not appear in Mozilla
 Firefox; however it appears in IE 7.  bg_container.jpg is 760 px wide  
 with
 the first pixel and the last pixel being black.  All the pixels in  
 between
 are white, thus creating a thin black border on the left and right hand
 sides of the 760 px container.  In the latest version of Firefox, I do  
 not
 see these two black lines.


 Could someone please advise.


 Thanks!



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



-- 
Tyssen Design
www.tyssendesign.com.au
Ph: (07) 3300 3303
Mb: 0405 678 590


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





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



RE: [WSG] Container Background Image Does Not Appear in Firefox

2007-06-19 Thread Joyce Evans
Thank you to all who responded.  I added overflow: hidden; to #container,
as suggested by John Faulds below, and I now see the background image in
Firefox, as well as IE.  

I obviously have much reading/learning to do.

Thank you. 

Joyce 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of John Faulds
Sent: Tuesday, June 19, 2007 7:56 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Container Background Image Does Not Appear in Firefox

It's as I said before. Your layout contains floated content and you  
haven't cleared your floats. Adding overflow: hidden to #container will  
make the borders appear in Firefox but you should do some reading up on  
'clearing floats'.

On Wed, 20 Jun 2007 10:35:50 +1000, Joyce Evans  
[EMAIL PROTECTED] wrote:

 Here is the link to the incomplete home page.  It's as far as I have  
 gotten
 with the CSS.  The CSS file name is brookgrooves_home.css, and it is an
 external style sheet, which you'll be able to download.

 http://www.nichemktghouston.com/bookgrooves/index.html

 Notice that the dark lines appear to the left and the right in IE but  
 not in
 Firefox.

 This is how the design sample looks prior to my programming.  This is  
 simply
 one jpg file:


http://www.nichemktghouston.com/bookgrooves/HomePageSample17e_ltGrnTitles.ht
 ml

 I can't even imagine how I'm going to handle the Topic and Members  
 columns
 with CSS, as well as the three columns for Popular Reads with the images  
 of
 the books.  It's been painful, but I'm trying not to use tables.

 Nonetheless, I'm not using a border because I need to figure out how to  
 get
 the background image to appear in Firefox.  I use background images  
 often,
 and they usually aren't as simple as a border.

 Thank you.


 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of John Faulds
 Sent: Tuesday, June 19, 2007 7:00 PM
 To: wsg@webstandardsgroup.org
 Subject: Re: [WSG] Container Background Image Does Not Appear in Firefox

 We need to see more of your code or a link to your page but I suspect  
 your
 container probably contains floated content and you haven't cleared your
 floats properly.
 I have to ask though, if your image is just creating black borders on
 either side of the container, why don't you use borders in CSS instead?

 On Wed, 20 Jun 2007 09:40:15 +1000, Joyce Evans
 [EMAIL PROTECTED] wrote:

 I'm new to this group, and I'm not sure if it's okay to post a question,
 but
 here it is:


 I've designed a website and am now creating the CSS for the home page.
 This
 is the CSS for my main container div:


 #container {

 width: 760px;

 background-color: #00;

 color: #00;

 margin: 0 auto;

 padding: 0;

 text-align: left;

 background-image: url(images/bg_container.jpg);

 background-repeat: repeat-y;

 }


 The problem is that the bg_container.jpg image does not appear in  
 Mozilla
 Firefox; however it appears in IE 7.  bg_container.jpg is 760 px wide
 with
 the first pixel and the last pixel being black.  All the pixels in
 between
 are white, thus creating a thin black border on the left and right hand
 sides of the 760 px container.  In the latest version of Firefox, I do
 not
 see these two black lines.


 Could someone please advise.


 Thanks!



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






-- 
Tyssen Design
www.tyssendesign.com.au
Ph: (07) 3300 3303
Mb: 0405 678 590


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





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



[WSG] Robot meta tags

2007-07-03 Thread Joyce Evans
I'm new to this group, so if this discussion has occurred in the past, I'm
not aware of it.

 

Is it important to include the following as part of the meta tags on web
pages?

 

meta name=robots content=index,follow

 

Joyce



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

RE: [WSG] Footer Problem IE5.x

2007-07-03 Thread Joyce Evans
Regarding Why beat your head against the wall of buggy browsers when the 
manufacturer themselves supplies a workaround?

I want to know more about conditional comments.  Is this a good resource?
http://msdn2.microsoft.com/en-us/library/ms537512.aspx#Conditional_Statement
s


Joyce

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Nick Gleitzman
Sent: Monday, July 02, 2007 3:28 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Footer Problem IE5.x


On 2 Jul 2007, at 6:09 PM, Sarah Peeke (XERT) wrote:

 I guess I was hoping to fix the problem(s), rather than just rely on a
 hack. Other suggestions appreciated.

Fair enough, but I'd say your chances of getting the one set of css 
rules to display correctly in all browsers are pretty slim - especially 
if you want to include browsers as flawed as Exploder 5.x. Even MS 
themselves accept how hard this is - hence CCs.

I routinely serve as many as three alternative stylesheets vis CCs for 
different versions of IE. They only need to contain a handful of rules 
necessary to override the correct values served to compliant browsers.

Whether you consider CCs a hack is, I guess, subjective. But your code 
will validate, and they're easy to remove with a global search and 
replace if and when the time comes that you don't need them any more.

Why beat your head against the wall of buggy browsers when the 
manufacturer themselves supplies a workaround?

N
___
omnivision. websight.
http://www.omnivision.com.au/



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





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



RE: [WSG] To target or not

2007-07-19 Thread Joyce Evans
I always thought it was a good idea to open links to other websites in a
separate window, so you don't lose the visitor.  If the visitor clicks on a
link on your website and it does not open into a separate window, the
visitor may stay in the other website for awhile, going to, say, 20
different pages.  Most likely, he's not going to click on the back button 20
times to get back to your website, so you've lost the visitor or potential
customer.  If the link opens up into a separate window, the visitor cannot
click on the back button, so he'll need to click on the exit (X) button, and
voila, he's back in your website, where you want him to be.

Joyce Evans
Niche Marketing
www.nichemktghouston.com

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Matthew Ohlman
Sent: Thursday, July 12, 2007 9:21 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] To target or not

Hello List,

I was curious what others opinions were on this issue...

Since W3C doesn't allow the target attribute in XHTML Strict, which do 
you think is better?  Having the window opening up with JavaScript or 
just keeping the page in the same window like W3C wants. 

I assume the reason for not allowing the target attribute is for 
accessibility--because screen readers can not control pop-ups.  
Therefore it seems logical to me to keep it in the same window--even if 
it is an external site, etc.

What does everyone think?

Matthew
-- 
Matthew Ohlman
www.ohlman.com


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





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



RE: [WSG] To target or not

2007-07-19 Thread Joyce Evans
I'm all about web conventions.  I didn't realize having a blank target
didn't follow web standards.  Is that documented somewhere?

Joyce Evans

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Lane
Sent: Thursday, July 19, 2007 4:45 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] To target or not

My suggestion is simple: let it be the content and presentation that 
keeps people on your site, not gimmickry.  Most smart web surfers use 
Firefox or Opera or a lesser browser that is nonetheless tabbed.  If I 
want to stay on a page, I open links from that page in new background 
tabs while I continue to read the page.

I find it oh-so-frustrating to have a site designer decide how my 
browsing should work, breaking web conventions (note, web conventions 
exist for a reason... they're what people expect - I recommend people 
think long and hard before they break them).

If I click on a link on their site I expect it to open in my current 
window - if it insists on opening a new window, it pisses me off, 
because that's not how I work.  I see that approach as indicating a 
designer still in a very IE5.5-6 mindset: primitive.  Sites that try to 
manipulate me don't pique my interest, they put me right off (and, 
needless to say, I don't go back).

Dave

Joyce Evans wrote:
 I always thought it was a good idea to open links to other websites in a
 separate window, so you don't lose the visitor.  If the visitor clicks on
a
 link on your website and it does not open into a separate window, the
 visitor may stay in the other website for awhile, going to, say, 20
 different pages.  Most likely, he's not going to click on the back button
20
 times to get back to your website, so you've lost the visitor or potential
 customer.  If the link opens up into a separate window, the visitor cannot
 click on the back button, so he'll need to click on the exit (X) button,
and
 voila, he's back in your website, where you want him to be.
 
 Joyce Evans
 Niche Marketing
 www.nichemktghouston.com
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Matthew Ohlman
 Sent: Thursday, July 12, 2007 9:21 PM
 To: wsg@webstandardsgroup.org
 Subject: [WSG] To target or not
 
 Hello List,
 
 I was curious what others opinions were on this issue...
 
 Since W3C doesn't allow the target attribute in XHTML Strict, which do 
 you think is better?  Having the window opening up with JavaScript or 
 just keeping the page in the same window like W3C wants. 
 
 I assume the reason for not allowing the target attribute is for 
 accessibility--because screen readers can not control pop-ups.  
 Therefore it seems logical to me to keep it in the same window--even if 
 it is an external site, etc.
 
 What does everyone think?
 
 Matthew

-- 
Dave Lane == Egressive Ltd == [EMAIL PROTECTED] == +64 21 229 8147
+64 3 963 3733 = Linux: it just tastes better = no software patents
http://egressive.com  we only use open standards: http://w3.org
Effusion Group Founding Member === http://effusiongroup.com


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





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



RE: [WSG] To target or not

2007-07-19 Thread Joyce Evans
Oops.  My response was posted after Philip Kiff gave some web standards
links.  Thanks.

Joyce Evans

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Joyce Evans
Sent: Thursday, July 19, 2007 5:44 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] To target or not

I'm all about web conventions.  I didn't realize having a blank target
didn't follow web standards.  Is that documented somewhere?

Joyce Evans

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Lane
Sent: Thursday, July 19, 2007 4:45 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] To target or not

My suggestion is simple: let it be the content and presentation that 
keeps people on your site, not gimmickry.  Most smart web surfers use 
Firefox or Opera or a lesser browser that is nonetheless tabbed.  If I 
want to stay on a page, I open links from that page in new background 
tabs while I continue to read the page.

I find it oh-so-frustrating to have a site designer decide how my 
browsing should work, breaking web conventions (note, web conventions 
exist for a reason... they're what people expect - I recommend people 
think long and hard before they break them).

If I click on a link on their site I expect it to open in my current 
window - if it insists on opening a new window, it pisses me off, 
because that's not how I work.  I see that approach as indicating a 
designer still in a very IE5.5-6 mindset: primitive.  Sites that try to 
manipulate me don't pique my interest, they put me right off (and, 
needless to say, I don't go back).

Dave

Joyce Evans wrote:
 I always thought it was a good idea to open links to other websites in a
 separate window, so you don't lose the visitor.  If the visitor clicks on
a
 link on your website and it does not open into a separate window, the
 visitor may stay in the other website for awhile, going to, say, 20
 different pages.  Most likely, he's not going to click on the back button
20
 times to get back to your website, so you've lost the visitor or potential
 customer.  If the link opens up into a separate window, the visitor cannot
 click on the back button, so he'll need to click on the exit (X) button,
and
 voila, he's back in your website, where you want him to be.
 
 Joyce Evans
 Niche Marketing
 www.nichemktghouston.com
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Matthew Ohlman
 Sent: Thursday, July 12, 2007 9:21 PM
 To: wsg@webstandardsgroup.org
 Subject: [WSG] To target or not
 
 Hello List,
 
 I was curious what others opinions were on this issue...
 
 Since W3C doesn't allow the target attribute in XHTML Strict, which do 
 you think is better?  Having the window opening up with JavaScript or 
 just keeping the page in the same window like W3C wants. 
 
 I assume the reason for not allowing the target attribute is for 
 accessibility--because screen readers can not control pop-ups.  
 Therefore it seems logical to me to keep it in the same window--even if 
 it is an external site, etc.
 
 What does everyone think?
 
 Matthew

-- 
Dave Lane == Egressive Ltd == [EMAIL PROTECTED] == +64 21 229 8147
+64 3 963 3733 = Linux: it just tastes better = no software patents
http://egressive.com  we only use open standards: http://w3.org
Effusion Group Founding Member === http://effusiongroup.com


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





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





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



RE: [WSG] Re: please avoid forcing people to open pdf in browser!

2007-07-23 Thread Joyce Evans
This seems to be a good idea.  Could you please give an example where this
code would be placed on the web page or how it would fit into the code?  I'm
having a blank moment.  Thanks.  

 

Joyce 

  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Jixor - Stephen I
Sent: Sunday, July 22, 2007 3:20 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Re: please avoid forcing people to open pdf in browser!

 

Jermayn,

Use a content-disposition header to force a download so that the user
doesn't have to have their browser potentially crippled by Acrobat and its
easy to save for later viewing.

Content-disposition: attachment; filename=document.pdf



Jermayn Parker wrote: 

pdfs are not going to go away (and docs are not the answer)
 
in Nielsons article (who is over rated and take his opinion with a
grain of salt) he says pdfs are for print and I agree but for most
Government websites they need these pdfs that we all hate and as I said
in an earlier email html versions is not always an option.
 
So the question remains how do we make a linked pdf presented and
operational the best??
 
 
 
 
  

[EMAIL PROTECTED] 20/07/2007 10:08:52 am 


On 2007/07/19 11:23 (GMT+1000) Webb, KerryA apparently typed:
 
  

Jermayn wrote:


 
  

I work at one of the those government places that has those
  

horrible
  

pdfs scattered through out all their horrible pages. I couldnt
  

agree
  

more.
  

 
  

And I work with people who build such sites, and I don't have a


problem
  

with PDFs per se.


 
As a rule, I do. Most are apparently made by and for the people who
design
inaccessible mousetype web sites, not for normal or low vision web
users.
 
  

If that's an efficient and effective way to publish a document, let


them
 
Efficient and effective only from a publisher's perspective, not from
a
user's perspective. Pdfs are for printing. Ecologically aware people
are not
interested in killing trees just to get a little freely available
information.
 
  

do it - providing the PDF is properly marked up.


 
It's rare that pdfs are published to be univerally accessible, so the
end
result is that as a group, pdfs are a scourge. Nielsen is too polite
about
it: http://www.useit.com/alertbox/20030714.html 
  

 


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


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

RE: [WSG] Using target=_blank

2007-07-24 Thread Joyce Evans
I agree with you completely, but we are definitely in the minority here.  

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, July 24, 2007 12:19 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Using target=_blank

Personally I prefer links to open in the same Window. But that's me. And I 
don't want to force my preference on anyone. That's why it's nicer to leave

it to the user to decide. The only way to let users decide is to open links

in the same window by default and teach said users a function of their 
browser they may not be aware of. Or to provide some preference control 
widget.

Sorry but I don't agree...to a point. As a web designer and user myself, I
prefer opening another window IF it is to a different website that I am
referring them to. That way the customer doesn't go wondering thru the other
website and forget to come back to mine. Mine will always be open in the
background to remind them (kind of like I'm the one they came to the dance
with).
Now if the link is in my own website, then of course I prefer them to be in
the same window. I co not believe you have to TEACH a potential
consumer/buyer to use your site. It should have a natural flow and be easy
to use.



Thanks  best,
Jim Barricks
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
Barricks Insurance Services
13900 NW Passage #302, Marina Del Rey, CA 90292
Phone: (310) 827-7286  |  Fax:  (310) 827-0256
Toll-Free 1-877-Look4Life  (1-877-566-5454)
http://www.barricksinsurance.com  | CA License 0383850  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
Life is not a journey to the grave with the intention of arriving 
safely in a pretty and well preserved body, but rather to skid in 
broadside, thoroughly used up, totally worn out, and loudly proclaiming 
 WOW -- What a Ride! 
*  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  * 


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





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



RE: [WSG] Using target=_blank

2007-07-24 Thread Joyce Evans
Links to other websites that are opened in a separate window from my
websites using target=_blank don't go to competitors' websites.  They are
simply informational.

 

  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Andrew Maben
Sent: Tuesday, July 24, 2007 1:16 PM
To: wsg@webstandardsgroup.org
Cc: Andrew Maben
Subject: Re: [WSG] Using target=_blank

 

On Jul 24, 2007, at 1:19 PM, [EMAIL PROTECTED] wrote:





That way the customer doesn't go wondering thru the other website and forget
to come back to mine.

 

If you go to the mall, would you be happier if every store you entered
assigned a staff member to accompany you so you don't forget to come back?
I don't think so. If you're looking for a specific item, you're likely to be
comparison shopping and perfectly capable of remembering which store has
what you want and finding your own way back. If you're just browsing, then
you'll remember stores that offer a pleasant experience - friendly and
helpful staff, selection and quality of merchandise and ambiance - and will
probably go back, even eventually mke a purchse, perhaps become a regular
customer. If the experience is unpleasant - heavy handed sales techniques,
poor quality, dingy premeises - you're equally likely to remember, never to
return... Probably the two most insulting customer relations postures are
coercion and insulting the customer's intelligence.

 

Further, it's a misunderstanding of the dynamics of the relationship to
speak of users visiting your site. On the contrary, the user is extending an
invitation to your site to visit HER browser, on HER computer, in HER home
or workplace, so you (we) are beholden to the highest standards of courtesy
and respect, if you hope to be invited back.

 

Andrew

 

 http://www.andrewmaben.com/ http://www.andrewmaben.net

 mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

 

In a well designed user interface, the user should not need instructions.





 


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


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

RE: [WSG] Site test Google analytics

2007-07-26 Thread Joyce Evans
I like the photo gallery.  Did you get the code from another source, or did
you write it?  If from another source, do you mine sharing?  I wasn't a
member back in May.

Thanks.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Jason Robb
Sent: Thursday, July 26, 2007 4:25 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] Site test  Google analytics

Hello everyone,

I launched a site today. http://www.barbarawellsstudio.com - I'm looking 
for some criticism, any suggestions are appreciated. On a side note, I 
posted a thread back in late May on Photo Gallery markup. My solution is 
located here: http://www.barbarawellsstudio.com/collections/

Also, when including Google Analytics, they ask to insert the script 
into the body, just before the end of the /body.

My question is this: If I insert the script anywhere but the head, 
does this break any rules or standards? Shouldn't all scripts be located 
in the head ONLY? Perhaps I am way off on this.

Much thanks in advance,

Jason Robb
www.eleventy72.com


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





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



RE: [WSG] an inline element (inside a block element) sibling ofanother block element

2007-07-26 Thread Joyce Evans
I just came across some code on a website that I'm maintaining and realized
this is what this thread is about.  The code I see is:

div class=nav_sub_left
a href=../news.htmlNews  lt;/a
pTestimonials lt;/p
pa href=links.htmlPartner Links lt;/a/p
/div

Are you all saying it's not good that the first line in the div tag doesn't
have paragraph tags around it?  What if the extra space a paragraph tag
would give is not wanted?  Maybe I didn't study this thread well enough.



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of E Michael Brandt
Sent: Thursday, July 26, 2007 9:38 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] an inline element (inside a block element) sibling
ofanother block element

we agree.

-- 

E. Michael Brandt

www.divaHTML.com
divaGPS : you-are-here menu highlighting
divaFAQ : FAQ pages with pizazz

www.valleywebdesigns.com
JustSo PictureWindow
JustSo PhotoAlbum

--

Raena Jackson Armitage wrote:
 On 7/27/07, *Jermayn Parker* [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] wrote:
 
 Just how can this be valid??
 the way i see it that ifyou have a paragraph or text it needs to be
 contained by a p tag or other similar tags
 
 
 
 Valid or not, it's not very semantic.
 
 -- 
 Raena Jackson Armitage
 www.raena.net http://www.raena.net
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: [EMAIL PROTECTED]
 ***


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





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



[WSG] vCard File

2007-08-01 Thread Joyce Evans
I think there may have been a discussion regarding the vCard File recently,
and if there was, I didn't study those emails because I didn't have to deal
with it at the time.  Today, however, I got a new project of re-creating a
website with the current design.  On this client's contact page, there is a
link to the .vcf file, which when I click on it, the client's contact
information appears in the Contacts section of my Outlook program.  I've
never seen a link to a vCard File on a website until today.  Is it okay to
have this link?  What happens if the visitor to the website does not use
Outlook?  Thank you.

 

Joyce

 

 



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

[WSG] CSS Problem in Mozilla and IE6

2007-08-10 Thread Joyce Evans
Here is the link to a website, and I've only gotten this far:

 

http://www.nichemktghouston.com/mneiman/physician.html

 

So far, It looks proper in IE7, but in Mozilla, the horizontal navigation
links do not center but rather move to the right so that I don't see the
full Contact link.

 

In IE 6, the pageHeader div is not stacked directly above the nav div.
There is some additional white space (from the background color).

 

Could anyone please help.  I seem to do fine with CSS when the navigation is
vertical in a column, but I always run into problems when the navigation is
horizontal.

 

Thank you,

Joyce

 

 



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

RE: [WSG] CSS Problem in Mozilla and IE6

2007-08-10 Thread Joyce Evans
And I should include the asterisk (*) as part of the code you gave me below?
Thank you.

 

Joyce

 

  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ryan Moore
Sent: Friday, August 10, 2007 1:22 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] CSS Problem in Mozilla and IE6

 

Hi Joyce,

While this may/may not help resolve your issue, i recommend adding this to
the beginning of your stylesheet.

* {
padding:0;
margin:0;
}

it will set the default margins and padding for all elements to 0.  You
would then have to specify margins and paddings for all elements, it gives
you more control over the layout as some browsers are known to have
different default margins and paddings for elements. 

RM

On 8/10/07, Gunlaug Sørtun [EMAIL PROTECTED] wrote:

Joyce Evans wrote:
 http://www.nichemktghouston.com/mneiman/physician.html

 So far, It looks proper in IE7, but in Mozilla, the horizontal 
 navigation links do not center but rather move to the right so that I
 don't see the full Contact link.

Add...
ul {padding: 0;}
...to zero out Gecko's defaults on that list. 

Nothing prevents that menu from getting skewed from font resizing though.

 In IE 6, the pageHeader div is not stacked directly above the nav
 div. There is some additional white space (from the background 
 color).

Add...
#pageHeader img {display: block;}
...to override the 'display: inline' default for that image.

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


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



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



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


RE: [WSG] CSS Problem in Mozilla and IE6

2007-08-10 Thread Joyce Evans
Thanks to all!  Everything works now.
 
Joyce

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Gunlaug Sørtun
Sent: Friday, August 10, 2007 1:08 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] CSS Problem in Mozilla and IE6

Joyce Evans wrote:
 http://www.nichemktghouston.com/mneiman/physician.html

 So far, It looks proper in IE7, but in Mozilla, the horizontal
 navigation links do not center but rather move to the right so that I
 don't see the full Contact link.

Add...
ul {padding: 0;}
...to zero out Gecko's defaults on that list.

Nothing prevents that menu from getting skewed from font resizing though.

 In IE 6, the pageHeader div is not stacked directly above the nav
 div. There is some additional white space (from the background
 color).

Add...
#pageHeader img {display: block;}
...to override the 'display: inline' default for that image.

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


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





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



RE: [WSG] CSS Problem in Mozilla and IE6

2007-08-10 Thread Joyce Evans
Good stuff!

 

Thanks!  Sorry about all of the thanks, but you guys are amazing.  I just
learned a lot!

 

  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Kepler Gelotte
Sent: Friday, August 10, 2007 1:19 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] CSS Problem in Mozilla and IE6

 

Hi Joyce,

 

Try defaulting all the element margin and padding settings to zero. You can
do this by adding the following to your CSS file:

 

* {

MARGIN: 0;

PADDING: 0;

}

 

This should take care of the Mozilla problem. Also, I noticed you have white
text over a grey background image for your navigation menu. For people who
have their images turned off, this will end up as white text on a white
background. Try setting the BACKGROUND-COLOR: #999; in #nav to fix this.

 

Regards,

Kepler Gelotte

 

  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Joyce Evans
Sent: Friday, August 10, 2007 1:22 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] CSS Problem in Mozilla and IE6

 

Here is the link to a website, and I've only gotten this far:

 

http://www.nichemktghouston.com/mneiman/physician.html

 

So far, It looks proper in IE7, but in Mozilla, the horizontal navigation
links do not center but rather move to the right so that I don't see the
full Contact link.

 

In IE 6, the pageHeader div is not stacked directly above the nav div.
There is some additional white space (from the background color).

 

Could anyone please help.  I seem to do fine with CSS when the navigation is
vertical in a column, but I always run into problems when the navigation is
horizontal.

 

Thank you,

Joyce

 

 


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


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

RE: [WSG] CSS Problem in Mozilla and IE6

2007-08-10 Thread Joyce Evans
Thanks so much for the information to make this appear correctly in FF 2!

 

Now if someone has a clue why the page header div won't sit right on top of
the nav div but rather splits (showing some of the white background) while
viewing in IE6, that would be great!

 

Joyce

  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ryan Moore
Sent: Friday, August 10, 2007 12:35 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] CSS Problem in Mozilla and IE6

 

In your CSS

change to this:

#nav ul {
margin: 0px 35px 0 35px;
padding: 5px 0 0 0;
text-align: center;
}

this works in FF 2 but note it has not been tested in IE.

RM

On 8/10/07, Joyce Evans [EMAIL PROTECTED] wrote:

Here is the link to a website, and I've only gotten this far:

 

http://www.nichemktghouston.com/mneiman/physician.html 

 

So far, It looks proper in IE7, but in Mozilla, the horizontal navigation
links do not center but rather move to the right so that I don't see the
full Contact link.

 

In IE 6, the pageHeader div is not stacked directly above the nav div.
There is some additional white space (from the background color).

 

Could anyone please help.  I seem to do fine with CSS when the navigation is
vertical in a column, but I always run into problems when the navigation is
horizontal.

 

Thank you,

Joyce

 

 


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



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



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

[WSG] Lower portion of lower case y does not appear in h1 in IE7

2007-08-10 Thread Joyce Evans
When I view the following link (which I'm working on) in IE7, the lower
portion of the y in the word Physician does not appear.  I see the
entire y in IE 6 and FF 2 but not in IE7.  This text is sitting within an
h1 tag within a #title tag.  Does anyone have an idea why I can't see the
lower portion of y?

 

http://www.nichemktghouston.com/mneiman/physician.html

 

Also, in the content div, I have a background image - bg_content.jpg that
has graphics to the left and to the right, and the center is simply white.
I have been told in the past that this type of background image is not a
good idea - meaning the white portion, but how could I get the left and the
right graphics to appear and repeat as more content is added, without
including the white portion of the graphic?

 

The first paragraph is actually the most important at this writing.

 

Thank you in advance.

 

Joyce

 

 

 



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

RE: [WSG] Lower portion of lower case y does not appear in h1 in IE7

2007-08-10 Thread Joyce Evans
Thank you, but I need the background image that I used in the #title tag, so
what you suggested below won't work in this situation.  It's so strange that
the lower part of the y is only missing in IE 7.  If I reduce the font size
of h1, it works, but I'd like to have the larger size if possible.  Thanks.

Joyce 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of E Michael Brandt
Sent: Friday, August 10, 2007 7:25 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Lower portion of lower case y does not appear in h1 in
IE7

 
 an h1 tag within a #title tag.  Does anyone have an idea why I can't see 
 the lower portion of y?


If you rid entirely of the title div, and its styling, and use this for 
your h1 styling, it ought to work better I think:

h1 {
background-color: #f29d0f;  
color: #fff;
text-align: right;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 1.4em;
padding: 0.2em 0.4em;
}


-- 

E. Michael Brandt

www.divaHTML.com
divaGPS : you-are-here menu highlighting
divaFAQ : FAQ pages with pizazz

www.valleywebdesigns.com
JustSo PictureWindow
JustSo PhotoAlbum

--



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





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



RE: [WSG] Lower portion of lower case y does not appear in h1 in IE7

2007-08-10 Thread Joyce Evans
Interesting - I didn't realize the operating system could affect the way IE
7 displays a web page.  I am still using Windows XP.

Joyce

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Navjot Pawera
Sent: Friday, August 10, 2007 10:01 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Lower portion of lower case y does not appear in h1 in
IE7

Hey,

*quick note*
The problem you quote here doesn't seem to exist in IE7 running in 
Windows Vista. I can see the complete y in the highlighted menu option 
Physician Services at 
http://www.nichemktghouston.com/mneiman/physician.html

--
Navjot Pawera

www.navjotpawera.com

Joyce Evans wrote:
 Thank you, but I need the background image that I used in the #title tag,
so
 what you suggested below won't work in this situation.  It's so strange
that
 the lower part of the y is only missing in IE 7.  If I reduce the font
size
 of h1, it works, but I'd like to have the larger size if possible.
Thanks.
 
 Joyce 
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of E Michael Brandt
 Sent: Friday, August 10, 2007 7:25 PM
 To: wsg@webstandardsgroup.org
 Subject: Re: [WSG] Lower portion of lower case y does not appear in h1
in
 IE7
 
  
 an h1 tag within a #title tag.  Does anyone have an idea why I can't see 
 the lower portion of y?
 
 
 If you rid entirely of the title div, and its styling, and use this for 
 your h1 styling, it ought to work better I think:
 
 h1 {
   background-color: #f29d0f;  
   color: #fff;
   text-align: right;
   font-family: Verdana, Arial, Helvetica, sans-serif;
   font-size: 1.4em;
   padding: 0.2em 0.4em;
 }
 
 



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





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



RE: [WSG] Lower portion of lower case y does not appear in h1 in IE7

2007-08-11 Thread Joyce Evans
Very nicely stated.  Unfortunately, I have not yet adjusted to the
possibility that a visitor to a site might change the text size on me.  I
need to change my way of thinking.

Thanks for the feedback.
Joyce
  
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Paul Novitski
Sent: Saturday, August 11, 2007 10:07 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Lower portion of lower case y does not appear in h1 in
IE7

At 8/10/2007 05:01 PM, Joyce Evans wrote:
When I view the following link (which I'm 
working on) in IE7, the lower portion of the y 
in the word Physician does not appear.  I see 
the entire y in IE 6 and FF 2 but not in 
IE7.  This text is sitting within an h1 tag 
within a #title tag.  Does anyone have an idea 
why I can't see the lower portion of y?

http://www.nichemktghouston.com/mneiman/physician.html

Also, in the content div, I have a background 
image - bg_content.jpg that has graphics to the 
left and to the right, and the center is simply 
white.  I have been told in the past that this 
type of background image is not a good idea - 
meaning the white portion, but how could I get 
the left and the right graphics to appear and 
repeat as more content is added, without 
including the white portion of the graphic?


Joyce,

The problem of IE7 cropping off the font 
descenders is fascinating and I look forward to 
reading an explanation.  Perhaps if you posted 
the problem to the CSS-D list you'd get an answer 
to that from the likes of Ingo Chao et al.

Part of the overall problem you're having with 
this page is that the background image is just 
35px tall so it can't accommodate text 
enlargement.  The image includes its own top  
side borders so it can't be repeated vertically 
or horizontally as the text expands:
http://www.nichemktghouston.com/mneiman/images/bg_title.jpg

You tried to suppress this problem by sizing the 
font in pixels, but of course that succeeds only 
in IE.  In other browsers the font enlarges out 
of its container and becomes not just ugly but 
also a nearly unreadable white on pale grey.

Two simple ways to change this situation are a) 
to make the background image much taller so that 
more of it will be revealed as the headline 
increases in size and b) to split the background 
image into two components: the unrepeatable top 
borders and the repeatable orange body.

Taking a step back, however, I don't see the need 
for a background image at all.  The background 
imagery consists entirely of rectlinear 
monochrome spaces and lines that can be 
reproduced exactly with background colors and 
borders.  The only complication in reproducing 
your page precisely this way is that adjacent CSS 
borders meet on a diagonal at the corner of a box 
and your top grey border butts flat on top of the 
gray side borders.  This detail can be sacrificed 
for easy layout or reproduced exactly by using an extra nested div.

Your nav menu as rendered is another sticky 
wicket, with the light  dark grey pill 
shapes.  Again you've created a fixed-height 
background that's inadequate to contain 
enlargeable text.  An easy way to start solving 
this is to make that background image quite tall 
with a light grey body and the dark grey curves 
only at the bottom, and position the background 
image in the bottom of its container.

It doesn't solve your menu's other problem which 
is that as the text enlarges the menu spills 
horizontally out of the page block.  Allowing the 
menu items to wrap around within your fixed-width 
column will keep the menu on-screen while the 
font enlarges but you'll need to re-think its 
background image.  One possibility is to use a 
segment of the light  dark grey background for 
each nav menu LI so that each menu item maintains 
its grey blobby background even as it 
wraps.  This would almost certainly require you 
to re-visualize the menu's graphic design to keep 
it looking good as text enlarges.

Regards,

Paul
__

Paul Novitski
Juniper Webcraft Ltd.
http://juniperwebcraft.com 



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





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



[WSG] W3C CSS Validation Service

2007-08-25 Thread Joyce Evans
I used to validate my XHTML at one W3C URL, and then there was another URL
where I validated my CSS style sheet(s).  It seems this has been combined so
that I can now validate both my CSS style sheet and my XHTML markup at this
URL:  http://jigsaw.w3.org/css-validator/.  I'd like to verify that this is
a correct observation on my part.

 

Also, I used to think I had to validate every single page of a website I
developed (they've all been small websites).  Today, I typed in only the URL
for the website I wanted to validate, and I received the message that no
error was found.  I'd like to verify this as well - that I only need to type
in the website's URL and not each individual page.

 

Thank you for responding to what are probably elementary questions.

 

Joyce 

 



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

RE: [WSG] W3C CSS Validation Service

2007-08-26 Thread Joyce Evans
Thanks to you and Stuart.  

Joyce 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dusan Smolnikar
Sent: Sunday, August 26, 2007 4:55 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] W3C CSS Validation Service

Css validator does not validate html. Maybe you got confused by the  
fact that you can enter a link to an html file. All it does is, it  
checks that html file for any css (inline or external) and validates  
the css. And if I recall correctly, this feature has been around for  
a while.

As Stuart noted, if your css is in external file it's always the  
same. You can only validate that once. But you still have to validate  
the html for each page separately. The html validator cannot find all  
of your pages to validate them.


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





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