Msg#: 4483108 posted 3:48 am on Aug 9, 2012 (gmt 0)
It says I have UL inside div and I am not sure how to fix.
There's something you're not telling us. A div can always be outside other stuff; the only limits are the other way around, on where you're allowed to insert a div. And, of course, straddling tags: if the UL starts inside a div, it has to end within that same div.
I count five separate php calls. The validator doesn't see those; it sees the resulting html. So there could be absolutely anything lurking in there:
inside the first <ul> but before its first <li>
inside the first <li>..</li> within that <ul>
inside the second <ul> but before its first <li>
inside a third <ul> nested inside a <li> in the second <ul>
after the last </li> but inside its containing </ul>
That is an awful lot of places where something could happen that the validator would complain about.
Msg#: 4483108 posted 5:41 am on Aug 9, 2012 (gmt 0)
People still use xhtml?
Guess I'm so deep into responsive HTML 5 that I failed to notice!
The designer nested all these instead of having good programming.
Nothing wrong with nesting, everyone does it, I do it all the time, but you have to nest correctly to avoid errors. Without nested DIVs many of the irrationally tablephobic web designers out there would be incapable of generating tabular or column layouts.
FYI, depending on how far you are in the project, and if you aren't committed to XHTML, you could use an HTML 5 framework, several good FREE ones, and get one website that scales from a big desktop monitor all the way down to a cell phone for the same price as developing a regular site that won't function so well on smaller devices.
Msg#: 4483108 posted 10:13 am on Aug 9, 2012 (gmt 0)
You can do both HTML 5 and xhtml in one go: polyglot (x)html5 - It rocks in all possible directions. I'm actually redoing a production site from old xhtml 1.1 into polyglot (x)html5: It's so much easier to have the browser validate the wellformedness all the time, it's also easier getting "that browser" (IE) to properly do CSS for some reason (as it thinks -well actually is- getting html5 while the rest of the browsers get xhtml5)!
But I do agree xhtml1.1 should not be developed any longer, neither should HTML4 be used anymore. (x)html5 is the way forward. And the polyglot variant is IMHO the best choice right now if you want to get to xhtml5 without having to abandon IE users.