You are not logged in.
in almost all the popups used, we can find some XHTML markup. For instance, in changeset [254], the file plugins/Forms/popups/select.html has added some XHTML markup (<p />, <input />, etc.), but this file IS NOT a xhtml document because it is NOT using any DTD and as a result it is falling in quirks mode which is HTML not XHTML.
Yes i have said it a lot already and i'll keep saying it until
1) we decide to use a valide markup
2) or someone stop ignoring my argue on this point
3) or someone explain me the reason why this choice has been made. Even if i dont think it is a choice at all but just a very old mistake we keep from htmlarea.
This is a real issue with the way we communicate between the javascript and the document, see ticket #318
Offline
I agree fully with you on this, the xhtml tags are "hyped" in my opinion in a "cool" mannor. Same with the <br> tag entered by htmlarea as <br />, which is fine if your doing xhtml but since we are mostly working in HTML v4.01 this is kinda dumb, and more importantly isn't correct.
Its been some while since I did the Xhtml compability check with the browsers (When we talk of serving the pages correctly with correct character encoding and such), but I would think moving to XHTML wouldt be a problem now - but I would not like to XINHA working in a XHTML only environment, since most people including myself use it in a HTML v4.01 environment.
Offline
It would be nice if it was in XHTML. It is the current standard after all.
Offline
There are two considerations:
1. The (x)html of the popups, and xinha-editor itself
2. The (x)html produced by Xinha (inside the editor)
In the first case, our objective should not be "conforming to standards 100%" it is "well formed and working" - that is, "tag soup" is fine, as long as it's well formed (tags closed, no invalid nesting, quoted attributes, lower case etc) and it works in the browsers we care about (currently Gecko and IE, later Safari (or maybe even generic KHTML if that's possible now)). Personally, I don't give a rats if the html in the dialogs conforms to any particular standard as long as they work and are tidy - if this was a generic interface thave could be used by alternate devices or whatever then I'd be more concerned, but it's not, it's Javascript heavy, Gecko and IE only, as long as it works there, no problem.
For the (x)html coming out of Xinha, we don't have a lot of control. Infact, we have very little control - the browser makes the HTML. For example when the user clicks the bold button, we just tell the browser "the user said 'do bold'", it's the browser that works out what needs to be bolded, and how it should be done, we don't get to do anything about that. In short, the (x)html coming out of Xinha is going to be well-formed, but if it's valid for any specification, not a hope.
James Sleeman
Offline