Custom XHTML attributes cause W3C validation fail

Hello,

up to now (CB1., CB uses diverse custom XHTML attibutes, e.g. mod_cblogin with cb_captcha uses "mosLabel" and "mosReq", and the profile edit page uses "autocomplete".

This causes W3C XHTML markup validation to fail for pages which show the cb_login module with cb_captcha or fpr the profile page in edit mode.

Is this planned to be changed some day, e.g. by using class attributes or the HTML5 "data-" attributes?

If planned to be changed: When?

I've checked the php scripts of CB and cb_captcha and see it is not trivial: The "mosLabel" and "mosReq" attributes are used many times there.

But the "autocomplete" atribute I have not found to be used anywhere, maybe it is obsolete meanwhile? If so, can it be removed?

Best regards,

Richard

Yes it's planned to be changed with release of CB 2.0. Those tags are used by only Joomla releases (J1.0 and mambo) so are kept for backwards compatibility sake. "autocomplete" is used to disable form auto complete. It prevents browsers for example auto populating it with data and is a valid XHTML tag. I suppose you can remove it if you absolutely feel necessary. I believe only Webkit and Mozilla based browsers actually support it; meaning Firefox, Chrome, Safari, etc..

Thanks for the answer.

Am looking forward to CB 2.0 then.

But regarding the autocomplete: Do you mean it will remain there?

This will cause W3C XHTML 1.0 markup validation to fail, because it if not W3C standard, whatever browsers may support or not.

Or is valid XHTML 1.1?

Best regards,

Richard

But regarding the autocomplete: Do you mean it will remain there?

Probably.

This will cause W3C XHTML 1.0 markup validation to fail, because it if not W3C standard, whatever browsers may support or not.

Or is valid XHTML 1.1?

autocomplete is not XHTML compliant until recent XHTML5. All past XHTML will never validate autocomplete as it started as a browser attribute specific to Webit/Mozilla engines (Chrome, Safari, Firefox). However, with HTML5 it's now a valid HTML attribute so of course XHTML needs to support it, but not with previous releases; only with recent XHTML5.

HTML5 is not Joomla standard yet, or is it?
What I've seen is all templates wich I know produce XHTML 1.

Hi, it's me again.

From my point of view CB should generate valid markip according to the document type. Can't CB check the document type and integrate autocomplete only if HTML5?

Best regards,

Richard