XHTML compliant?

[my2001]

Hi!

I'm just wondering if new phpBB 2.2 will be XHTML 1.0/1.1 compliant? I know there has been a feature request regarding XHTML compliance but I don't know if this is already present in current CVS releases or whether it is going to be implemented? Can anybody gimme an hint?

[Graham]

Probably

This is pretty much a template specific issue rather than a coding one, and templates are much lower priority in development terms than the code.

However, if you try validating it, you'll find that it is pretty much there already, bar a couple of minor issues.

[olger901]

Normally spoken it would I even tought it was fully W3C compliant

[my2001]

Probably

This is pretty much a template specific issue rather than a coding one, and templates are much lower priority in development terms than the code.

However, if you try validating it, you'll find that it is pretty much there already, bar a couple of minor issues.

Oh, that would be kewl! And thanks for your answers.

[feaelin]

Probably

This is pretty much a template specific issue rather than a coding one, and templates are much lower priority in development terms than the code.

However, if you try validating it, you'll find that it is pretty much there already, bar a couple of minor issues.

Oh, that would be kewl! And thanks for your answers.

A pleasing thought. Although that means I have to make sure I keep it that way when modding! I've mostly kludged my mods together, so havenn't paid attention to niceties such as standards compliance.

[Toe]

Something I've been wondering - how does phpBB handle overlapping tags? When someone enters something like:

Code: Select all

[b]blah[i]blah[/b]blah[/i]

it would most likely be output as something like:

Code: Select all

<strong>blah<em>blah</strong>blah</em>

Which is invalid XHTML...

[Roberdin]

Something I've been wondering - how does phpBB handle overlapping tags? When someone enters something like:

Code: Select all

[b]blah[i]blah[/b]blah[/i]

it would most likely be output as something like:

Code: Select all

<strong>blah<em>blah</strong>blah</em>

Which is invalid XHTML...

Why not find out?

blahblahblah

Code: Select all

<span style="font-weight: bold">blah<span style="font-style: italic">blah</span>blah</span>

The use of <span> tags has nicely avoided the problem

[profpete]

Comiliant XHTML, but not what the user was intending... 8O

[dhn]

XHTML compliance is easy, now semantical correctness, that is the interesting part.