Why is OXID not validating?
You are using:
<br> instead of <br />
<input> instead of <input />
etc. etc.
because creating valid templates is your job.
Azure Template is valid with html5 and <input> and <br> is also valid with html4
<input /> <br /> <image /> ist XHTML style
I guess you habe edited the Azure template and put XHTMl doctype instead of default html.
I was meaning the core/, admin/ and views/ files.
I will be a good idea to make OXID HTML5 compatible.
actually this is a big process to be done step by step - and to be honest, it does not harm anyone if it isn´t fully validating at the moment
the main thing are the templates, which lies in your hands
regarding upcoming version 5.0 I´m pretty sure we will have all done
Thanks for the info. We got really frustrated when we have corrected all core-like files to be HTML5 Valid and when 4.6.1 came - all came back 
Morning!
[QUOTE=skygate;91799]Thanks for the info. We got really frustrated when we have corrected all core-like files to be HTML5 Valid and when 4.6.1 came - all came back :([/QUOTE]
Excuse me, I don’t get it at all. Where there are <input> and <br> tags in /core or /view? IMO, everything that belongs to HTML, w3c validity etc shall actually go to /out (the view in MVC). Therefore, the template inheritance and override system was found. If something is not like this, it is a bug.
Cheers
AFAIK the hidden inputs for session and remote tokens are being generated in the code. I don’t get that whole wc3 compliant thing anyways, I never heard of a customer that called and said something like “Hey you are not w3c compliant, I can not order from your store like that”
[QUOTE=aggrosoft;91864]I don’t get that whole wc3 compliant thing anyways, I never heard of a customer that called and said something like “Hey you are not w3c compliant, I can not order from your store like that”[/QUOTE]
This is a ridiculous argument. But If You really want to know - our client has used the W3C validation tool and it took him 1 minute to get the information that the page is not valid.
There are even <br> tags in the lang.php files, if You please use the search tool within the whole project, You will also find the
<dd>, <dt> tags
width used not in css files, but as the attribute as for HTML4
etc etc.
So the general question is:
Could be the OXID code HTML5-valid in some near future? 
Thanks in advance
as I said before - it´s an ongoing process and will be fixed step by step
For sure in some future versions it´ll be nearly totally valid.
As you need to touch all areas of the shop (core, frontend, backend, language-files, templates) this is not an easy task to be done on the side.
if you are a developer or you pretend to be one, press ctrl+a
(and in case if you don’t want to wait for OXID 5.0 to get some valid Templates)
have you heard about smarty?
have you heard about smarty modifier?
have you hear about the smarty modifier “replace”?
[B]be creative and fancy![/B]
[{ $oViewConf->getHiddenSid()|replace:">":" />" }]
[{ oxcontent oxid=$oView->getContentId()|replace:"<br>":"<br />"}]
[{oxeval var=$oLongdesc|replace:"<br>":" <br />"}]
or just modify the oxmultilang function to replace <br> with <br />.
p.s. i wish the [spoiler] feature for this forum 
[QUOTE=vanilla thunder;92024] to replace <br> with <br />
[/QUOTE]
I still don’t get it. What’s wrong with <br>?
<br /> is like a new orthography.
browser also understand the “old-style” <br>, but for some reasons somebody said some days ago, that <br /> is the new better way.
[QUOTE=vanilla thunder;92045]<br /> is like a new orthography.[/QUOTE]
OK but as you said this is XHTML and not HTML5.
I was meaning the core/, admin/ and views/ files.
I will be a good idea to make OXID HTML5 compatible.
its fully compatible