does anyone know why JSF 2.0 at the moment seemingly doesn't support strict XHTML? Accordingly to the specification it's only required to render XHTML 1.0 transitional to conform to the spec. Is there any way to make the generated output "strict"? Or are there plans to support XHTML strict in furture releases?
Could you please explain in more detail why you think loose XHTML is the way to go?
Of course it's easier in the first place if you allow anyone to produce any kind of HTML as they like. And I'm well aware of the fact that web development sometimes may require some dirty hacks just to get things done because even the most popular browsers don't work 100% correctly. But I can't see why loose XHTML should help to solve these problems in the long run.
To say that it makes development more difficult when you use strict XHTML sounds like you would prefer to produce loose (or better say invalid?) XHTML so that no one has to think about the correctness of XHTML files.
posted 9 years ago
Perfection is always the best option. But time limitation and priorities are set in the project goal.
The highest priority is given to business logic and model and the lowest is given to view.
JSF pages is also develop by programmer or software engineer. if the markup is becoming problem for him then it took lots of time and not worth too much.