errors in header/footer

Post by Dale
Hi,
WAS THIS ALWAYS WRONG OR DID THE CHECKER JUST START LOOKING FOR IT?
https://www.dalekelly.org/
I haven't changed the header/footer for the years of my page.
The error seems to be the "/" before the ">" at the end of each link
<a href="https://validator.w3.org/check?uri=referer"><img
src="https://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01
Strict" height="31" width="88"></a>
For some reason it just checks the main page and gives me that same
error for all.
This are the links I get errors on ...
in HEADER ...
<meta property="og:type" content="website" />
<meta property="og:url" content="https://www.dalekelly.org/" />
<meta property="og:description" content="A place for me to share my
thoughts." />
<meta property="og:title" content="Dale's Website" />
<meta property="og:image"
content="https://www.dalekelly.org/images/shave_haircut.png" />
in FOOTER ...
<a href="https://jigsaw.w3.org/css-validator/check/referer"><img
style="border:0;width:88px;height:31px"
src="https://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid
CSS!" /></a>

Somehow, you repeated your message. I snipped the duplicate part.

Yes, the checkers for HTML, CSS, and Atom and RSS feeds are occasionally
updated and improved.

The virgule (/) indicates the end of an element. However, an end tag is
prohibited for the src elemen. In my hand-crafted (no tool) Web pages,
I only indicate ends where it is generally required; and I use explicit
end tags (e.g., </ul>, </a>) rather than merely a virgule.

--
David E. Ross
<http://www.rossde.com/>

Beyond Meat and other such vegetarian meat substitutes
represent the ultimate in ultra-processed foods. Real
meat is natural. Beyond Meat is definitely not.

2022-10-22 22:14:21 UTC

Post by David E. Ross
The virgule (/) indicates the end of an element. However, an end tag is
prohibited for the src elemen.

It's ironic isn't it, when a specification is not consistent.

Dale

2022-10-22 22:25:06 UTC

Somehow, you repeated your message. I snipped the duplicate part.
Yes, the checkers for HTML, CSS, and Atom and RSS feeds are occasionally
updated and improved.
The virgule (/) indicates the end of an element. However, an end tag is
prohibited for the src elemen. In my hand-crafted (no tool) Web pages,
I only indicate ends where it is generally required; and I use explicit
end tags (e.g., </ul>, </a>) rather than merely a virgule.

Thank You !!!!

I think I will edit one page and see how it goes.

--
Mystery? -> https://www.dalekelly.org/

John-Paul Stewart

2022-10-22 23:13:33 UTC

The trailing slash as shown in <meta ... /> and <img ... /> (etc.) is
XHTML syntax rather than HTML 4.01 Strict, which is what the OP
specified he's using.

In XML and XHTML, you need either a separate closing tag (e.g.,
...) or the "self-closing" <img ... /> syntax. Every element
must be closed one way or the other, unlike plain HTML.

Dale

2022-10-22 23:53:23 UTC

The trailing slash as shown in <meta ... /> and <img ... /> (etc.) is
XHTML syntax rather than HTML 4.01 Strict, which is what the OP
specified he's using.
In XML and XHTML, you need either a separate closing tag (e.g.,
...) or the "self-closing" <img ... /> syntax. Every element
must be closed one way or the other, unlike plain HTML.

I chose "HTML 4.01 Strict" for some kind of overall compatibility
reasons. Forget them for the most part. Looks like I got the wrong
reasons. But this checker error just started lately.

Back then I couldn't find a higher standard for the checker.

I'll put an upgrade to XHTML? on the way.

https://www.w3schools.com/html/html_xhtml.asp

--
Mystery? -> https://www.dalekelly.org/

David E. Ross

2022-10-23 01:53:28 UTC

Post by Dale

The trailing slash as shown in <meta ... /> and <img ... /> (etc.) is
XHTML syntax rather than HTML 4.01 Strict, which is what the OP
specified he's using.
In XML and XHTML, you need either a separate closing tag (e.g.,
...) or the "self-closing" <img ... /> syntax. Every element
must be closed one way or the other, unlike plain HTML.

I chose "HTML 4.01 Strict" for some kind of overall compatibility
reasons. Forget them for the most part. Looks like I got the wrong
reasons. But this checker error just started lately.
Back then I couldn't find a higher standard for the checker.
I'll put an upgrade to XHTML? on the way.
https://www.w3schools.com/html/html_xhtml.asp

Do NOT go to XHTML. The W3C advised against it some time ago. Instead,
try HTML 5.

--
David E. Ross
<http://www.rossde.com/>

Donald Trump demands that he be declared the winner of
the 2020 presidential election. Otherwise, he demands
that the election be rerun immediately.

What has he been smoking?

Dale

2022-10-23 02:15:41 UTC

Post by Dale

The trailing slash as shown in <meta ... /> and <img ... /> (etc.) is
XHTML syntax rather than HTML 4.01 Strict, which is what the OP
specified he's using.
In XML and XHTML, you need either a separate closing tag (e.g.,
...) or the "self-closing" <img ... /> syntax. Every element
must be closed one way or the other, unlike plain HTML.

I chose "HTML 4.01 Strict" for some kind of overall compatibility
reasons. Forget them for the most part. Looks like I got the wrong
reasons. But this checker error just started lately.
Back then I couldn't find a higher standard for the checker.
I'll put an upgrade to XHTML? on the way.
https://www.w3schools.com/html/html_xhtml.asp

Do NOT go to XHTML. The W3C advised against it some time ago. Instead,
try HTML 5.

Thank You !!!!

--
Mystery? -> https://www.dalekelly.org/

David E. Ross

2022-10-23 01:54:49 UTC

Somehow, you repeated your message. I snipped the duplicate part.
Yes, the checkers for HTML, CSS, and Atom and RSS feeds are occasionally
updated and improved.
The virgule (/) indicates the end of an element. However, an end tag is
prohibited for the src elemen. In my hand-crafted (no tool) Web pages,
I only indicate ends where it is generally required; and I use explicit
end tags (e.g., </ul>, </a>) rather than merely a virgule.

Oops! I meant img element, not the "src elemen".

Dale

2022-10-23 12:37:59 UTC

Somehow, you repeated your message. I snipped the duplicate part.
Yes, the checkers for HTML, CSS, and Atom and RSS feeds are occasionally
updated and improved.
The virgule (/) indicates the end of an element. However, an end tag is
prohibited for the src elemen. In my hand-crafted (no tool) Web pages,
I only indicate ends where it is generally required; and I use explicit
end tags (e.g., </ul>, </a>) rather than merely a virgule.

Removed the virgules (/) in question on my index.html

https://www.dalekelly.org/

No errors now.

One of the reason for the "meta property" tags was for other social
media. Checked and they worked.

Noticed that if I run the checker placed on other pages, it checks
index.html. Would like the checker code to check each page I have the
checker on.

Here is the checker code that is on each page ...

<a href="https://validator.w3.org/check?uri=referer"><img
src="https://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01
Strict" height="31" width="88"></a>

This is a new error also. As you said, the checkers for HTML, CSS, and
Atom and RSS feeds are occasionally updated and improved.

How can I edit the checker so it checks the page it is on, not always
index.html? If not how do I edit it specifically for each page?

--
Mystery? -> https://www.dalekelly.org/

John-Paul Stewart

2022-10-23 19:40:50 UTC

Post by Dale
Noticed that if I run the checker placed on other pages, it checks
index.html. Would like the checker code to check each page I have the
checker on.
Here is the checker code that is on each page ...
<a href="https://validator.w3.org/check?uri=referer"><img
src="https://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01
Strict" height="31" width="88"></a>
This is a new error also.

This isn't so much a change in the way the checker works, but a change
in how browsers send the "referer" header. It used to be that they'd
send a full URL (e.g., http://www.example.com/foo.html). Now, for
privacy reasons, they'll typically only send the domain (e.g.,
http://www.example.com/) as the referer.

Thus when the checker tries to check the referer URL, it is only seeing
the domain part that was sent by the browser rather than the full URL of
the page in question. That's why it always checks your index.html no
matter what page the link was on.

See https://en.wikipedia.org/wiki/HTTP_referer#Referrer_hiding for more
info on the topic.

AFAIK, the only way you'll be able to ensure the link on each page
checks that specific page is to edit it manually to specify the full URL
of that page instead of "referer" after the "check?uri=" part. You'll
also have to percent-encode the target URL as described at
https://en.wikipedia.org/wiki/Percent-encoding when creating the links.

Dale

2022-10-23 20:34:15 UTC

This isn't so much a change in the way the checker works, but a change
in how browsers send the "referer" header. It used to be that they'd
send a full URL (e.g., http://www.example.com/foo.html). Now, for
privacy reasons, they'll typically only send the domain (e.g.,
http://www.example.com/) as the referer.
Thus when the checker tries to check the referer URL, it is only seeing
the domain part that was sent by the browser rather than the full URL of
the page in question. That's why it always checks your index.html no
matter what page the link was on.
See https://en.wikipedia.org/wiki/HTTP_referer#Referrer_hiding for more
info on the topic.
AFAIK, the only way you'll be able to ensure the link on each page
checks that specific page is to edit it manually to specify the full URL
of that page instead of "referer" after the "check?uri=" part. You'll
also have to percent-encode the target URL as described at
https://en.wikipedia.org/wiki/Percent-encoding when creating the links.

Thank You !!!!

Some nice study there.

--
Mystery? -> https://www.dalekelly.org/

Jukka K. Korpela

2022-10-23 12:58:04 UTC

Post by David E. Ross
Yes, the checkers for HTML, CSS, and Atom and RSS feeds are occasionally
updated and improved.

And so is the HTML specification, “living HTML”, making it pointless to
proclaim validity. A document that is valid now may become invalid any
moment when the specification is changed.

Post by David E. Ross
The virgule (/) indicates the end of an element.

No it does not. Or, well, in SGML-based HTML it did in theory, but this
was never implemented.

Post by David E. Ross
However, an end tag is
prohibited for the src elemen.

There is no src element.

In the markup

<img src="..." alt="..." />

the slash (solidus) “/” before “>” is XHTML syntax, making the img tag
act both as an opening tag and a closing tag. This was never valid in
HTML 4.01, though it was tolerated by browsers.

The page https://www.dalekelly.org/ declares <!DOCTYPE html>, thereby
referring to “living HTML” as defined at
https://html.spec.whatwg.org/multipage/
Yet it shows an image proclaiming HTML 4.01, which is a much older
specification.

“Valid HTML” icons were always worse than useless, and this is even more
so now. So I will not help in fixing the link (making the “referer”
thing work). The only sensible thing to do with the “validity” icon and
link is to remove them.

Yucca, https://jkorpela.fi

Dale

2022-10-23 16:40:32 UTC

Post by Jukka K. Korpela

Post by David E. Ross
Yes, the checkers for HTML, CSS, and Atom and RSS feeds are occasionally
updated and improved.

And so is the HTML specification, “living HTML”, making it pointless to
proclaim validity. A document that is valid now may become invalid any
moment when the specification is changed.

Post by David E. Ross
The virgule (/) indicates the end of an element.

No it does not. Or, well, in SGML-based HTML it did in theory, but this
was never implemented.

Post by David E. Ross
However, an end tag is
prohibited for the src elemen.

There is no src element.
In the markup
<img src="..." alt="..." />
the slash (solidus) “/” before “>” is XHTML syntax, making the img tag
act both as an opening tag and a closing tag. This was never valid in
HTML 4.01, though it was tolerated by browsers.
The page https://www.dalekelly.org/ declares <!DOCTYPE html>, thereby
referring to “living HTML” as defined at
https://html.spec.whatwg.org/multipage/
Yet it shows an image proclaiming HTML 4.01, which is a much older
specification.
“Valid HTML” icons were always worse than useless, and this is even more
so now. So I will not help in fixing the link (making the “referer”
thing work). The only sensible thing to do with the “validity” icon and
link is to remove them.
Yucca, https://jkorpela.fi

Thank You !!!!

Its on the list for editing. Image tags first.

--
Mystery? -> https://www.dalekelly.org/

Dale

2022-10-23 20:31:58 UTC