I'm not Marvin. Wrong email. On Mon, Jan 18, 2010 at 4:46 PM, Russ Weakley <r...@maxdesign.com.au> wrote:
> Hi Marvin, > > I've placed two valid examples online for you to check (will stay online > for next 10 days or so only): > > HTML: <http://maxdesign.com.au/jobs/marvin.htm> > CSS: <http://maxdesign.com.au/jobs/marvin.css> > > Can you test these valid files and see if IE8 lets you hear/see the > headings that were causing you issues? > > Some notes on your files: > > --------- > CSS issues > --------- > > In both errors you have used: > > background-color: left; > > The value of "left" is not allowed (it also does not make sense as you are > trying to apply a colour). > > The allowed values include "transparent", "inherit" and the various colour > options. The options are: > > Option 1: Color keyword values > > Example: p { color: black; } > > CSS 2.1 color keyword values must only include: aqua, black, blue, fuchsia, > gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, > and yellow. > > More here: > <http://www.w3.org/TR/CSS21/syndata.html#color-units> > > Option 2: Hexidecimal values > > Hexadecimal values use a '#' immediately followed by either three or six > hexadecimal characters. The three-digit RGB notation (#rgb) is converted > into six-digit form (#rrggbb) by replicating digits, not by adding zeros. > > Example 1: p { color: #f00; } with three number value or > Example 2: p { color: #ff0000; } with siz number value > > Option 3: Functional notation values > > Functional notation values use rgb(' followed by a comma-separated list of > three numerical values (either three integer values or three percentage > values) followed by ')'. > > Example 1: p { color: rgb(255,255,255); } with three numeric values > Example 2: p { color: rgb(100%, 100%, 100%); } with three percentage values > > --------- > HTML issues > --------- > > Many of your issues are associated with the use of the BR element and can > be resolved by replacing <br> with <br />. > > The BR element is considered an "empty" or "self closing element". When > using XHTML (you are using XHTML 1.0 Transitional) self closing elements > should include a trailing slash: <br /> > > You have also placed several BR elements inside a UL element. This is not > allowed. The only items that can be placed inside a UL element are LI > elements. > > More here: > <http://www.w3.org/TR/html4/struct/lists.html#edef-UL> > > You have the following paragraph with no closing paragraph element near the > end of your document: > > <p style="clear:both;"> > > Finally, your email address markup includes a subject "hack": > > mailto:i...@joes.com.au?subject=joe's Website Query > > If nothing else, the subject needs to be correctly encoded so all spaces > are replaced with "20%". > > Example: > > mailto:i...@joes.com.au?subject=joe's%20Website%20Query" > > Read more on this here: > <http://www.blooberry.com/indexdot/html/topics/urlencoding.htm> > > Regardless, this solution for email subjects is a far from ideal. > > Read more on this here: > <http://www.sightspecific.com/~mosh/WWW_FAQ/mailsubj.html<http://www.sightspecific.com/%7Emosh/WWW_FAQ/mailsubj.html> > > > < > http://shadow2531.com/opera/testcases/mailto/modern_mailto_uri_scheme.html > > > > Final notes: > > 1. There are a range of cases where you have used BR elements where they > are probably not needed. The same could easily be achieved using CSS by > applying additional padding on one of the vertically adjacent elements. > > 2. Similarly, you have used the HR element in several instances and this > could also be achieved using CSS by applying padding and borders to > vertically adjacent elements. Not essential, but worth considering. > > 3. There are several instances where you have used a DIV or PARAGRAPH with > the single purpose of clearing other content. Again, this could easily have > been achieved by applying the CLEAR property to one of the existing > following elements. > > 4. Finally, in two instances, you have used the TARGET attribute within an > ANCHOR element - target="_top". There have been many discussions on this > about this on the WSG list in the past. Rather than get bogged down in this > again, two simple points: > - this is not ideal as it not valid for XHTML 1.0 Strict (even though it is > acceptable in your case it is a good practice to move towards strict) > - leave these out and let the user control their experience! > > Thanks > Russ > > > On 19/01/2010, at 10:04 AM, Marvin Hunkin wrote: > > hi. >> what do you mean vallidate the css and the pages. >> did do that a while back and it vallidated all. >> > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > PR: wait... <javascript:{}> I: wait... <javascript:{}> L: wait...<javascript:{}> LD: wait... <javascript:{}> I: wait... <javascript:{}>wait... <javascript:{}> Rank: wait... <javascript:{}> Traffic: wait... <javascript:{}> Price: wait...<javascript:{}> C: wait... <javascript:{}> ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
