W3c markup validator?

I submitted a new site that I created (my first) to the w3c validator and got 3 warnings and 1 error:
No Character Encoding Found! Falling back to UTF-8.
Unable to Determine Parse Mode!
No Character encoding declared at document level
Line 1, Column 1: end of document in prolog
The site is www.telluridegravityworks.com.
The source code view shows:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
i see charset=utf-8 referenced. Why do I get the validation warning?
The parse model warning seems to be saying that no doc type is declared. I see the doc type in the first line of the code view...?
No character encoding at document level. Is it good practice to declare this twice? Would i just repeat the same tag as above inside of the body tag?
The error about prolog says: >>This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty, and report any discrepancy.<< I don't get this. Should I be concerned or take some action regarding this?
I just typed in the site address like the link above. Should I run each individual page trhough the validator?
Thanks for any help. This is my first site and I want to be sure I haven't made any errors.

Before someone better comes along to answer this I would try including a language declaration like this:
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">

Similar Messages

W3C markup validation error.

I've been trying to determine the W3C markup validation error on http://www.kitsapwebdesign.net/business-growth/web-design/index.html The error says "non SGML character number 0 ". Apparently it's some kind of character error, but the error is not visible in the code. Does anyone have any ideas you could suggest to fix it?

Before posting here, I deleted the line 47 on other pages (with the same errors) of the website and it has no effect. Also I may point out any time I save one of the webpages (with or without changing any coding) and re-upload them the errors are gone. But has a warning "Byte-Order Mark found in UTF-8 File".
Your link (of my webpage) passed the validation, but i don't see what you did in the coding to eliminate the errors... it looks identical to the original.
Can you tell me exactly what you did so I can duplicate it so I can fix the other pages on the website?

Re: W3C Markup Validation Service ??

Am 23.03.2007 schrieb Tantale:
> I used this service
http://validator.w3.org/ to
check my webpage
>
http://www.jmrw.com/Abroad/Barcelone/index.htm
made with Dreamweaver 8.
>
> The result is 206 errors, most of them "end tag omitted,
but OMITTAG NO was
> specified.".
I don't see any errors on your page. It validates fine.
Regards
Inge Grotjahn
CatManiacs World:
http://www.gwsystems.com/inge

Are these errors reported because of some proprietary coding used on the pages that the W3C Page Validator is not equipped to evaluate?
Or, are these reported errors accurate, because the pages get messed up over time because multitudes of folks are constantly making changes, and introducing errors?
It's a little of both. It's also the result of a cost/benefit analysis by the producing bean counters, I think. If the page will display OK without taking the extra time to code properly then why do it? I would also imagine that there is quite a bit of legacy code involved.
The websites to look at are those of the folks who talk the talk....
My personal ethic and workflow prevent me from taking such a cavalier approach.

W3C Markup Validation

Can someone please help me understand what it is I need to
fix in order for my site to be W3C compliant?
W3C My site is
my site
Thank you,
Falofal

Falofal posted in macromedia.dreamweaver
> Can someone please help me understand what it is I need
to fix in
> order for my site to be W3C compliant?
http://validator.w3.org/ My
> site is
http://www.sourcelake.ca/test8/
I see you've produced valid XHTML (why XHTML?). You'll also
want to use
their CSS validator at
http://jigsaw.w3.org/css-validator/
Change:
font: "Times New Roman", Times, serif;
to:
font-family: "Times New Roman", Times, serif;
Change:
ssssbackground-color: #333;
to:
background-color: #333;
I don't know what to make of the errors in ul.MenuBarVertical
iframe in
SpryMenuBarVertical.css. They seem to be an IE hack without
actually
targeting IE in the CSS. You might be able to ignore them.
Mark A. Boyd
Keep-On-Learnin' :)

W3C CSS and Markup Validation Service

I just finished my first CSS Web site using PhotoShop, Fireworks, Flash and Dreamweaver. I did the site from the ground up, the visual way according to some tutorials I found that are uploaded at the Adobe Media Player server. The site checks out with zero errors using the CSS and Markup W3C Validation Services. The design holds together at http://browsershots.org/ in 75+ different browsers.
Just for fun, I checked out Adobe's, Apple's, Maximum PC's and Tom's Hardware Guide's homepages using W3C's Validation Services. All of these sites had between 80 and 339 errors per page tested.
Question:
Are these errors reported because of some proprietary coding used on the pages that the W3C Page Validator is not equipped to evaluate?
Or, are these reported errors accurate, because the pages get messed up over time because multitudes of folks are constantly making changes, and introducing errors?

Are these errors reported because of some proprietary coding used on the pages that the W3C Page Validator is not equipped to evaluate?
Or, are these reported errors accurate, because the pages get messed up over time because multitudes of folks are constantly making changes, and introducing errors?
It's a little of both. It's also the result of a cost/benefit analysis by the producing bean counters, I think. If the page will display OK without taking the extra time to code properly then why do it? I would also imagine that there is quite a bit of legacy code involved.
The websites to look at are those of the folks who talk the talk....
My personal ethic and workflow prevent me from taking such a cavalier approach.

Onload error in markup validator

Hi,
Not very good with code.
I have this on load error in markup validator http://validator.w3.org/check?uri=http%3A%2F%2Fwww.denotestationery.com%2Fdenote_localroot %2Fgallery.html&charset=%28detect+automatically%29&doctype=Inline&group=0
In reference to this webpage. It's coming from the Nav bar.
http://www.denotestationery.com/denote_localroot/gallery.html
My question is.... If I delete onload="" code, will it cause me any problems? (I have actually tried this on one of the nav bar images and checked on the browser, and it seems to be ok, although I have not uploaded this recent change to the remote server)

My question is.... If I delete onload="" code, will it cause me any problems? (I have actually tried this on one of the nav bar images and checked on the browser, and it seems to be ok, although I have not uploaded this recent change to the remote server)
I removed the onload event from each of those navbar items (they all have one - not just the one picked up by the validator) and the validator didn't throw an error... actually not even sure why the onload event is writen there as it is actually empty'...
If you remove the onload event, just test in all browsers and if it works, leave it out.
The option to try is to create the navbar on a new blank page and see if it write the code exactly the same - in case there was an error the first time it was done.
Just some suggested troubleshooting ideas - I never use that method to create a navbar and don't have time to even test creating one :-)

W3C CSS validator says it can't find my spry folder

I'm trying to put the finishing touches on my first site, but when I sent it through the W3C CSS validator it failed. The error message is:
File not found: http://www.smallfarming101.com/../SpryAssets/SpryMenuBarHorizontal.css: Bad Request File not found:
The Spry Assets folder is there in the public_html folder and just to be sure, I deleted the existing folder and ftp'd an updated one. Why is the validator not happY? Thanks.
http://www.smallfarming101.com

Hi,
the only thing I can imagine why W3 reports an error is this: ".. /" in your http://www.smallfarming101.com/../SpryAssets/SpryMenuBarHorizontal.css. Presumably, it is not necessary. This depends how deep your spry files are nested.
Hans-G.

W3C URL validation

I have an XHTML (Transitional) page that includes absolute
URLs to ColdFusion pages. These URLs include characters, such as
&, that the W3C won't validate unless I change the characters
to their ASCII equivalents. However, if I do this, then the URL
doesn't work.
Is there a way to validate ColdFusion URLs in W3C's
validator?
Thank you.

Why won't something like this work?
<a
href="page.cfm?cat=#rsTest.cat#&subcat=#rsTest.cat#">#rsTest.item#</a>
The & replaces the &
Ken Ford
Adobe Community Expert - Dreamweaver
Fordwebs, LLC
http://www.fordwebs.com
"Urmo5" <[email protected]> wrote in message
news:fv786p$cgm$[email protected]..
> I'm not a ColdFusion developer - so I'm not sure why our
URLs have these
> characters in them. I'll ask one of our developers.
>
> No, I wasn't aware that there is a different escaping
ASCII scheme for
> URLs.
> Is there a list of these available somewhere?
>
> Thanks for the response.
>

W3C HTML validation

I use DWmx2004, and have occasional questions about W3C HTML
validation.
I do value the help of this forum, but wonder if I should
take validation questions elsewhere?
If you think I should, can you point me to a good forum on
the subject?

Why would your questions not be appropriate here?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"smiffy47" <[email protected]> wrote in
message
news:egsreu$a46$[email protected]..
>I use DWmx2004, and have occasional questions about W3C
HTML validation.
> I do value the help of this forum, but wonder if I
should take validation
> questions elsewhere?
> If you think I should, can you point me to a good forum
on the subject?
>

W3c css validation for accordion

hi all;
it seems that the accordion widget cannot pass w3c css
validation due to some unknown css properties such as
moz-user-select, moz-user-select & possibly others.
I really care about passing the validation(my site contains a
link to the validator) and was wondering if there is a way to
replace them with a valid alternative (my preferred solution) or
maybe i can drop them if i can manually (only of the widget is not
affected by this).
any response would be great.

Hello Guys,
The Accordion has 2 Mozilla specific instructions into its
CSS:
-moz-user-select: none;
-khtml-user-select: none;
for the panel tab (SpryAccordion.css, .AccordionPanelTab,
line 54)
They are not allowing the Panel Tabs text or div selection
when the rest of the text and other in page objects may be
selected.
Indeed this behavior is not w3c standard but you may drop it
if you want. In this situation the Accordion will behave exactly as
it does on IE and when you select the text in the page you will be
able also to select the title for the panel.
Regards,
Cristian MARIN

Problems validating GL CS pages using W3C HTML Validator

I've tried validating a number of pages and they come up with approx. 30 errors and I think all of them are coming from the disjointed rollovers in the navigation. How do I get the page/pages to validate. Any help would be great.
jodmcc49

Thanks Janet,
The site is not uploaded yet. I apologize for the large amount of code. I thought it could be inserted in a code window, such as other forums. Here is the code: HTML: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
    <head>
        <meta http-equiv="content-type" content="text/html;charset=utf-8">
        <meta name="generator" content="Adobe GoLive">
        <title>Hillman Foods - Contact Us</title>
        <csactions>
            <csaction name="C773F5560" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_home.gif" urlparams="2"></csaction>
            <csaction name="C773F5CF1" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_contact_on.gif" urlparams="2"></csaction>
            <csaction name="C773F6282" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_about.gif" urlparams="2"></csaction>
            <csaction name="C773F64D3" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_contact_on.gif" urlparams="2"></csaction>
            <csaction name="C773F66F4" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_job.gif" urlparams="2"></csaction>
            <csaction name="C773F6885" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_contact_on.gif" urlparams="2"></csaction>
            <csaction name="C773F69E6" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_contact.gif" urlparams="2"></csaction>
            <csaction name="C773F6B27" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_contact_on.gif" urlparams="2"></csaction>
            <csaction name="C773F6C38" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_employee.gif" urlparams="2"></csaction>
            <csaction name="C773F6D39" class="Set Image URL" type="onevent" val0="homedefault" val1="images/location_contact_on.gif" urlparams="2"></csaction>
            <csaction name="C77B46FF10" class="Goto Link" type="onevent" val0="index.html" val1="" urlparams="1"></csaction>
            <csaction name="C77B472511" class="Goto Link" type="onevent" val0="about.html" val1="" urlparams="1"></csaction>
            <csaction name="C77B474312" class="Goto Link" type="onevent" val0="job.html" val1="" urlparams="1"></csaction>
            <csaction name="C77B477213" class="Goto Link" type="onevent" val0="contact.html" val1="" urlparams="1"></csaction>
            <csaction name="C77B479414" class="Goto Link" type="onevent" val0="employee.html" val1="" urlparams="1"></csaction>
        </csactions>
        <csscriptdict import>
            <script type="text/javascript" src="GeneratedItems/CSScriptLib.js"></script>
        </csscriptdict>
        <csactiondict>
            
            <script type="text/javascript"></script>
            
        </csactiondict>
    </head>
    <body>
        <div id="wrap">
        <div id="navigation">
            <img id="logo" src="images/logo.gif" alt="" height="165" width="388" border="0"><img src="images/location_contact_on.gif" alt="" name="homedefault" height="62" width="402" border="0"><a onclick="CSAction(new Array(/*CMP*/'C77B46FF10'));return CSClickReturn()" onmouseover="CSAction(new Array(/*CMP*/'C773F5560'));return true;" onmouseout="CSAction(new Array(/*CMP*/'C773F5CF1'));" href="#" csclick="C77B46FF10" csout="C773F5CF1" csover="C773F5560"><img id="nav_01" src="images/home.gif" alt="" height="40" width="40" border="0"></a><a onclick="CSAction(new Array(/*CMP*/'C77B472511'));return CSClickReturn()" onmouseover="CSAction(new Array(/*CMP*/'C773F6282'));return true;" onmouseout="CSAction(new Array(/*CMP*/'C773F64D3'));" href="#" csclick="C77B472511" csout="C773F64D3" csover="C773F6282"><img id="nav_02" src="images/arrow.gif" alt="" height="40" width="40" border="0"></a><a onclick="CSAction(new Array(/*CMP*/'C77B474312'));return CSClickReturn()" onmouseover="CSAction(new Array(/*CMP*/'C773F66F4'));return true;" onmouseout="CSAction(new Array(/*CMP*/'C773F6885'));" href="#" csclick="C77B474312" csout="C773F6885" csover="C773F66F4"><img id="nav_03" src="images/burger_flip.gif" alt="" height="40" width="40" border="0"></a><a onclick="CSAction(new Array(/*CMP*/'C77B477213'));return CSClickReturn()" onmouseover="CSAction(new Array(/*CMP*/'C773F69E6'));return true;" onmouseout="CSAction(new Array(/*CMP*/'C773F6B27'));" href="#" csclick="C77B477213" csout="C773F6B27" csover="C773F69E6"><img id="nav_04" src="images/envelope_on.gif" alt="" height="40" width="40" border="0"></a><a onclick="CSAction(new Array(/*CMP*/'C77B479414'));return CSClickReturn()" onmouseover="CSAction(new Array(/*CMP*/'C773F6C38'));return true;" onmouseout="CSAction(new Array(/*CMP*/'C773F6D39'));" href="#" csclick="C77B479414" csout="C773F6D39" csover="C773F6C38"><img id="nav_05" src="images/key.gif" alt="" height="40" width="40" border="0"></a></div>
        <div id="feedbackform">
            <form id="feedback" action="(EmptyReference!)" method="get" name="feedback">
                <h1>Hillman Foods Inc. Contact Us</h1>
                <label for="contacttype">Reason for contact:</label><select name="contacttype" size="1">
                    <option value="Select">Select</option>
                    <option value="General Comments">General Comments</option>
                    <option value="Compliments/Recognition">Compliments/Recognition</option>
                    <option value="Complaints">Complaints</option>
                    <option value="Suggestions">Suggestions</option>
                </select>
                <h5>Contact Information: <span class="redtext">(Please fill in all fields marked with "*")</span></h5>
            <div class="section">
                <label for="title">Title<span class="redtext">*</span>:</label><select id="title" name="title" size="1">
                    <option value="Select">Select</option>
                    <option value="Dr.">Dr.</option>
                    <option value="Rev.">Rev.</option>
                    <option value="Mr.">Mr.</option>
                    <option value="Mrs.">Mrs.</option>
                    <option value="Miss">Miss</option>
                </select> <label for="firstname">First Name <span class="redtext">*</span>:</label><input id="firstname" class="text" type="text" name="firstname" size="24"><label for="lastname">Last Name <span class="redtext">*</span>:</label><input id="lastname" class="text" type="text" name="lastname" size="24">
            </div>
            <div class="group">
            <label for="mailingaddress">Mailing Address <span class="redtext">*</span> (U.S. Only):</label><input id="mailingaddress" class="text" type="text" name="mailingaddress" size="24"><input id="mailingaddress2" class="text" type="text" name="mailingaddress2" size="24"></div>
            <div class="section">
            <label for="mailcity">City <span class="redtext">*</span>:</label><input id="mailcity" class="text" type="text" name="mailcity" size="24"><label for="mailstate">State <span class="redtext">*</span>:</label><select id="mailstate" name="mailstate" size="1">
                    <option value="Select">Select</option>
                    <option value="AL">AL</option>
                    <option value="AK">AK</option>
                    <option value="AZ">AZ</option>
                    <option value="AR">AR</option>
                    <option value="CA">CA</option>
                    <option value="CO">CO</option>
                    <option value="CT">CT</option>
                    <option value="DE">DE</option>
                    <option value="FL">FL</option>
                    <option value="GA">GA</option>
                    <option value="HI">HI</option>
                    <option value="ID">ID</option>
                    <option value="IL">IL</option>
                    <option value="IN">IN</option>
                    <option value="IA">IA</option>
                    <option value="KS">KS</option>
                    <option value="KY">KY</option>
                    <option value="LA">LA</option>
                    <option value="ME">ME</option>
                    <option value="MD">MD</option>
                    <option value="MA">MA</option>
                    <option value="MI">MI</option>
                    <option value="MN">MN</option>
                    <option value="MS">MS</option>
                    <option value="MO">MO</option>
                    <option value="MT">MT</option>
                    <option value="NE">NE</option>
                    <option value="NV">NV</option>
                    <option value="NH">NH</option>
                    <option value="NJ">NJ</option>
                    <option value="NM">NM</option>
                    <option value="NY">NY</option>
                    <option value="NC">NC</option>
                    <option value="ND">ND</option>
                    <option value="OH">OH</option>
                    <option value="OK">OK</option>
                    <option value="OR">OR</option>
                    <option value="PA">PA</option>
                    <option value="RI">RI</option>
                    <option value="SC">SC</option>
                    <option value="SD">SD</option>
                    <option value="TN">TN</option>
                    <option value="TX">TX</option>
                    <option value="UT">UT</option>
                    <option value="VT">VT</option>
                    <option value="VA">VA</option>
                    <option value="WA">WA</option>
                    <option value="WV">WV</option>
                    <option value="WI">WI</option>
                    <option value="WY">WY</option>
                </select> <label for="mailzip">Zip <span class="redtext">*</span>:</label><input id="mailzip" class="text" type="text" name="mailzip" size="24"></div>
                <div class="section">
                <label for="dayphone">Day Phone <span class="redtext">*</span>:</label><input id="dayphone" class="text" type="text" name="dayphone" size="3">-<input id="dayphone2" class="text" type="text" name="dayphone2" size="3">-<input id="dayphone3" class="text" type="text" name="dayphone3" size="4"><label for="dayphoneext">Extension:</label><input id="dayphoneext" class="text" type="text" name="dayphoneext" size="5"></div>
                <div class="section">
                <label for="eveningphone">Evening Phone <span class="redtext">*</span>:</label><input id="eveningphone" class="text" type="text" name="eveningphone" size="3">-<input id="eveningphone2" class="text" type="text" name="eveningphone2" size="3">-<input id="eveningphone3" class="text" type="text" name="eveningphone3" size="4"><label for="eveningphoneext">Extension:</label><input id="eveningphoneext" class="text" type="text" name="eveningphoneext" size="5"></div>
                <div class="section">
                <label for="timetoreach">Most convenient time/day to reach you by phone:</label><input id="timetoreach" class="text" type="text" name="timetoreach" size="24"></div>
                <div class="section">
                <label for="email">Your E-mail Address <span class="redtext">*</span>:</label><input id="email" class="text" type="text" name="email" size="24"></div>
                <div class="section">
                <label for="email2">Re-enter E-mail Address <span class="redtext">*</span>:</label><input id="email2" class="text" type="text" name="email2" size="24"></div>
                <h5>Restaurant Visited: (Please fill in all fields)</h5>
                <div class="section">
                <label for="restaddress">Address <span class="redtext">*</span>:</label><input id="restaddress" class="text" type="text" name="restaddress" size="24"></div>
                <div class="section">
                <label for="restcity">City <span class="redtext">*</span>:</label><input id="restcity" class="text" type="text" name="restcity" size="24"><label for="reststate">State <span class="redtext">*</span>:</label><select id="reststate" name="reststate" size="1">
                    <option value="Select">Select</option>
                    <option value="AL">AL</option>
                    <option value="AK">AK</option>
                    <option value="AZ">AZ</option>
                    <option value="AR">AR</option>
                    <option value="CA">CA</option>
                    <option value="CO">CO</option>
                    <option value="CT">CT</option>
                    <option value="DE">DE</option>
                    <option value="FL">FL</option>
                    <option value="GA">GA</option>
                    <option value="HI">HI</option>
                    <option value="ID">ID</option>
                    <option value="IL">IL</option>
                    <option value="IN">IN</option>
                    <option value="IA">IA</option>
                    <option value="KS">KS</option>
                    <option value="KY">KY</option>
                    <option value="LA">LA</option>
                    <option value="ME">ME</option>
                    <option value="MD">MD</option>
                    <option value="MA">MA</option>
                    <option value="MI">MI</option>
                    <option value="MN">MN</option>
                    <option value="MS">MS</option>
                    <option value="MO">MO</option>
                    <option value="MT">MT</option>
                    <option value="NE">NE</option>
                    <option value="NV">NV</option>
                    <option value="NH">NH</option>
                    <option value="NJ">NJ</option>
                    <option value="NM">NM</option>
                    <option value="NY">NY</option>
                    <option value="NC">NC</option>
                    <option value="ND">ND</option>
                    <option value="OH">OH</option>
                    <option value="OK">OK</option>
                    <option value="OR">OR</option>
                    <option value="PA">PA</option>
                    <option value="RI">RI</option>
                    <option value="SC">SC</option>
                    <option value="SD">SD</option>
                    <option value="TN">TN</option>
                    <option value="TX">TX</option>
                    <option value="UT">UT</option>
                    <option value="VT">VT</option>
                    <option value="VA">VA</option>
                    <option value="WA">WA</option>
                    <option value="WV">WV</option>
                    <option value="WI">WI</option>
                    <option value="WY">WY</option>
                </select></div>
                <div class="section">
                <label for="restlandmark">Landmark <span class="redtext">*</span> (describe location of restaurant):</label><input id="restlandmark" class="text" type="text" name="restlandmark" size="24"></div>
                <div class="section">
                <label for="incidentdate">Date/Time of Incident (Date format: mm/dd/year):</label><input id="incidentdate" class="text" type="text" name="incidentdate" size="12"><label for="incidenttime">Time <span class="redtext">*</span>:</label><select id="incidenttime" name="incidenttime" size="1">
                    <option value="Select">Select</option>
                    <option value="12:00">12:00</option>
                    <option value="12:15">12:15</option>
                    <option value="12:30">12:30</option>
                    <option value="12:45">12:45</option>
                    <option value="1:00">1:00</option>
                    <option value="1:15">1:15</option>
                    <option value="1:30">1:30</option>
                    <option value="1:45">1:45</option>
                    <option value="2:00">2:00</option>
                    <option value="2:15">2:15</option>
                    <option value="2:30">2:30</option>
                    <option value="2:45">2:45</option>
                    <option value="3:00">3:00</option>
                    <option value="3:15">3:15</option>
                    <option value="3:30">3:30</option>
                    <option value="3:45">3:45</option>
                    <option value="4:00">4:00</option>
                    <option value="4:15">4:15</option>
                    <option value="4:30">4:30</option>
                    <option value="4:45">4:45</option>
                    <option value="5:00">5:00</option>
                    <option value="5:15">5:15</option>
                    <option value="5:30">5:30</option>
                    <option value="5:45">5:45</option>
                    <option value="6:00">6:00</option>
                    <option value="6:15">6:15</option>
                    <option value="6:30">6:30</option>
                    <option value="6:45">6:45</option>
                    <option value="7:00">7:00</option>
                    <option value="7:15">7:15</option>
                    <option value="7:30">7:30</option>
                    <option value="7:45">7:45</option>
                    <option value="8:00">8:00</option>
                    <option value="8:15">8:15</option>
                    <option value="8:30">8:30</option>
                    <option value="8:45">8:45</option>
                    <option value="9:00">9:00</option>
                    <option value="9:15">9:15</option>
                    <option value="9:30">9:30</option>
                    <option value="9:45">9:45</option>
                    <option value="10:00">10:00</option>
                    <option value="10:15">10:15</option>
                    <option value="10:30">10:30</option>
                    <option value="10:45">10:45</option>
                    <option value="11:00">11:00</option>
                    <option value="11:15">11:15</option>
                    <option value="11:30">11:30</option>
                    <option value="11:45">11:45</option>
                </select><label for="incidentampm">AM/PM <span class="redtext">*</span>:</label><select id="incidentampm" name="incidentampm" size="1">
                    <option value="Select">Select</option>
                    <option value="A.M.">A.M.</option>
                    <option value="P.M.">P.M.</option>
                </select></div>
                <div class="section">
                <label for="visittype">Visit Type <span class="redtext">*</span>:<input type="radio" name="Driv-Thru" value="Drive-Thru">Drive-Thru<input type="radio" name="In-Store" value="In-Store">In-Store</label></div>
                <div class="group">
                <label for="commentinfo">Comment Information: (Please contain comments within limits of this text box</label><textarea name="commentinfo" rows="20" cols="60"></textarea></div>
                <div class="section">
                <input type="submit" name="send" value="Send"><input type="reset" name="clear" value="Clear">
            </form>
        </div>
        </div>
    </body>
</html>
CSS:
body   { font-size: small; font-family: Verdana, Arial, sans-serif; font-style: normal; font-variant: normal; font-weight: normal; margin: 0; }
* html body { font-size: x-small; /* for IE5/Win */ f\ont-size: small; /* for other IE versions */ }
h1 { font-size: 150%; }
h2 { font-size: 130%; }
h3 { font-size: 120%; }
h4 { font-size: 100%; }
ul { list-style-type: square; list-style-position: outside; margin: 0 0 0 20px; padding: 0 }
ul li    { font-size: 100%; padding-bottom: 8px }
dl dt {font-size: small; font-weight: bold;}
dl dd {padding-bottom: 8px;}
#navigation     { margin-top: 10px; margin-bottom: 15px; padding-bottom: 15px; width: 800px; border-bottom: 1px solid black }
#wrap { margin-right: auto; margin-left: auto; position: relative; width: 800px }
#navigation img#logo { margin-right: 10px; float: left; }
#navigation img#nav_01 { margin-top: 63px; margin-right: 50px; float: left; }
#navigation img#nav_02 { margin-top: 63px; margin-right: 50px; float: left; }
#navigation img#nav_03 { margin-top: 63px; margin-right: 50px; float: left; }
#navigation img#nav_04 { margin-top: 63px; margin-right: 50px; float: left; }
#navigation img#nav_05 { margin-top: 63px }
#news { margin-right: 10px; padding: 5px; width: 220px; float: left; }
#specialspromo { margin-right: 10px; padding: 5px; width: 380px; float: left; }
#video { padding: 5px; width: 179px; float: left; }
form { width: 800px; padding: 10px;}
.redtext { color: red }
.section, .group {padding-bottom: 20px;}
.section input, .section label, section select {display: inline; margin: 0 3px;}
.group input, group label, .group select, group textarea {display: block;}
#about {padding: 10px;}
.aboutaddresses   { padding-top: 10px; padding-left: 10px; width: 300px; float: left }
address { margin-top: -15px; margin-right: 10px }

W3c html validation problem

hello,
I´m developing my website and wanted him to be mobile compatible, but i got into a w3c validation error wich I´m not finding a solution.
for mobile devices, and as far as I´ve searched over the net, it is comum practice to use
<ul id="testing" selected="true">
<li id="li1">something here</li>
</ul>
the problem is w3c says ul can´t have selected as propertie, so what I wanted to ask is what can I do to make this work in comum browsers and in mobile devices?
this selected="true is needed to make javascript work, so it is a kind of variable wich is used in a if statment.
Thanks, look to read from you soon
Pluda

Thanks, I´m going to try your sample.
the goal is making noe interface who works everywhere, I tryed this on sony ericson and iphone, on mozila firefox, google chrome, safari and internet explorer (in ie it doesn´t work)
the navigation is like an iphone app, you have one list of topics, and when you click on one of them, all the content moves from right to left, revealing the correspondent list content.
Nancy O. told me I should validate in w3c, and I did, I get no errors if I remove the selected="true", but then no movement happens and nothing is revealed.
The javascript is simple, is a for in loop trought the list items, checking if selected is true or not. if true, it moves elements, otherwise it doesn´t.
I just don´t see an inteligent way of replacing the selected=true for other thing.
the example is the same you already saw in my previous post, http://www.mataborrao.com/teste the js file is in http://www.mataborrao.com/teste/js/navegacao.js

[Invalid] Markup Validation - Understanding How-to Fix

Hi, it's me again!
I am finally now getting started on the W3 validator portion of the web site making process. I put my website through it and it listed these issues below:
http://validator.w3.org/check?uri=http%3A%2F%2Frestorationacpc.com%2F&charset=%28detect+au tomatically%29&doctype=Inline&group=0
This is for this site here:
http://www.restorationacpc.com/
The problem I am having is that it is giving me errors like this:
Line 42, Column 76: character ";" not allowed in attribute specification list
… var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
How would I fix something like this without messing up the entire line of coding? I was pretty sure that the ";" would be allowed and required for something like this.
The list goes on however, picking out different characters in each line and labeling them invalid, and I do understand that there is indeed something invalid. I just need to know how to fix is without screwing up everything else like I already had done in my past attempts.
Any and all help is appreciated, as always!

Nevermind, I see what you mean, I wrapped the javascript that is was marking as errored in CDATA. The rest of the errors can actually be fixed by simple cleaning of the code.
Thanks again for the help!

Third Eye Needed {W3C HtML Validation}

I am trying to clean up my HTML 17 errors but most are caused by the same error. I have tried everything before posting this. To me it looks like the validation is telling me to enter a space but done that and same error. I also tried inserting the recomended "<" never worked Would appreciate someone having a look as I am keen to clean up the code.
Thank you
Mark

Doing what SnakeEyze suggested should fix it...
Add the closing quote mark before the closing tag.
height="100"

Problems producing W3C-valid template-built pages

Folks:
DW CS3 on Intel Mac
CMX Design-Time Extension
I would like my site to pass the W3C markup validator,
http://validator.w3.org/.
My site design is straightforward: I've got a single
custom-built template page, "index.php" for the layout of my site.
There's no content in this file. The header of this file contains a
link to my site's single master CSS style-sheet.
All content comes from one of over 100 html "contact-chunk"
files, each of which contains only "bare" HTML, no header or
trailer material at all, no <!DOCTYPE...> nor <html>
... <head> ... </head> ... <body> ..
</body> stuff at all. One of these contact-chunk files is
included at each page-load. The details are not important.
Wait, I lied: Each of those contact-chunk files contains a
bare link to the site's master CSS style-sheet, like this:
<link href="/TheMasterStyleSheet.css" rel="stylesheet"
type="text/css">
"Bare", meaning NOT enclosed by <head> ...
</head> or anything else. DW requires just the link so it can
detect the site-wide style-sheet and let me apply styles from it to
the "content-chunk" files.
When complete pages are served to clients, that extra link
would ordinarily mean the browser would see two different external
style-sheet links from the composite page at load-time, which is is
not allowed. This is in fact flagged as an error by W3C validator.
There is no sense in giving browsers known-invalid code! It
makes total sense to me that links to external styles-sheets need
to occur just once,in the header of such composites as they are
seen by browsers. It also makes sense to me that the contact chunk
files could not contain <html> ... <head> ...
</head> ... <body> .. </body> tags because these
would be nested within the <body>... </body? structure in
the template page. Confusion!
Thanks to the DW designers, there's a way to avoid sending
the second style-sheet link: DW's Design-Time Style-Sheet mechanism
allows me declare specific style-sheet links as Design-Time ONLY;
the specified links are stripped before the files are uploaded. DW
CS3 supports only page-by-page declarations, But with the
minimal-cost "CMX Design-time" extension (
http://www.communitymx.com/abstract.cfm?CID=61265)
added, I can make these declarations on a site-wide basis. Cool!
All the above seems quite reasonable and how-it-must-be for
template-include designs. However,I have found two problems:
1. The Design-Time Style Sheet Mechanism works unpredictably
When I tell the CMX Design-time Extension to exclude my
master CSS style-sheet link from all .html files, site-wide, it
apparently does what it is required to make this happen: it creates
.mno files in _notes folders corresponding to all .html files in
the source tree. (The only files with .html extensions in my source
tree are such content-chunk files.) Without the extension, I'd end
up with identical files after manually applying Text--> CSS
Styles -->Design-Time individually to all the content-chunk
files.
I did have some successful test runs on individual content
chunk files, so I know the Design-Time Mechanism is fundamentally
sound.
Yes, I am certain I re-PUT all the .html files to the server
to allow the specified CSS link in each to be stripped. There is
only one external style-sheet, and I'm certain I specified that
one. Yes, I looked in the DW and extension documentation for
additional information.
2. This Design-Time Style Sheet mechanism is completely
ineffective for embedded styles in content-chunk files..
I think embedded styles are completely legal, and make
perfect sense when particular styles are needed only for one source
file. A few of my contact-chunk files contain these.
My questions:
Question 1: How to assure that the DW Design-Time mechanism
is activated and works consistently? Or how to debug it? What
exactly should appear in the _notes/*.mno files?
Question 2: Assuming both my development machine and the
server are running Unix, is there any downside to picking a
distinctive extension for content-chunk files? Any standard? How
about ".ihtml" e.g., "foo.ihtml"?
Question 3: Is there any alternative that preserves embedded
styles in my design? (I think it is inevitable that I'll need to
move my local styles to the master CSS style-sheet or use in-line
styles. I'm just checking in case I've missed a clever
alternative.)
Question 4: I'm doing a lot of work to make this design work
with site-wide CSS, and each time I solve one issue, another one
pops up. In my experience, that pattern either means I'm trying to
use a subtle, complex mechanism, which simply takes a while to get
right. Or that I've committed a fundamental design error, and
there's possibly a much easier way to accomplish the same result.
Which?
TIA,
Henry
TIA,
Henry

> "Bare", meaning NOT enclosed by <head> ...
</head> or anything else.
> DW
> requires just the link so it can detect the site-wide
style-sheet and let
> me
> apply styles from it to the "content-chunk" files.
Won't work. The chunks are going in the body. Links to
stylesheets in the
body are invalid HTML and ignored by the browsers.
> When complete pages are served to clients, that extra
link would
> ordinarily
> mean the browser would see two different external
style-sheet links from
> the
> composite page at load-time, which is is not allowed.
This is in fact
> flagged
> as an error by W3C validator.
This makes no sense. A page can have oodles of links to
external
stylesheets, but they must all be in the head of the page.
> 1. The Design-Time Style Sheet Mechanism works
unpredictably
Perhaps it's more accurate to say that the CMX extension
works unpredictably
with DT Stylesheets. I've never seen an instance of DT
stylesheets failing,
either in my hands or in anyone else's. Your report is the
first. I think
CMX will have to help you with this one.
> 2. This Design-Time Style Sheet mechanism is completely
ineffective for
> embedded styles in content-chunk files..
>
> I think embedded styles are completely legal, and make
perfect sense when
> particular styles are needed only for one source file. A
few of my
> contact-chunk files contain these.
Nope - embedded styles are illegal in this sense.
> Question 2: Assuming both my development machine and the
server are
> running
> Unix, is there any downside to picking a distinctive
extension for
> content-chunk files? Any standard? How about ".ihtml"
e.g.,
> "foo.ihtml"?
Nope. You could use 'monkeybutt' if you wanted. However, if
you want DW
to recognize that extension as containing HTML code you would
need to
'register' it with DW -
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_16410&sliceId=1
> Question 3: Is there any alternative that preserves
embedded styles in my
> design? (I think it is inevitable that I'll need to move
my local styles
> to
> the master CSS style-sheet or use in-line styles. I'm
just checking in
> case
> I've missed a clever alternative.)
Yes, you can give each "chunk" chunk-specific container
names, and place the
desired chunk-specific CSS selectors in the parent CSS.
> Question 4: I'm doing a lot of work to make this design
work with
> site-wide
> CSS, and each time I solve one issue, another one pops
up. In my
> experience,
> that pattern either means I'm trying to use a subtle,
complex mechanism,
> which
> simply takes a while to get right. Or that I've
committed a fundamental
> design
> error, and there's possibly a much easier way to
accomplish the same
> result.
> Which?
The latter, I believe.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"hen3ry" <[email protected]> wrote in
message
news:[email protected]...
> Folks:
>
> DW CS3 on Intel Mac
> CMX Design-Time Extension
>
> I would like my site to pass the W3C markup validator,
>
http://validator.w3.org/.
>
> My site design is straightforward: I've got a single
custom-built
> template
> page, "index.php" for the layout of my site. There's no
content in this
> file.
> The header of this file contains a link to my site's
single master CSS
> style-sheet.
>
> All content comes from one of over 100 html
"contact-chunk" files, each of
> which contains only "bare" HTML, no header or trailer
material at all, no
> <!DOCTYPE...> nor <html> ... <head>
... </head> ... <body> .. </body>
> stuff
> at all. One of these contact-chunk files is included at
each page-load.
> The
> details are not important.
>
> Wait, I lied: Each of those contact-chunk files contains
a bare link to
> the
> site's master CSS style-sheet, like this:
>
> <link href="/TheMasterStyleSheet.css"
rel="stylesheet"
> type="text/css">
>
> "Bare", meaning NOT enclosed by <head> ...
</head> or anything else.
> DW
> requires just the link so it can detect the site-wide
style-sheet and let
> me
> apply styles from it to the "content-chunk" files.
>
> When complete pages are served to clients, that extra
link would
> ordinarily
> mean the browser would see two different external
style-sheet links from
> the
> composite page at load-time, which is is not allowed.
This is in fact
> flagged
> as an error by W3C validator.
>
> There is no sense in giving browsers known-invalid code!
It makes total
> sense to me that links to external styles-sheets need to
occur just
> once,in the
> header of such composites as they are seen by browsers.
It also makes
> sense
> to me that the contact chunk files could not contain
<html> ... <head> ...
> </head> ... <body> .. </body> tags
because these would be nested within
> the
> <body>... </body? structure in the template
page. Confusion!
>
> Thanks to the DW designers, there's a way to avoid
sending the second
> style-sheet link: DW's Design-Time Style-Sheet mechanism
allows me
> declare
> specific style-sheet links as Design-Time ONLY; the
specified links are
> stripped before the files are uploaded. DW CS3 supports
only page-by-page
> declarations, But with the minimal-cost "CMX
Design-time" extension
> (
http://www.communitymx.com/abstract.cfm?CID=61265)
added, I can make
> these
> declarations on a site-wide basis. Cool!
>
> All the above seems quite reasonable and how-it-must-be
for
> template-include
> designs. However,I have found two problems:
>
> 1. The Design-Time Style Sheet Mechanism works
unpredictably
>
> When I tell the CMX Design-time Extension to exclude my
master CSS
> style-sheet link from all .html files, site-wide, it
apparently does what
> it is
> required to make this happen: it creates .mno files in
_notes folders
> corresponding to all .html files in the source tree.
(The only files with
> .html extensions in my source tree are such
content-chunk files.) Without
> the
> extension, I'd end up with identical files after
manually applying Text-->
> CSS
> Styles -->Design-Time individually to all the
content-chunk files.
>
> I did have some successful test runs on individual
content chunk files, so
> I
> know the Design-Time Mechanism is fundamentally sound.
>
> Yes, I am certain I re-PUT all the .html files to the
server to allow the
> specified CSS link in each to be stripped. There is only
one external
> style-sheet, and I'm certain I specified that one. Yes,
I looked in the DW
> and
> extension documentation for additional information.
>
>
> 2. This Design-Time Style Sheet mechanism is completely
ineffective for
> embedded styles in content-chunk files..
>
> I think embedded styles are completely legal, and make
perfect sense when
> particular styles are needed only for one source file. A
few of my
> contact-chunk files contain these.
>
> My questions:
>
> Question 1: How to assure that the DW Design-Time
mechanism is activated
> and
> works consistently? Or how to debug it? What exactly
should appear in
> the
> _notes/*.mno files?
>
> Question 2: Assuming both my development machine and the
server are
> running
> Unix, is there any downside to picking a distinctive
extension for
> content-chunk files? Any standard? How about ".ihtml"
e.g.,
> "foo.ihtml"?
>
> Question 3: Is there any alternative that preserves
embedded styles in my
> design? (I think it is inevitable that I'll need to move
my local styles
> to
> the master CSS style-sheet or use in-line styles. I'm
just checking in
> case
> I've missed a clever alternative.)
>
> Question 4: I'm doing a lot of work to make this design
work with
> site-wide
> CSS, and each time I solve one issue, another one pops
up. In my
> experience,
> that pattern either means I'm trying to use a subtle,
complex mechanism,
> which
> simply takes a while to get right. Or that I've
committed a fundamental
> design
> error, and there's possibly a much easier way to
accomplish the same
> result.
> Which?
>
> TIA,
>
> Henry
>
> TIA,
>
> Henry
>
>

W3c markup validator?

Similar Messages

Maybe you are looking for