Do they have a point, or are they just trying to pick holes in
somebody’s coat?
If you ask me, that’s the most petty, picky validator I’ve seen so
far. If the W3C site validator gives you a pass - and it does - then
use the W3C icons. The W3C page offers them after giving you a
‘congratulations’ for your site.
Save the Webthing validation for when you want to diss someone else’s
site, don’t bother with using it on your own.
How important is it to achieve full validation? After reading this
thread I got curious and I ran my new home page through the WC3
validator which reported two errors. I tried a couple of name changes
to items but it reported the same error just with the name changed so
I am surmising it is in the Freeway generated code. What to do? And
is it worth it?
Pete
On 16 Feb 2008, at 23:05, Keith Martin wrote:
Sometime around 16/2/08 (at 05:20 -0500) bartdemylle said:
Do they have a point, or are they just trying to pick holes in
somebody’s coat?
If you ask me, that’s the most petty, picky validator I’ve seen so
far. If the W3C site validator gives you a pass - and it does - then
use the W3C icons. The W3C page offers them after giving you a
‘congratulations’ for your site.
Save the Webthing validation for when you want to diss someone else’s
site, don’t bother with using it on your own.
Can you provide a link please Pete. Out of the box Freeway sites
should validate with no problems, some third party Actions or manually
entered code could prevent sites from validating.
Joe
On 17 Feb 2008, at 00:31, Pete MacKenzie wrote:
How important is it to achieve full validation? After reading this
thread I got curious and I ran my new home page through the WC3
validator which reported two errors. I tried a couple of name changes
to items but it reported the same error just with the name changed so
I am surmising it is in the Freeway generated code. What to do? And
is it worth it?
Pete
On 16 Feb 2008, at 23:05, Keith Martin wrote:
Sometime around 16/2/08 (at 05:20 -0500) bartdemylle said:
Do they have a point, or are they just trying to pick holes in
somebody’s coat?
If you ask me, that’s the most petty, picky validator I’ve seen so
far. If the W3C site validator gives you a pass - and it does - then
use the W3C icons. The W3C page offers them after giving you a
‘congratulations’ for your site.
Save the Webthing validation for when you want to diss someone else’s
site, don’t bother with using it on your own.
Here’s the link Joe. Apart from the Carousel (so it may be that, from what you say) all is done from scratch in FW5. I used the validator at http://validator.w3.org/
I haven’t tried any of the other pages. There was an unfinished <tr tag and apparently the validator reckoned the item carouselchassis is referenced twice. It had been named item 1 and there was also an item1a but I changed the names wondering if that was the problem to no avail. Same error message with the new name. Full error messages copied below (richtext to show colours).
See what you think
Pete
Validation Output: 2 Errors
Error Line 313, Column 59: ID “CAROUSELCHASSIS” already defined.
An “id” is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
2. Info Line 313, Column 11: ID “CAROUSELCHASSIS” first defined here.
<div id="carouselchassis" clas
Error Line 322, Column 8: end tag for “TR” which is not finished.
Most likely, you nested tags and closed them in the wrong order. For example
…
is not acceptable, as must be closed before
. Acceptable nesting is:
…
Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is “not finished”, not complete. For instance, in HTML the element must contain a child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Could you please send me the Freeway file? I need to look at this,
because I thought I made this particular problem impossible.
Walter
On Feb 17, 2008, at 6:39 AM, Pete MacKenzie wrote:
Here’s the link Joe. Apart from the Carousel (so it may be that,
from what you say) all is done from scratch in FW5. I used the
validator at http://validator.w3.org/
I haven’t tried any of the other pages. There was an unfinished <tr
tag and apparently the validator reckoned the item carouselchassis
is referenced twice. It had been named item 1 and there was also an
item1a but I changed the names wondering if that was the problem to
no avail. Same error message with the new name. Full error messages
copied below (richtext to show colours).
See what you think
Pete
Validation Output: 2 Errors
Error Line 313, Column 59: ID “CAROUSELCHASSIS” already defined.
✉
An "id" is a unique identifier. Each time this attribute is
used in a document it must have a different value. If you are using
this attribute as a hook for style sheets it may be more
appropriate to use classes (which group elements) than id (which
are used to identify exactly one element).
2. Info Line 313, Column 11: ID “CAROUSELCHASSIS” first defined
here.
Error Line 322, Column 8: end tag for “TR” which is not
finished.
</tr>
Most likely, you nested tags and closed them in the wrong
order. For example
…
is not acceptable, as must
be closed before
. Acceptable nesting is:
…
Another possibility is that you used an element which
requires a child element that you did not include. Hence the parent
element is “not finished”, not complete. For instance, in HTML the
element must contain a child element, lists (ul, ol,
dl) require list items (li, or dt, dd), and so on.
Pete sent me his document off-list, and I was able to find a bug in
the Action. I have revved the action, the latest version of
Protaculous is now 0.7.3b. You may download it at http:// freewaypro.com/actions/downloads/
More to come, very soon.
Also, if you are using Protaculous and the Softpress Scriptaculous
actions in the same document, realize that you are loading the same
gigantic JavaScripts into your page twice. It will work (I revved the
version of Prototype and Scriptaculous so I am shipping the same
version as Softpress) but you will be needlessly punishing your site
visitors with a truly enormous page download.
Joe Billings and I are working out a way to determine if a library is
already loaded so we won’t cause this problem in the future. But for
the moment, please choose one or the other – they can’t be together
on the same page without this side-effect happening.
Walter
On Feb 17, 2008, at 9:00 AM, Walter Lee Davis wrote:
Could you please send me the Freeway file? I need to look at this,
because I thought I made this particular problem impossible.
Walter
On Feb 17, 2008, at 6:39 AM, Pete MacKenzie wrote:
Here’s the link Joe. Apart from the Carousel (so it may be that,
from what you say) all is done from scratch in FW5. I used the
validator at http://validator.w3.org/
I haven’t tried any of the other pages. There was an unfinished <tr
tag and apparently the validator reckoned the item carouselchassis
is referenced twice. It had been named item 1 and there was also an
item1a but I changed the names wondering if that was the problem to
no avail. Same error message with the new name. Full error messages
copied below (richtext to show colours).
See what you think
Pete
Validation Output: 2 Errors
Error Line 313, Column 59: ID “CAROUSELCHASSIS” already
defined.
✉
An "id" is a unique identifier. Each time this attribute is
used in a document it must have a different value. If you are using
this attribute as a hook for style sheets it may be more
appropriate to use classes (which group elements) than id (which
are used to identify exactly one element).
2. Info Line 313, Column 11: ID “CAROUSELCHASSIS” first defined
here.
Error Line 322, Column 8: end tag for “TR” which is not
finished.
</tr>
Most likely, you nested tags and closed them in the wrong
order. For example
…
is not acceptable, as must
be closed before
. Acceptable nesting is:
…
Another possibility is that you used an element which
requires a child element that you did not include. Hence the parent
element is “not finished”, not complete. For instance, in HTML the
element must contain a child element, lists (ul, ol,
dl) require list items (li, or dt, dd), and so on.
Sometime around 17/2/08 (at 16:06 -0500) bartdemylle said:
Wow, I never thought my question about validation would result in an
action being improved.
My hat is off to Walter. He’s shown yet another reason why Freeway is
the nicest way to make web sites… not just 'cause it is easy, but
also because Freeway’s users are so darn friendly!
With regards to the original validation question, the validation that
failed was an accessibility validation. If you change the evaluation
type from Accessibility to Validate then your page will validate fine.
We have addressed a number of accessibility issues in Freeway 5 but
remember that there are no hard and fast rules for validation so one
site’s valid could be another’s invalid and vide versa.
Joe
On 17 Feb 2008, at 21:21, Keith Martin wrote:
Sometime around 17/2/08 (at 16:06 -0500) bartdemylle said:
Wow, I never thought my question about validation would result in an
action being improved.
My hat is off to Walter. He’s shown yet another reason why Freeway is
the nicest way to make web sites… not just 'cause it is easy, but
also because Freeway’s users are so darn friendly!
With regards to the original validation question, the validation that
failed was an accessibility validation. If you change the evaluation
type from Accessibility to Validate then your page will validate fine.
We have addressed a number of accessibility issues in Freeway 5 but
remember that there are no hard and fast rules for validation so one
site’s valid could be another’s invalid and vide versa.
Joe
On 17 Feb 2008, at 21:21, Keith Martin wrote:
Sometime around 17/2/08 (at 16:06 -0500) bartdemylle said:
Wow, I never thought my question about validation would result in an
action being improved.
My hat is off to Walter. He’s shown yet another reason why Freeway is
the nicest way to make web sites… not just 'cause it is easy, but
also because Freeway’s users are so darn friendly!