Named anchor not XHTML compliant

I have an XHTML-compliant site (don’t we all?). I want to keep it that way--non-negotiable. My MODx install uses TinyMCE, this is negotiable, but I do like TinyMCE. The only problem I have is that named anchors use the "name" attribute which is not XHTML-compliant, the "id" attribute must be used. My page already uses the "id" attribute for the anchors, but TinyMCE will not recognize these as named anchors and when I try to add new anchors, it forces me to use the "name" attribute. How can I get around this or make TinyMCE XHTML-compliant, at least in this regard?

*bump*? Does anyone focus on XHTML-compliancy?

I suspect the way it’s being done is messed up, but anchors using name are still fine as XHTML S/T/F using a standard link. <a name="anchor"></a> should work and validate just fine. Could you elaborate on the issue?

Reference: http://www.w3schools.com/tags/tag_a.asp

Quote from: AMDbuilder at Nov 13, 2009, 05:24 PM

I suspect the way it’s being done is messed up, but anchors using name are still fine as XHTML S/T/F using a standard link. <a name="anchor"></a> should work and validate just fine. Could you elaborate on the issue?

Reference: http://www.w3schools.com/tags/tag_a.asp

I have to apologize for the seriously late response here, no notification received before. However, now and back then, the page on w3schools says that it is valid for HTML/XHTML Strict 1.0, which is different from strict 1.1, what my clients use. The name attribute in general is deprecated in 1.1:

Reference: http://www.w3.org/TR/xhtml11/changes.html#a_changes

That means any pages that use the name attribute no longer validate, which is good because name duplicates information that should be found in the id element. The problem is in clients knowing just enough to be dangerous, even to themselves. It doesn’t take much more than a client seeing some webpage say the development is not up to standards for the client to start looking elsewhere or asking questions that move in circles.

If the plug-in developers are otherwise occupied, I hope it will be a straightforward change to make on my end at least to support id over name for anchors. I will see if any newer releases of the editors provide fuller XHTML support or capabilites.

And that is precisely why I’ve completely dropped XHTML in favor of HTML5. All of my templates from now on will be HTML5. Besides, it’s a lot of fun to use <article>...</article> tags in Ditto tpls

Quote from: sottwell at Jul 04, 2010, 12:10 AM

And that is precisely why I’ve completely dropped XHTML in favor of HTML5. All of my templates from now on will be HTML5. Besides, it’s a lot of fun to use <article>...</article> tags in Ditto tpls

Are you finding better support from the editors for 5? Any in particular?

Never really paid much attention; I just use a programmer’s editor called Smultron. But then I started out writing assembly language utilities for DOS using EDLIN, so I’m not very discriminating.