Yes, I thought about a config param as well. But I wanted to make it
not too sophisticated and to introduce another piece for config hell.
However, I can live with the config param as long as it defaults to true.
BTW, I like the name STRICT_XHTML_LINKS
What do others think?
--Manfred
On Nov
I like mario's suggestion.
-M
On Nov 22, 2007 9:43 AM, Manfred Geiler [EMAIL PROTECTED] wrote:
Yes, I thought about a config param as well. But I wanted to make it
not too sophisticated and to introduce another piece for config hell.
However, I can live with the config param as long as it
I'd rather it use the standard always, but defaulting to the standard
with a way to revert to the incorrect form shouldn't harm anything.
On Nov 22, 2007 1:43 AM, Manfred Geiler [EMAIL PROTECTED] wrote:
Yes, I thought about a config param as well. But I wanted to make it
not too sophisticated
And in particular, as the Sun RI renders , it is nice to have the
option to be bug-compatible.
So in this case, I'm also in favour of making it configurable.
Simon
On Thu, 2007-11-22 at 10:12 -0700, Andrew Robinson wrote:
I'd rather it use the standard always, but defaulting to the standard
Please have a look at
http://issues.apache.org/jira/browse/MYFACES-1774
Do you think there is a problem with generally rendering amp; instead of ?
Issues with old browsers perhaps?
Thanks,
Manfred
For html, I think we should continue to render .
For xhtml, we should render amp;
On Nov 21, 2007 7:37 AM, Manfred Geiler [EMAIL PROTECTED] wrote:
Please have a look at
http://issues.apache.org/jira/browse/MYFACES-1774
Do you think there is a problem with generally rendering amp; instead of
yeah, but the renderer does not know if the current page rendered has
a html or a xhtml header.
So, I propose to always render amp; as it is recommended in the W3C
HTML Spec.
All browsers SHOULD interpret it correctly. If not, it is definitely a
browser bug.
And if someone has an issue with an
Hi!
So, I propose to always render amp; as it is recommended in the W3C
HTML Spec.
I'd propose to make it configureable out of the box, a simple
context-param with default to amp; - easy enough and will survive the
users from providing their own LinkRenderer.
Something like:
