|
Re: still too early for XHTML :-((: msg#00045java.enhydra.xmlc
On Čt, 2003-04-10 at 17:50, Jacob Kjome wrote: > > > point out which other element this affects. It is only a "hack" > > to do > > > <script></script> in the sense that you feel you shouldn't have > > to. > > > > right. > > You miss my point. No, I don't. > Opera7 doesn't support XHTML? How so? What behavior do you see? I have a simple page with four combo boxes (<SELECT>) and one submit button. Neither of the elements react to mouse clicks. I can neither pull down the combo boxes nor submit the form. It looks like it's stuck. I may look into that later but to me it looks like it's Opera's fault. > > Got HTML files from our designer and the XMLC couldn't compile it. > I still don't understand what you mean. Again. I got the files and couldn't compile them. The validator said the files were OK. The compiler was not in sync with the validator, it had outdated DTD. In later revisions of XHTML 1.0 they extended the DTD - every tag can have an ID. What can't you understand? I know that the ID is not needed in the TITLE tag but I still think that XMLC should follow the latest XHTML revisions. > that it is doing pretty printing or something. I would definitely > like to find out if compiling XHTML preserves the doctype or not. I can confirm that it does preserve the doctype. Petr
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: still too early for XHTML :-((, Jacob Kjome |
|---|---|
| Next by Date: | Re: still too early for XHTML :-((, Jacob Kjome |
| Previous by Thread: | Re: still too early for XHTML :-((, Jacob Kjome |
| Next by Thread: | Re: still too early for XHTML :-((, Jacob Kjome |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |