6 Dec
2011
6 Dec
'11
2:48 p.m.
On Dec 5, 2011, at 8:41 PM, Jerome Velociter wrote:
On Mon, Dec 5, 2011 at 11:33 AM, Vincent Massol
<vincent(a)massol.net> wrote:
FTR I had created this some time ago:
http://jira.xwiki.org/jira/browse/XRENDERING-137
So while I agree to move to HTML5 as soon as we can, we need to be careful to list all
possible issues and fix them first.
Thanks
-Vincent
Hi Jerome,
On Dec 5, 2011, at 11:27 AM, Jerome Velociter wrote:
HTML5 doctype only really affects the triggering of support mode of
browsers (quirks vs. standard). FF 3.6 and others will go just fine,
rendering in standard mode. See
http://stackoverflow.com/questions/5629/any-reason-not-to-start-using-the-h…
for more.
One thing we have to keep in mind though is validation. For example
<tt> is deprecated with HTML5, and our XHTML renderer renders the
##syntax## as <tt>. We might have to introduce a HTML5 renderer to
take care of such differences with XHTML specs. Hello,
Since we are dropping support for IE6 and IE7, wouldn't it be a good
time to switch to the HTML5 doctype [1] ?
It would also force IE8 to render in non-compatibility mode (meaning
using the IE8 rendering engine), as a good side effect. [2]
Maybe we can do this in XE 3.4 ?
WDYT ?
Is it going to work with FF 3.6?
Are there recent browsers not supporting (or supporting badly) this HTML5 doctype
nowadays? > Thanks
> -Vincent
>
>>
>> Jerome