9 Oct
2014
9 Oct
'14
12:19 p.m.
Hello.
Flamingo is still not HTML5 valid, so I am working on it.
We actually use some <meta> tags that are become invalid in HTML5.
= X-UA-Compatible =
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
It forces the Compatibility mode for IE browsers to use the latest
rendering mode.
We can replace it by adding the X-UA-Compatible in the HTTP headers, but I
actually propose to surround this tag like this:
<!--[if IE]>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<![endif]-->
The code is valid (because inside a comment so the validator does not parse
it) and it is still usable with IE.
= imagetoolbar =
<meta http-equiv="imagetoolbar" content="no"/>
it disables the toolbar that comes up when you mouse over an image in MSIE.
Same, I propose to add a conditional comment:
<!--[if IE]>
<meta http-equiv="imagetoolbar" content="no"/>
<![endif]-->
= Content-Script-Type =
<meta http-equiv="Content-Script-Type" content="text/javascript"
/>
It defines the default scripting language that is used for intrinsic events
(e.g. onmouseover attributes).
This tag has been deprecated, and there is nothing to replace it. I don't
think this tag is very useful because most of the browsers assume that an
intrinsic event will be handled by javascript. Actually I did not know this
meta tag before today and my inline javascript did always work!
So I propose to just remove it.
= Distribution =
<meta name="distribution" content="GLOBAL" /> (from
XWiki.XWikiPreferences)
It actually defines either the website should be considered as public or
local (see See http://www.metatags.info/meta_name_distribution).
I propose to remove it.
= reply-to =
<meta http-equiv="reply-to" content="" /> (from
XWiki.XWikiPreferences)
To be useful, the content should not be empty, so the administrator should
set it. Moreover, it is very not well-known, and it could be a problem
since the spam bots can read it.
I propose to remove it. If the administrator wants it, she can put it in
the preferences, with the proper value filled.
= language =
<meta name="language" content="en" /> (from
XWiki.XWikiPreferences)
It is actually redundant with <html lang="en">.
I propose to remove it.
What do you think?
Thanks,
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
9 Oct
9 Oct
12:26 p.m.
2014-10-09 12:19 GMT+02:00 Guillaume "Louis-Marie" Delhumeau <
gdelhumeau(a)xwiki.com>gt;:
Hello.
Flamingo is still not HTML5 valid, so I am working on it.
We actually use some <meta> tags that are become invalid in HTML5.
= X-UA-Compatible =
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
It forces the Compatibility mode for IE browsers to use the latest
rendering mode.
We can replace it by adding the X-UA-Compatible in the HTTP headers, but I
actually propose to surround this tag like this:
<!--[if IE]>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<![endif]-->
Actually, after some tests done last year, I got the conclusion that we
should use both the <meta> tag AND the HTTP header. If only one of them is
used, IE does not always obey, *on intranet sites*.
See
http://stackoverflow.com/questions/6156639/x-ua-compatible-is-set-to-ie-edg…
The code is valid (because inside a comment so the validator does not
parse it) and it is still usable with IE.
= imagetoolbar =
<meta http-equiv="imagetoolbar" content="no"/>
it disables the toolbar that comes up when you mouse over an image in MSIE.
Same, I propose to add a conditional comment:
<!--[if IE]>
<meta http-equiv="imagetoolbar" content="no"/>
<![endif]-->
= Content-Script-Type =
<meta http-equiv="Content-Script-Type" content="text/javascript"
/>
It defines the default scripting language that is used for intrinsic
events (e.g. onmouseover attributes).
This tag has been deprecated, and there is nothing to replace it. I don't
think this tag is very useful because most of the browsers assume that an
intrinsic event will be handled by javascript. Actually I did not know this
meta tag before today and my inline javascript did always work!
So I propose to just remove it.
= Distribution =
<meta name="distribution" content="GLOBAL" /> (from
XWiki.XWikiPreferences)
It actually defines either the website should be considered as public or
local (see See http://www.metatags.info/meta_name_distribution).
I propose to remove it.
= reply-to =
<meta http-equiv="reply-to" content="" /> (from
XWiki.XWikiPreferences)
To be useful, the content should not be empty, so the administrator should
set it. Moreover, it is very not well-known, and it could be a problem
since the spam bots can read it.
I propose to remove it. If the administrator wants it, she can put it in
the preferences, with the proper value filled.
= language =
<meta name="language" content="en" /> (from
XWiki.XWikiPreferences)
It is actually redundant with <html lang="en">.
I propose to remove it.
What do you think?
Thanks,
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
6:30 p.m.
On 10/09/2014 06:19 AM, Guillaume "Louis-Marie" Delhumeau wrote:
Hello.
Flamingo is still not HTML5 valid, so I am working on it.
We actually use some <meta> tags that are become invalid in HTML5.
= X-UA-Compatible =
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
It forces the Compatibility mode for IE browsers to use the latest
rendering mode.
We can replace it by adding the X-UA-Compatible in the HTTP headers, but I
actually propose to surround this tag like this:
<!--[if IE]>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<![endif]-->
The code is valid (because inside a comment so the validator does not parse
it) and it is still usable with IE.
Since we can control the headers, and the meta element only works in
certain conditions, we should set this as a header instead. To make sure
this is always set, we can add a servlet filter that adds that header.
For performance (smaller responses), we can only add it if the request
comes from an IE browser.
= imagetoolbar =
<meta http-equiv="imagetoolbar" content="no"/>
it disables the toolbar that comes up when you mouse over an image in MSIE.
Same, I propose to add a conditional comment:
<!--[if IE]>
<meta http-equiv="imagetoolbar" content="no"/>
<![endif]-->
This is no longer needed, XWiki doesn't support IE6 anymore, and newer
versions don't have an image toolbar.
Simply remove it.
= Content-Script-Type =
<meta http-equiv="Content-Script-Type" content="text/javascript"
/>
It defines the default scripting language that is used for intrinsic events
(e.g. onmouseover attributes).
This tag has been deprecated, and there is nothing to replace it. I don't
think this tag is very useful because most of the browsers assume that an
intrinsic event will be handled by javascript. Actually I did not know this
meta tag before today and my inline javascript did always work!
So I propose to just remove it.
This was added since there's an accessibility rule that mandates it.
Since it's an http-equiv, we should add this as a HTTP header as well.
= Distribution =
<meta name="distribution" content="GLOBAL" /> (from
XWiki.XWikiPreferences)
It actually defines either the website should be considered as public or
local (see See http://www.metatags.info/meta_name_distribution).
I propose to remove it.
This one is ancient, IIRC it was there before my time. I doubt it has
any relevance, and since most XWiki instances are private intranets (I
guess?), "global" is wrong as a default value, yet I doubt anyone ever
changes it. +1 for removing it.
= reply-to =
<meta http-equiv="reply-to" content="" /> (from
XWiki.XWikiPreferences)
To be useful, the content should not be empty, so the administrator should
set it. Moreover, it is very not well-known, and it could be a problem
since the spam bots can read it.
I propose to remove it. If the administrator wants it, she can put it in
the preferences, with the proper value filled.
That's not a valid header... Remove it.
= language =
<meta name="language" content="en" /> (from
XWiki.XWikiPreferences)
It is actually redundant with <html lang="en">.
I propose to remove it.
Remove it.
What do you think?
Thanks,
--
Sergiu Dumitriu
http://purl.org/net/sergiu
14 Oct
14 Oct
11:51 a.m.
Thanks Sergiu. I am going to do this.
2014-10-09 18:30 GMT+02:00 Sergiu Dumitriu <sergiu(a)xwiki.org>rg>:
On 10/09/2014 06:19 AM, Guillaume
"Louis-Marie" Delhumeau wrote:
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hello.
Flamingo is still not HTML5 valid, so I am working on it.
We actually use some <meta> tags that are become invalid in HTML5.
= X-UA-Compatible =
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
It forces the Compatibility mode for IE browsers to use the latest
rendering mode.
We can replace it by adding the X-UA-Compatible in the HTTP headers, but
I
actually propose to surround this tag like this:
<!--[if IE]>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<![endif]-->
The code is valid (because inside a comment so the validator does not
parse
it) and it is still usable with IE.
Since we can control the headers, and the meta element only works in
certain conditions, we should set this as a header instead. To make sure
this is always set, we can add a servlet filter that adds that header.
For performance (smaller responses), we can only add it if the request
comes from an IE browser.
= imagetoolbar =
<meta http-equiv="imagetoolbar" content="no"/>
it disables the toolbar that comes up when you mouse over an image in
MSIE.
Same, I propose to add a conditional comment:
<!--[if IE]>
<meta http-equiv="imagetoolbar" content="no"/>
<![endif]-->
This is no longer needed, XWiki doesn't support IE6 anymore, and newer
versions don't have an image toolbar.
Simply remove it.
= Content-Script-Type =
<meta http-equiv="Content-Script-Type" content="text/javascript"
/>
It defines the default scripting language that is used for intrinsic
events
(e.g. onmouseover attributes).
This tag has been deprecated, and there is nothing to replace it. I don't
think this tag is very useful because most of the browsers assume that an
intrinsic event will be handled by javascript. Actually I did not know
this
meta tag before today and my inline javascript
did always work!
So I propose to just remove it.
This was added since there's an accessibility rule that mandates it.
Since it's an http-equiv, we should add this as a HTTP header as well.
= Distribution =
<meta name="distribution" content="GLOBAL" /> (from
XWiki.XWikiPreferences)
It actually defines either the website should be
considered as public or
local (see See http://www.metatags.info/meta_name_distribution).
I propose to remove it.
This one is ancient, IIRC it was there before my time. I doubt it has
any relevance, and since most XWiki instances are private intranets (I
guess?), "global" is wrong as a default value, yet I doubt anyone ever
changes it. +1 for removing it.
= reply-to =
<meta http-equiv="reply-to" content="" /> (from
XWiki.XWikiPreferences)
To be useful, the content should not be empty, so the administrator
should
set it. Moreover, it is very not well-known, and
it could be a problem
since the spam bots can read it.
I propose to remove it. If the administrator wants it, she can put it in
the preferences, with the proper value filled.
That's not a valid header... Remove it.
= language =
<meta name="language" content="en" /> (from
XWiki.XWikiPreferences)
It is actually redundant with <html lang="en">.
I propose to remove it.
Remove it.
What do you think?
Thanks,
--
Sergiu Dumitriu
http://purl.org/net/sergiu
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
15 Oct
15 Oct
2:45 p.m.
2014-10-09 18:30 GMT+02:00 Sergiu Dumitriu <sergiu(a)xwiki.org>rg>:
For this one, I think we can add it in the Servlet. I don't think it is
skin-dependent.
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
On 10/09/2014 06:19 AM, Guillaume
"Louis-Marie" Delhumeau wrote:
Don't you think this header could also depend on the skin? If yes, then I
prefer to add that HTTP header in htmlheaders.vm.
Hello.
Flamingo is still not HTML5 valid, so I am working on it.
We actually use some <meta> tags that are become invalid in HTML5.
= X-UA-Compatible =
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
It forces the Compatibility mode for IE browsers to use the latest
rendering mode.
We can replace it by adding the X-UA-Compatible in the HTTP headers, but
I
actually propose to surround this tag like this:
<!--[if IE]>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<![endif]-->
The code is valid (because inside a comment so the validator does not
parse
it) and it is still usable with IE.
Since we can control the headers, and the meta element only works in
certain conditions, we should set this as a header instead. To make sure
this is always set, we can add a servlet filter that adds that header.
For performance (smaller responses), we can only add it if the request
comes from an IE browser.
= imagetoolbar =
<meta http-equiv="imagetoolbar" content="no"/>
it disables the toolbar that comes up when you mouse over an image in
MSIE.
Same, I propose to add a conditional comment:
<!--[if IE]>
<meta http-equiv="imagetoolbar" content="no"/>
<![endif]-->
This is no longer needed, XWiki doesn't support IE6 anymore, and newer
versions don't have an image toolbar.
Simply remove it.
= Content-Script-Type =
<meta http-equiv="Content-Script-Type" content="text/javascript"
/>
It defines the default scripting language that is used for intrinsic
events
(e.g. onmouseover attributes).
This tag has been deprecated, and there is nothing to replace it. I don't
think this tag is very useful because most of the browsers assume that an
intrinsic event will be handled by javascript. Actually I did not know
this
meta tag before today and my inline javascript
did always work!
So I propose to just remove it.
This was added since there's an accessibility rule that mandates it.
Since it's an http-equiv, we should add this as a HTTP header as well.
= Distribution =
<meta name="distribution" content="GLOBAL" /> (from
XWiki.XWikiPreferences)
It actually defines either the website should be
considered as public or
local (see See http://www.metatags.info/meta_name_distribution).
I propose to remove it.
This one is ancient, IIRC it was there before my time. I doubt it has
any relevance, and since most XWiki instances are private intranets (I
guess?), "global" is wrong as a default value, yet I doubt anyone ever
changes it. +1 for removing it.
= reply-to =
<meta http-equiv="reply-to" content="" /> (from
XWiki.XWikiPreferences)
To be useful, the content should not be empty, so the administrator
should
set it. Moreover, it is very not well-known, and
it could be a problem
since the spam bots can read it.
I propose to remove it. If the administrator wants it, she can put it in
the preferences, with the proper value filled.
That's not a valid header... Remove it.
= language =
<meta name="language" content="en" /> (from
XWiki.XWikiPreferences)
It is actually redundant with <html lang="en">.
I propose to remove it.
Remove it.
What do you think?
Thanks,
--
Sergiu Dumitriu
http://purl.org/net/sergiu
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
3624
days inactive
3630
days old
4 comments
2 participants
participants (2)
-
Guillaume "Louis-Marie" Delhumeau -
Sergiu Dumitriu