Is there any movement in fixing the bad and invalid html that orbeon
generates today. It is full with inline elements like spans containing blocklevel elements and too much element all together. Is anybody working on this or even aware of the problem. I am trying to intergrate orbeon in a valid xhtml1.0 transitional site and sure don't like what it gives me. Cheers, Wilfred Nas WNAS User Interface Consultant 06-24269159 http://wnas.nl [hidden email] twitter.com/wnas -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Administrator
|
Wilfred,
Re. the issue of inline containing block, I assume you are referring to the issue of <span> elements produced by <xforms:group>? One issue is that <xforms:group> can be used for both inline and block scenarios. So we picked <span> to represent xforms:group as this just works with all major browsers. This has never been a problem in the past AFAIK but still it would be good to find a general solution to this. I have entered an RFE to track this: http://forge.ow2.org/tracker/index.php?func=detail&aid=313974&group_id=168&atid=350207 Now if you are looking for a quick fix in your application, you could modify RESOURCES/config/theme-plain.xsl, or create another theme stylesheet, and replace all xhtml:span[tokenize(@class, '\s+') = 'xforms-group'] with xhtml:div elements. I have also entered a bug for the issue of "too many elements" with checkboxes and radio button: http://forge.ow2.org/tracker/index.php?func=detail&aid=313975&group_id=168&atid=350207 In this case though, I don't think modifying the XHTML produced in the theme will do, as the client-side JS assumes a specific hierarchy. But Orbeon Forms is open source and if you can work towards improving this it would be great. -Erik On Jul 2, 2009, at 10:00 AM, Wilfred Nas wrote: > Is there any movement in fixing the bad and invalid html that orbeon > generates today. It is full with inline elements like spans > containing blocklevel elements and too much element all together. Is > anybody working on this or even aware of the problem. > > I am trying to intergrate orbeon in a valid xhtml1.0 transitional > site and sure don't like what it gives me. > > > Cheers, > > Wilfred Nas > > WNAS > User Interface Consultant > > 06-24269159 > http://wnas.nl > [hidden email] > twitter.com/wnas > > > > > > -- > You receive this message as a subscriber of the [hidden email] > mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws Orbeon Forms - Web Forms for the Enterprise Done the Right Way http://www.orbeon.com/ -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Free forum by Nabble | Edit this page |