RE: [WSG] FINAL VERSION OF MY SITE

2010-02-04 Thread Elizabeth Spiegel
Hi Marvin

Other people have commented on your code; I'll just add a few points on the
content.

Copyright page: the likelihood of the AFP prosecuting someone for breach of
copyright is minuscule (particularly where we're talking about the content
on a commercial site). Just state that the material is copyright; no
unauthorised reproduction allowed etc.  My own site says: All text and
images on the site are C Elizabeth Spiegel, 2005-2009; all rights reserved.
You may link to any page on this site, on condition that it is not framed to
give the impression that it belongs to or is associated with your own site,
business or organisation. [note to self - must update the date range!]  The
statement that 'This information is accurate at this current time' is
meaningless without an indication of when it was written/updated - I would
omit it altogether. 

On the other hand, on produce.html, the date the page was updated is very
important: I don't want to turn up at Joe's to take advantage of his cheap
carrots, only to discover that the price hasn't been updated in months. Also
on this page you have oranges at $1.49kg per kg - lose the first kg.

Make and document decisions about details like capitalisation and
punctuation. It's less a matter of there being a right way (although there
are any number of style guides around) than one of using a consistent
approach. Most authorities these days tend to lean towards minimal caps and
punctuation (so Pty Ltd, not PTY. LTD.) On your list of Today's specials,
for example, mushrooms are $3.99 / kg. while strawberries are $2.99 a
Punnet. and tomatoes are $7.99 a tray. Decide whether or not to use
spaces either side of the slash, a period after kg, and whether to
capitalise both trays and punnets, or neither.

I would probably have combined the History and Staff pages into an About us
(or About Joe's) page. I'd also combine the Fruit and vegetable links and
Fruit and vegetable recipes pages into a single page (after all, they're
both lists of links). 

Overall, a pleasant and easy-to-use site.


Elizabeth Spiegel
Web editing

0409 986 158
GPO Box 729, Hobart TAS 7001
www.spiegelweb.com.au




 -Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On
Behalf Of Marvin Hunkin
Sent: Thursday, 4 February 2010 9:47 AM
To: WSG@WEBSTANDARDSGROUP.ORG
Subject: [WSG] FINAL VERSION OF MY SITE

HI.
CAN SOME ONE TAKE A FINAL LOOK AT THIS SITE.
AND GOT 2 FONTS.
ONE VERDANA AND ONE Arial black.
do i need any other fonts.
and does it look really good?
and also any other improvements.
let me know.
and if i need to make any changes.
tell me how to do this.
marvin.

http://www.raulferrer.com/joe/html/ 




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] CSS Validation Error

2010-02-04 Thread David Dorward
 
On 4 Feb 2010, at 07:42, Joshua Street wrote:
 The validator does correctly parse as per the spec. The spec defines a way 
 for vendor prefixes to exist without conflicting with anything in CSS, no 
 more. This makes them part of the grammar, not the vocabulary, and the 
 validator checks both. The CSS 2.1 specification says Authors should avoid 
 vendor-specific extensions.
 
 I agree vendor-specific extensions do not constitute acceptable
 vocabulary, but as the specification allows a grammatical means for
 their inclusion it seems counter-productive to flag them as errors.

It provides a means for vendors to experiment without conflicting with real 
CSS, and for authors to *test* those features.

 The specification assures authors and vendors that An initial dash or
 underscore is guaranteed never to be used in a property or keyword by
 any current or future level of CSS - and, accordingly, they are (and
 will remain) grammatically permissible / safe for use. The imperative
 to avoid these extensions lacks explanation and, while this list is
 (by virtue of our name!) perhaps not the place for such views, seems
 to stem from the desire to preserve the appearance of standardisation
 rather than maximising the utility and flexibility of the standard in
 question.

The appearance of standardisation? The whole point of vendor extensions is that 
they are non-standard. Some of them are experimental implementations of 
standard features, some of them are experimental implementations of proposed 
features which may appear in future standards, some of them are outright 
proprietary. They are not standard.

 As a counterpoint to this, of course, using standards-compliant
 techniques to achieve an outcome will more successfully preserve
 interoperability into the future. However, I would assert the advice
 to avoid vendor-specific extensions should be constrained by this,
 rather than suggesting that a guaranteed future-compatible (albeit
 potentially no longer functional, contingent on ongoing vendor
 support) identifier should be avoided unswervingly.

They aren't guaranteed future-compatible. 

Vendor: We propose this feature and have implemented this as -vendor-foo

Other Vendor: Well, it has these problems, what if ...

Vendor: OK. We've changed the way it works.

All the slightly older clients supporting the original implementation promptly 
break.


How would this be implemented anyway?

Anything that looks like a vendor prefix works?

-moz-bowder-wadius: 

Congratulations! It is valid! 

But why doesn't it work?

Or does someone try to maintain a list of all the different extensions? The CSS 
2.1 specification lists 12 known vendors who use the vendor prefix. Who is 
going to maintain a central list of all proprietary extensions and the values 
they accept? How would they be versioned?


-- 
David Dorward
http://dorward.me.uk



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] CSS off button

2010-02-04 Thread Erickson, Kevin (DOE)
Thanks Jayachandran!
 
That definitely works but is there a way that it could keep the CSS off
when the visitor leaves the page? Using a cookie maybe?
Here is the page using your example:
http://www.doetest.vi.virginia.gov/z_testing_area/kevin/test-css-off-fro
m-wsg2.shtml
 
Thank you,
Kevin



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Jayachandran Kandasamy
Sent: Wednesday, January 27, 2010 2:25 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] CSS off button


Hi Kevin,
 
I have tried some sample code for switching off the CSS in jQuery.
 
Please go through this code below and let me know how far it is helping
you - if need anyother assistance please reply 
 
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
HTML
HEAD
TITLE New Document /TITLE
META NAME=Generator CONTENT=EditPlus
META NAME=Author CONTENT=
META NAME=Keywords CONTENT=
META NAME=Description CONTENT=
script src=http://code.jquery.com/jquery-latest.js;/script
http://code.jquery.com/jquery-latest.js%22%3E%3C/script 
link href=css/sample.css type=text/css rel=stylesheet/
style type=text/css
body {
 background-color: #acc;
 color: #fff;
 font-size: 25px;
}
/style
style type=text/css
.chumma {
 background-color: #ff9900;
 color: #123456;
 font-size: 30px;
 width: 500px;
 height: 500px;
}
/style
script type=text/javascript
 $(document).ready(function(){
  $(input.offButt).click(function() {
   if($(head:has(style))  $(head:has(link))){
$(head:has(style)).remove();
$(head:has(link)).remove();
   }
  });
 });
/script
/HEAD
BODY
Sample for CSS off
form name=sampleForm
input type=button value=Click to Off the CSS class=offButt
id=offButt /
div class=chummaHi Kevin/div
div class=nameWebsite group - Kevin/div
/form
/BODY
/HTML

Thanks,
JC

On Fri, Jan 22, 2010 at 12:22 PM, Erickson, Kevin (DOE)
kevin.erick...@doe.virginia.gov wrote:


Hello fellow WSG'ers.
 
Could anyone please tell me if there is a right way to put a
clickable button in a web page that will turn off all CSS?
 
Thanks,
Kevin


***
List Guidelines:
http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org

*** 



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*** 


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


RE: [WSG] CSS off button

2010-02-04 Thread Erickson, Kevin (DOE)
Sorry. That question wasn't very clear. I meant when the visitor goes to
other pages on the site I would like the CSS to remain off using a
cookie. Do you have a way to do that?



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Erickson, Kevin (DOE)
Sent: Thursday, February 04, 2010 1:44 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] CSS off button


Thanks Jayachandran!
 
That definitely works but is there a way that it could keep the CSS off
when the visitor leaves the page? Using a cookie maybe?
Here is the page using your example:
http://www.doetest.vi.virginia.gov/z_testing_area/kevin/test-css-off-fro
m-wsg2.shtml
 
Thank you,
Kevin



From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Jayachandran Kandasamy
Sent: Wednesday, January 27, 2010 2:25 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] CSS off button


Hi Kevin,
 
I have tried some sample code for switching off the CSS in jQuery.
 
Please go through this code below and let me know how far it is helping
you - if need anyother assistance please reply 
 
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
HTML
HEAD
TITLE New Document /TITLE
META NAME=Generator CONTENT=EditPlus
META NAME=Author CONTENT=
META NAME=Keywords CONTENT=
META NAME=Description CONTENT=
script src=http://code.jquery.com/jquery-latest.js;/script
http://code.jquery.com/jquery-latest.js%22%3E%3C/script 
link href=css/sample.css type=text/css rel=stylesheet/
style type=text/css
body {
 background-color: #acc;
 color: #fff;
 font-size: 25px;
}
/style
style type=text/css
.chumma {
 background-color: #ff9900;
 color: #123456;
 font-size: 30px;
 width: 500px;
 height: 500px;
}
/style
script type=text/javascript
 $(document).ready(function(){
  $(input.offButt).click(function() {
   if($(head:has(style))  $(head:has(link))){
$(head:has(style)).remove();
$(head:has(link)).remove();
   }
  });
 });
/script
/HEAD
BODY
Sample for CSS off
form name=sampleForm
input type=button value=Click to Off the CSS class=offButt
id=offButt /
div class=chummaHi Kevin/div
div class=nameWebsite group - Kevin/div
/form
/BODY
/HTML

Thanks,
JC

On Fri, Jan 22, 2010 at 12:22 PM, Erickson, Kevin (DOE)
kevin.erick...@doe.virginia.gov wrote:


Hello fellow WSG'ers.
 
Could anyone please tell me if there is a right way to put a
clickable button in a web page that will turn off all CSS?
 
Thanks,
Kevin


***
List Guidelines:
http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org

*** 



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*** 
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*** 


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


Re: [WSG] CSS Validation Error

2010-02-04 Thread James Ellis
Hi

I guess it's understand the consequences and use at your own risk. I doubt a
vendor will change the spelling and if they do, I'm pretty sure they'd
maintain BC by allowing both to work.
Using the example of *-radius, the vendor differences are more to do with
what the values selected will render as rather than the naming, for instance
webkit allows elliptical curves while moz only allows regular curves:
http://www.css3.info/border-radius-apple-vs-mozilla/
Apparently, webkit more closely resembles the CSS3 spec. Mozilla may change
their interpretation leading to possibly unexpected results (which you can
then fix).

Opera is apparently going to be supporting 'border-radius' in an upcoming
Presto release.

The end-goal is for all the major browsers to switch to border-radius and
then ignore their vendor specifc version, to avoid conflicts.

There are plenty of options to create curve-edged boxes but the CSS method
is the easiest programatically to implement, followed by creating PNG
quadrants on the fly with Imagick or similar and positioning them using CSS.
Opera allows SVG backgrounds,
so they can be created on-the-fly as XML. Plenty of designers cap a box top
and bottom with two curved slices but that's a pain to implement in flexible
layouts.

To answer a question further back, yes border-radius should be last in the
list after the vendor extensions.

Cheers
James



 They aren't guaranteed future-compatible.

 Vendor: We propose this feature and have implemented this as -vendor-foo

 Other Vendor: Well, it has these problems, what if ...

 Vendor: OK. We've changed the way it works.

 All the slightly older clients supporting the original implementation
 promptly break.


 How would this be implemented anyway?

 Anything that looks like a vendor prefix works?

 -moz-bowder-wadius:

 Congratulations! It is valid!

 But why doesn't it work?

 Or does someone try to maintain a list of all the different extensions? The
 CSS 2.1 specification lists 12 known vendors who use the vendor prefix. Who
 is going to maintain a central list of all proprietary extensions and the
 values they accept? How would they be versioned?




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] CSS off button

2010-02-04 Thread Jayachandran Kandasamy
Hi Kevin,

I will let you know about the cookie technique soon :)

On Thu, Feb 4, 2010 at 10:43 AM, Erickson, Kevin (DOE) 
kevin.erick...@doe.virginia.gov wrote:

  Thanks Jayachandran!

 That definitely works but is there a way that it could keep the CSS off
 when the visitor leaves the page? Using a cookie maybe?
 Here is the page using your example:
 http://www.doetest.vi.virginia.gov/z_testing_area/kevin/test-css-off-from-wsg2.shtml

 Thank you,
 Kevin

  --
 *From:* li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] *On
 Behalf Of *Jayachandran Kandasamy
 *Sent:* Wednesday, January 27, 2010 2:25 AM

 *To:* wsg@webstandardsgroup.org
 *Subject:* Re: [WSG] CSS off button

   Hi Kevin,

 I have tried some sample code for switching off the CSS in jQuery.

 Please go through this code below and let me know how far it is helping you
 - if need anyother assistance please reply

 !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
 HTML
 HEAD
 TITLE New Document /TITLE
 META NAME=Generator CONTENT=EditPlus
 META NAME=Author CONTENT=
 META NAME=Keywords CONTENT=
 META NAME=Description CONTENT=
 script 
 src=http://code.jquery.com/jquery-latest.js;/scripthttp://code.jquery.com/jquery-latest.js%22%3E%3C/script
 
 link href=css/sample.css type=text/css rel=stylesheet/
 style type=text/css
 body {
  background-color: #acc;
  color: #fff;
  font-size: 25px;
   }
 /style
 style type=text/css
 .chumma {
  background-color: #ff9900;
  color: #123456;
  font-size: 30px;
  width: 500px;
  height: 500px;
 }
 /style
 script type=text/javascript
  $(document).ready(function(){
   $(input.offButt).click(function() {
if($(head:has(style))  $(head:has(link))){
 $(head:has(style)).remove();
 $(head:has(link)).remove();
}
   });
  });
 /script
 /HEAD
  BODY
 Sample for CSS off
 form name=sampleForm
 input type=button value=Click to Off the CSS class=offButt
 id=offButt /
 div class=chummaHi Kevin/div
 div class=nameWebsite group - Kevin/div
 /form
 /BODY
 /HTML
 Thanks,
 JC
  On Fri, Jan 22, 2010 at 12:22 PM, Erickson, Kevin (DOE) 
 kevin.erick...@doe.virginia.gov wrote:

  Hello fellow WSG'ers.

 Could anyone please tell me if there is a right way to put a clickable
 button in a web page that will turn off all CSS?

 Thanks,
 Kevin

 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***



 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***

 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

RE: [WSG] CSS off button

2010-02-04 Thread Paul Novitski

At 2/4/2010 10:43 AM, Erickson, Kevin (DOE) wrote:
Here is the page using your example: 
http://www.doetest.vi.virginia.gov/z_testing_area/kevin/test-css-off-from-wsg2.shtmlhttp://www.doetest.vi.virginia.gov/z_testing_area/kevin/test-css-off-from-wsg2.shtml



I recommend that you give folks a corresponding button to turn 
styling back on after they switch it off.


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: memberh...@webstandardsgroup.org
***



[WSG] ie8 not rendering contact form in compatibility mode

2010-02-04 Thread Craig Jones


Hi all,
I am having trouble with a contact form not displaying on a clients 
computer.

They are running ie8 and the form displays then immediately disappears.
I have given the table a class and CSS but still no luck. It appears to 
work in all other browsers.

http://www.gamlinroofing.com.au/contact.php
Any fix would be greatly appreciated.
Craig
cr...@designawebnoosa.com.au



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] ie8 not rendering contact form in compatibility mode

2010-02-04 Thread Kepler Gelotte
 I am having trouble with a contact form not displaying on a clients 
 computer.

It appears to happen in IE8 in compatibility mode or IE7. I get a
javascript error:

Unexpected call to method or property access: swfobject.modified.js line 69
character 190

Try commenting this script out and see if the contact form stays put. If
that keeps the form from disappearing, then my guess is you need to debug
the javascript.

Best regards,

Kepler Gelotte
Neighbor Webmaster, Inc.
156 Normandy Dr., Piscataway, NJ 08854
www.neighborwebmaster.com
phone/fax: (732) 302-0904




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***