XHTML validation trouble

Hi guys,
I'm a having a little trouble getting my site XHTM
Transitional validated.
Im getting about 50 errors using W3's HTML validator.
I don't understand how Dreamweaver allows so many errors and
they don't show up and it's in built validator?
I've got all the settings switched to XHTML etc.
Any ideas how i can sort this? Is there no quick solution?
Thanks

Actually, I find the DW validator to be a reasonable
first-order
approximation, but I'm so accustomed to the W3 one, that I
usually go there
first.
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
==================
"PeteC" <[email protected]> wrote in
message
news:ed48vd$s7p$[email protected]..
> RookOrn wrote:
>> Im getting about 50 errors using W3's HTML
validator.
>>
>> I don't understand how Dreamweaver allows so many
errors and they
>> don't show up and it's in built validator?
>
> The DW validator is useless (IMHO). I rely on the W3C
validator - but
> remember that it's only valid if the CSS passes as well.
>
> A URL will be a good start to working out these 50
errors...
>
> Regards,
>
> Pete.
> --
> Peter Connolly
>
http://www.acutecomputing.co.uk
> Derby
> UK
> Skype ID: acutecomputing
>

Similar Messages

XHTML Validation and Accessibility

We've recently completed developing some Application Express systems for a customer, and they were disappointed the pages did not pass W3C XHTML validation to meet their accessibility targets.
I've had the chance to do a bit of a post-mortem and nailed some issues that were down to our templates. I've also noted some previous threads here (notably Re: Validation!!! and Re: HTML DB and Accessibility (AA-Compliance) and look forward to resolution of markup validation issues in future releases. In the meantime, here are the most frequent problems we encountered. I'd appreciate any explanations, and any suggestions on how to improve matters in the short term.
INVALID ENTITIES
The majority of the validation errors are like:
Cannot generate system identifier for general entity "p_fname"
General entity "p_fname" not defined and no default entity
Reference not terminated by REFC delimiter
Reference to external entity in attribute value
Reference to entity "p_fname" for which no system identifier could be generated
Entity was defined here
Where the App Ex engine is generating internal URLs and not escaping ampersands, that are then interpreted by the validator as forming part of an entity. This isn't disastrous, but an early fix in a future release would be welcome as it would reduce the number of errors and make it easier to spot any arising from invalid template code.
Am I right in thinking that storing CSS, images and scripts externally to App Ex would eliminate this?
STANDARD HTML BUTTONS
All "HTML Buttons" result in:
Value of attribute "type" cannot be "BUTTON"; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
There is no attribute "onClick"
End tag for "input" omitted, but OMITTAG NO was specified
Where the engine is generating an attribute value in uppercase and attribute names in camel-hump case instead of all lowercase. We can work round this by creating an "HTML Button" template with valid attributes and values.
ITEM LABEL
Reference to non-existent ID "P1_DATASET_CATEGORIES"
Where the label is the overall label for a checkbox item with multiple checkboxes, all of which have their own valid label. Should the engine include the checkbox item as a hidden item? Can we work round this by doing that manually, e.g. in Post Element Text?
HEADERS
Reference to non-existent ID "GV_VALUE"
Where a report has report has Headings Type "None" and hence no <th>s for headers attributes to refer to. Is there a workaround for this?
REPORT BREAK FORMATTING
End tag for "br" omitted, but OMITTAG NO was specified
<br> tags inserted by break processing within the engine are not terminated " />". This is not controllable by any template (that I am aware of) - anything that can be done?
TEXT FIELDS
This is rather puzzling, as it seems to be random: items on some pages are affected, those on others are not. Anyone have an explanation?
There is no attribute "TYPE"
There is no attribute "NAME"
There is no attribute "SIZE"
There is no attribute "MAXLENGTH"
There is no attribute "VALUE"
There is no attribute "id"
Element "INPUT" undefined
End tag for "INPUT" omitted, but OMITTAG NO was specified
Reference to non-existent ID "P5_ENTRIES_DISPLAYED"
Where the engine is generating an element and attribute names in uppercase instead of all lowercase. From earlier threads, I'm presuming nothing can be done at present.
HYPERLINK
There is no attribute "HREF"
Element "A" undefined
As above: element and attribute names in uppercase instead of all lowercase.
TABLE HEADING/DATA ALIGNMENT
Value of attribute "align" cannot be "LEFT"; must be one of "left", "center", "right", "justify", "char"
Attribute value generated in uppercase. Any workaround?
REPORT SORT ARROW
End tag for "img" omitted, but OMITTAG NO was specified
Sort arrow <img> element not terminated " />". Any workaround? (Or can this be suppressed completely/replaced?)

Hello,
Most of your issues are things we are aware of and hope to get fixed in 3.0 as they are produced from an engine specifically using htf package to render elements which we will be changing. Unfortunatly with most of those issues I see there I don't think you can do much.
I doubt the html the engines produce will pass xhtml strict in 3.0 but we will pass xhtml transitional (other than maybe urls in links) with a custom DTD that takes into account things we output in our namespace.
Carl

JSF autocomplete - fails XHTML validation

My JSF pages (mojarra 2.0.1) generate a hidden state holder with an autocomplete="off"' property as part of the </h:form> closing tag:
<input type="hidden"
name="javax.faces.ViewState"
id="javax.faces.ViewState"
value="-1715251979060474851:6281790946545926031"
autocomplete="off" />
</form>The autocomplete property is not valid XHTML so it does not validate under XHTML 1.0 Transitional, or any other common XHTML DTD as far as I can tell (see: [http://validator.w3.org/]).
I'd like to validate under XHTML 1.0 Transitional. Has anyone got a good fix for this?

The autocomplete was added as a fix, so you do not want to disable this. See: [Issue 1129|https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=1129]
There are a couple of ways to pass validation.
*1) add ATTLIST to doctype - does not work*
I found a way to pass XHTML validation as suggested by: [https://wiki.mozilla.org/The_autocomplete_attribute_and_web_documents_using_XHTML]
Its a little bit it of a cheat really, but I add *[<!ATTLIST input autocomplete CDATA #IMPLIED>]* into my doctype and it will pass the W3C XHTML validator:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
[<!ATTLIST input autocomplete CDATA #IMPLIED>]>This method passes validation, but this leaves your HTML with a "]>" at the start of the page, so is not usable
*2) Custom DTD*
The other way is to download the DTD from W3C, modify it and use your own custom DTD.
Also a cheat but gets you through the W3C tests.
Edited by: zsaurnni on Dec 7, 2009 10:24 PM

Creating XHTML valid PayPal Forms

Hi,
Trying to create an XHTML valid paypal form for view cart, etc. This is the code from the paypal website:
<form target="paypal" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<input type="hidden" name="cmd" value="_cart">
<input type="hidden" name="business" value=".............">
<input type="hidden" name="display" value="1">
<input type="image" src="https://www.paypal.com/en_GB/i/btn/btn_viewcart_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online.">
<img alt="" border="0" src="https://www.paypal.com/en_GB/i/scr/pixel.gif" width="1" height="1">
</form>
My solution so far is:
<form target="paypal" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<fieldset class="paypal">
<div class="paypal">
<input type="hidden" name="cmd" value="_cart"/>
<input type="hidden" name="business" value="............."/>
<input type="hidden" name="display" value="1"/>
<input type="image" src="https://www.paypal.com/en_GB/i/btn/btn_viewcart_LG.gif" name="submit" alt="PayPal - The safer, easier way to pay online." />
<img alt=""src="https://www.paypal.com/en_GB/i/scr/pixel.gif" width="1" height="1" />
</div>
</fieldset>
</form>
The last error is with regard to the <form target=" "> I have experimented using JavaScript:
<script type="text/javascript">
//<![CDATA[
function submitform()
document.myform.submit();
//]]>
</script>
But not sure once I name the script if I can just remove target??
Any help would be greatly appreciated.
Regards,
Ozan89

1) Do we need to use WML renderkit for displaying information on a PDA.
- I'm not too experienced with PDA's, but I'm guessing most of them (new ones) support XHTML these days. You could easily use JSF for this. Which PDA's are you going to support? Is there a specific set of them or just about any PDA out there?
2) How can I develop a single JSP/JSF page and display both on laptop browser and PDA browser.
-If the PDA browser supports XHTML you could do CSS styling based on the user agent so that the page displays differently on the two.
3) Can plain HTML support this funtionality
- Again I'm not sure about PDA compability here, but I would think that many PDA's support plain HTML.
4) Are there examples which demonstrates developing this kind of application:
The WALL project seems like a good place to start searching.

Dreamweaver's XHTML Validation VS W3C's

Hi,
I had some issues with a client xhtml site. So, as a good web developer, I fix them all. So in Dreamwever (CS3), the validation panel told me that everything is fine. But, when I go online on the W3c's validator, I get 8 errors!
Which one is good ?
As an exemple, Dreamweaver tells me that, in xhtml, every tag should be close. So, I close some of my <br> tag as </br>.
Everything was fine in DW, but the W3c's validator tells me the opposite : Closing tags should have an opening one !
I'm really confuse ...
Is validation important ?
Should I trust Dreamweaver's Validator or W3c's
I test some CSS-Based site randomly over the internet and a lot of them have xhtml and/or css issues ... So even great web developers don't always validate their code.
What should I do ?
Thanks for your input !
Martin

Martyn_C wrote:
in Dreamwever (CS3), the validation panel told me that everything is fine. But, when I go online on the W3c's validator, I get 8 errors!
Which one is good ?
The W3C validator is the only one you should trust. There are some errors in the Dreamweaver one.
As an exemple, Dreamweaver tells me that, in xhtml, every tag should be close. So, I close some of my <br> tag as </br>.
Everything was fine in DW, but the W3c's validator tells me the opposite : Closing tags should have an opening one !
The correct way to close an empty tag, such as <br>, in XHTML is like this: <br />.
I test some CSS-Based site randomly over the internet and a lot of them have xhtml and/or css issues ... So even great web developers don't always validate their code.
That's right. Not everyone is bothers to check. I must admit that I don't check every page that I create, but I'm reasonably confident that I'm creating valid code anyway. I used the validator much more in the days when I was learning, as it was very useful in identifying mistakes. Validating a site is also a good way to troubleshoot problems when your page doesn't display as expected.
Most of the websites that I create are my own, so validation is less important. If I were creating a site for a client, I would definitely validate it to make sure everything was OK.

Does WebLogic's generated HTML pass W3C HTML/xHTML validation?

A client needs to use WebLogic AND make sure that the final code is valid HTML
4.01 or XHTML 1.0 transitional code. What tools exist in the IDE to insure that
syntactically correct client code is generated?

Yes, there is a W3C utility, but can only be used "after the fact", after the finished
web page has been generated and sent on to the browser. Is there a way from within
the BEA environment to insure that code created is valid HTML/XHTML?
"Mark Griffith" <[email protected]> wrote:
I am pretty sure there is nothing in the IDE to check this. Doesnt WC3
have
a utility to do this for you?
cheers
mbg
"Chris Spurgeon" <[email protected]> wrote in message
news:[email protected]..
A client needs to use WebLogic AND make sure that the final code isvalid
HTML
4.01 or XHTML 1.0 transitional code. What tools exist in the IDE toinsure that
syntactically correct client code is generated?

Xhtml validation - i dont understand error

Hi All
I have created a site called www.monicawellsphotography.net
I have been following the flash satay method for the flash
movies, along with dreameavers active content script - i tested my
page including the validation and everything checked out
I also used the validation tool on dreamweaver for my pages
and everything seems to be ok on this. HOWEVER the w3c validation
tool is giving me an error message to which I am not sure what to
do about -
It says
1. Error Line 75 column 18: document type does not allow
element "noscript" here; missing one of "object", "applet", "map",
"iframe", "button", "ins", "del" start-tag.
</script><noscript><object
type="application/x-shockwave-flash" data="gallerycom
The mentioned element is not allowed to appear in the context
in which you've placed it; the other mentioned elements are the
only ones that are both allowed there and can contain the element
mentioned. This might mean that you need a containing element, or
possibly that you've forgotten to close a previous element.
One possible cause for this message is that you have
attempted to put a block-level element (such as "<p>" or
"<table>") inside an inline element (such as "<a>",
"<span>", or "<font>").
Although I understand the words I dont understand how to fix
it,
Can anyone help with this?
Best Regards
Lorna17

Me again
Just found out what the problem was - I had a <p> tag
at the beginning and end of it
so please ignore this post
Regards
Lorna17

XHTML Validation

Hi guys. I have converted a page to XHTML 1.1. On this page I
have a DIV inside another DIV. In the inside DIV I have a rollover
image. I get the following message when I validate the markup:
The tag: "img" doesn't have an attribute: "border" in
currently active versions.[XHTML 1.0 strict]
If I remove the "borders" I get funny blue borders around the
rollover. I am still new to Dreamweaver but I decided to try and do
things the correct way from the beginning but it appears as if I
have bitten off more than I can chew. Please help.

> The tag: "img" doesn't have an attribute: "border" in
currently active
> versions.[XHTML 1.0 strict]
This is correct.
> Please help.
Add this to your CSS -
a img {border:none; }
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
==================
"Sailor21" <[email protected]> wrote in message
news:ek4nr6$gcd$[email protected]..
> Hi guys. I have converted a page to XHTML 1.1. On this
page I have a DIV
> inside
> another DIV. In the inside DIV I have a rollover image.
I get the
> following
> message when I validate the markup:
>
> The tag: "img" doesn't have an attribute: "border" in
currently active
> versions.[XHTML 1.0 strict]
>
> If I remove the "borders" I get funny blue borders
around the rollover. I
> am
> still new to Dreamweaver but I decided to try and do
things the correct
> way
> from the beginning but it appears as if I have bitten
off more than I can
> chew.
> Please help.
>

XHTML valid &

hello,
I am trying to validate some of my xhtml however am getting
the old "& in a url" issue as detailed at
htmlhelp.com
however when i change my code to equal & in a .lib item, I
seem to lose the change upon updating all pages that use the .lib
item as it is reverted back to just an & can anyone suggest
some way around this / why this is.
version: dwmx 2004 7.1.etc
Cheers, pop

opps meant .lbi not .lib, anyway solved issue via setting a
var to & eg <%pvar = "&"%> and used that in
place of &. eg a<%=pvar%>b. Bit of hack but works.
However still would like to know why dw seems to strip the code
upon updating a .lbi

Validating xhtml made by coldfusion

Hello there,
I have problems validating the my Cold Fusion pages with the
xhtml. Cold Fusion is inserting the javascript code (see below)
ahead of the page header, as results the xhtml validation cannot
find the DOCTYPE. The javascript is coming from the session
variables that I created to manage login/out.
I would like to know how can I force ColdFusion to insert the
code below the xhtml header?

On both CF8 and CFMX7.0.2 it sticks its script in the
<head> block for me.
And it all validates as XHTML.
It might help if you post your code rather than (some of ~)
the output of
your code.
Adam

Why isn't my page validating XHTML compatible?

If you run my website I'm building through an XHTML validator
it brings up one error and I don't understand why it brings up this
error since all of my XHTML seems to validate fine...
XHTML
Validation Results

You cannot have a <form> tag inside a <p>
paragraph.
<p align="center">
<form action="
http://app.icontact.com/icp/signup.php"
method="post"
name="icpsignup" target="_blank" accept-charset="UTF-8"
onsubmit="return
verifyRequired();pageTracker._linkByPost(this)">
<input type="hidden" name="redirect"
value="
http://dev.thinktecmediagroup.com/thank-you.php"
/>
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
==================
"Chris Jumonville" <[email protected]> wrote
in message
news:gnko91$728$[email protected]..
> If you run my website I'm building through an XHTML
validator it brings up
> one
> error and I don't understand why it brings up this error
since all of my
> XHTML
> seems to validate fine...
>
>
>
>
http://validator.w3.org/check?uri=http%3A%2F%2Fdev.thinktecmediagroup.com%2F&cha
>
rset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%
> 2F1.606
>

Not Valid HTML or XHTML

Hi,
I am baffled because ever since some updates were done to Adobe InContext, I haven't been able to edit certain pages on my websites. I get the error:
"You cannot save this page."
"The page does not appear to be valid HTML or XHTML."
I can't find any problems with it, and I've been able to save my profile pages before with inContext in the past. This happens with both I.E. 8 and Firefox 3.
The affected pages are:
http://www.aliyamustafina.com/includes/ice/ide.html#page=chinese%2Fprofile.php
http://www.anna-pavlova.net/includes/ice/ide.html#page=spanish%2Fprofile.php
Can anyone tell me which code is causing the pages to fail to publish? I removed the PHP code once to see if this would correct it (the PHP code is in a table field that is not set to be editable by InContext), but the error remained.
Thanks!
Alan

Hi Alan,
On a quick inspection I've found several tags which are not closed properly:
in the first page, the map tag is closed twice, and on the bottom of the page there's a tr and td which are never closed. These kind of problems are the most probable cause for which you receive these error messages. Please try to correct the page structure so that it is XHTML valid (you can use a validator to check all the issues) and let me know if you still have the same problem.
Thank you,
Florin

JSF & XHTML/CSS

I am trying to integrate parts of a JSF app I've been making with standard HTML and CSS markup, but I'm running into serious issues. Are there a few things I need to know about how to do this properly? Few pages on the internet address the best way to go about this, though I've already read a lot of complaints about how difficult this is.
This is a simplified version of my HTML showing one button:
<%@ page contentType="text/html; charset=MacRoman" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<style type="text/css" media="screen">
     .button {background-color: white; width: 100%; height: 25px; cursor: pointer; font: 22px sans-serif; font-weight: bold; color: #333300;}
     .button:hover {background-color: #999966; width: 100%; height: 25px; cursor: pointer; font: 22px sans-serif; font-weight: bold; color: #666633;}
     .buttonText {position: relative; left: 30px; background-color: white; width: 300px; line-height: 25px;}
</style>
</head>
<body>
<div class="button">
     <div class="buttonText">
          Create New
     </div>
</div>
</body>
</html>I would like to have the above page in JSF and have the Create New button act as a commandlink, but with the appropriate style applied.
So far I haven't been able to achieve this.
My first question is what to do with the doctype declarations and the other elements that make this page XHTML valid. I tried removing them, but the page did not display correctly in all browsers, and so I put them back in. Is this going to cause any problems at all, or is it something I should be doing anyway? I just felt funny with a JSP page with XHTML declarations, but then again if the JSP is just going to produce markup it should have it.
My HTML page has a fair bit of markup and a small amount of JSF components.
Should I…
-start the <f:view><h:form> tags at the top and end at the bottom while enclosing all the html in <f:verbatim> tags?
-start the <f:view><h:form> at the latest possible times, enclose the HTML within that with <f:verbatim> and leave the rest of the HTML alone?
any other solutions??
Can I apply a style to an h:outputText or h:commandlink ?
thanks

I would not worry too much about making the page XHTML valid. Having doctype there only says what you consider to be valid it certainly has nothing to do with enforcement.
you should be able to include your style css and then use
<h:buttonText styleClass="buttonText"/>
thats all there is to it.

Invalid mark up XHTML 1.0 Strict

I check my pages on XHTML and CSS validators both in DW and
other sites. my css is all correct and my xhtml is correct except
for the flash div. The code is too long to put here, can someone go
put this url through a xhtml validating page and see what I mean? I
need to know how to correct the errors.
swf is on this
page

Nobody???

XHTML vaidator vs Weblogic???

I'm running the HTML generated by my weblogic 8 app through the XHTML
validator at vaidator.wc.org. Very good, finds lots of stuff. But...
It throws errors when it encounters perfectly good Javascript if that
script contains a & or < character. I've found a source that says that
to get around this problem, you should surround your Javascript like
this:
<script type="text/javascript">
// <[CDATA[
valid javascript
// ]]>
</script>
So I did that. When I try to bring up this page, I get a message from
Weblogic saying that a <jsp:text..> tag wasn't closed. There is no
such tag in my jsp page! What's going on?
Tim Slattery
[email protected]
http://members.cox.net/slatteryt

On Thu, 23 Aug 2007 12:40:43 -0700, Tim Slattery <[email protected]>
wrote:
I'm running the HTML generated by my weblogic 8 app through the XHTML
validator at vaidator.wc.org. Very good, finds lots of stuff. But...
It throws errors when it encounters perfectly good Javascript if that
script contains a & or < character. I've found a source that says that
to get around this problem, you should surround your Javascript like
this:
<script type="text/javascript">
// <[CDATA[It turns out this line should have been
// <![CDATA[
and when it's coded that way, everything works properly. I still don't
know why the error appears when the ! isn't there, but I guess it
doesn't matter.
Tim Slattery
[email protected]
http://members.cox.net/slatteryt

XHTML validation trouble

Similar Messages

Maybe you are looking for