11 Mar
2014
11 Mar
'14
3:12 p.m.
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for IE9,
so we should also adjust our support strategy by supporting newer browsers
(IE10, IE11) and dropping the support for old ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar the
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query support.
IE8 doesn't has support for media query natively, we would need Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
11 Mar
11 Mar
3:31 p.m.
-0 at this stage from me. IMO we need to first question our xwiki users and do a more
thorough survey to understand who’s using XWiki with IE8 and how they’d feel if we dropped
support for it.
According to http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar, IE8
is one of the top IE versions used by users so it seems a bit early to take a decision
right now about this.
Since XWiki is an Enterprise software it’s all the more important to verify that
Enterprises are ready to drop IE8 before taking that decision IMO.
Thanks
-Vincent
On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica) (valicac(a)gmail.com) wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for IE9,
so we should also adjust our support strategy by supporting newer browsers
(IE10, IE11) and dropping the support for old ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar the
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query support.
IE8 doesn't has support for media query natively, we would need Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5:11 p.m.
I should agree with Vincent. The reason IE8 is still in use is mostly
because it is the latest MS browser for Windows XP. I know that XP will be
EoL very soon, but while MS has taken that decision, the current market
share of Windows XP is still quite large. I hope the EoL will speed up a
bit the migration process, but not enough for dropping IE8 now.
It could be a project for the 7.x release if the regression of IE8 is
confirmed.
While it requires a bit of adaptation, bootstrap 3 support IE8, so I do not
see why we would need to stop supporting IE8 for the new skin. Obviously,
the design under IE8 will be a bit degraded. Supporting IE8 does not
prevent us from using latest HTML5/CSS3 features, if IE8 degrade nicely.
And there is no real need to be responsive on IE8, since no mobile device
use it.
So I am currently -1 for this change.
Thanks,
PS: I am far more concerned by the JS conflict issue we have between
Bootstrap, JQuery and Prototype.
On Tue, Mar 11, 2014 at 3:31 PM, vincent(a)massol.net <vincent(a)massol.net>wrote;wrote:
-0 at this stage from me. IMO we need to first
question our xwiki users
and do a more thorough survey to understand who’s using XWiki with IE8 and
how they’d feel if we dropped support for it.
According to
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar,
IE8 is one of the top IE versions used by users so it seems a bit early to
take a decision right now about this.
Since XWiki is an Enterprise software it’s all the more important to
verify that Enterprises are ready to drop IE8 before taking that decision
IMO.
Thanks
-Vincent
On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica) (valicac(a)gmail.com)
wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for IE9,
so we should also adjust our support strategy by supporting newer browsers
(IE10, IE11) and dropping the support for old ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-barthe
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query support.
IE8 doesn't has support for media query natively, we would need Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
6:09 p.m.
2014-03-11 17:11 GMT+01:00 Denis Gervalle <dgl(a)softec.lu>lu>:
I should agree with Vincent. The reason IE8 is still
in use is mostly
because it is the latest MS browser for Windows XP. I know that XP will be
EoL very soon, but while MS has taken that decision, the current market
share of Windows XP is still quite large. I hope the EoL will speed up a
bit the migration process, but not enough for dropping IE8 now.
It could be a project for the 7.x release if the regression of IE8 is
confirmed.
While it requires a bit of adaptation, bootstrap 3 support IE8, so I do not
see why we would need to stop supporting IE8 for the new skin. Obviously,
the design under IE8 will be a bit degraded. Supporting IE8 does not
prevent us from using latest HTML5/CSS3 features, if IE8 degrade nicely.
And there is no real need to be responsive on IE8, since no mobile device
use it.
Just for your information:
IE8 cannot degrade nicely without Respond.js. Because without media
queries, it will use the "mobile first" version of bootstrap, which means
that everything will be displayed like if they were on a mobile phone.
Anyway, if we can integrate Respond.js too, it is not a problem anymore.
Louis-Marie
So I am currently -1 for this change.
Thanks,
PS: I am far more concerned by the JS conflict issue we have between
Bootstrap, JQuery and Prototype.
On Tue, Mar 11, 2014 at 3:31 PM, vincent(a)massol.net <vincent(a)massol.net
wrote:
-0 at this stage from me. IMO we need to first
question our xwiki users
and do a more thorough survey to understand who's using XWiki with IE8
and
how they'd feel if we dropped support for
it.
According to
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar,
IE8 is one of the top IE versions used by users so it seems a bit early
to
take a decision right now about this.
Since XWiki is an Enterprise software it's all the more important to
verify that Enterprises are ready to drop IE8 before taking that decision
IMO.
Thanks
-Vincent
On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica) (valicac(a)gmail.com
)
wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for
IE9,
so we should also adjust our support strategy by
supporting newer
browsers
(IE10, IE11) and dropping the support for old
ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-barthe
most popular IE browsers are IE10 (8.48%) and IE8
(7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query
support.
IE8 doesn't has support for media query
natively, we would need
Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12 Mar
12 Mar
8:05 a.m.
Another solution would be to support IE8 only for Colibri and to make
Flamingo support IE9+.
Thanks,
Caty
On Tue, Mar 11, 2014 at 7:09 PM, Guillaume "Louis-Marie" Delhumeau <
gdelhumeau(a)xwiki.com> wrote:
2014-03-11 17:11 GMT+01:00 Denis Gervalle
<dgl(a)softec.lu>lu>:
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar,
decision
http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
I should agree with Vincent. The reason IE8 is
still in use is mostly
because it is the latest MS browser for Windows XP. I know that XP will
be
EoL very soon, but while MS has taken that
decision, the current market
share of Windows XP is still quite large. I hope the EoL will speed up a
bit the migration process, but not enough for dropping IE8 now.
It could be a project for the 7.x release if the regression of IE8 is
confirmed.
While it requires a bit of adaptation, bootstrap 3 support IE8, so I do
not
see why we would need to stop supporting IE8 for
the new skin. Obviously,
the design under IE8 will be a bit degraded. Supporting IE8 does not
prevent us from using latest HTML5/CSS3 features, if IE8 degrade nicely.
And there is no real need to be responsive on IE8, since no mobile device
use it.
Just for your information:
IE8 cannot degrade nicely without Respond.js. Because without media
queries, it will use the "mobile first" version of bootstrap, which means
that everything will be displayed like if they were on a mobile phone.
Anyway, if we can integrate Respond.js too, it is not a problem anymore.
Louis-Marie
So I am currently -1 for this change.
Thanks,
PS: I am far more concerned by the JS conflict issue we have between
Bootstrap, JQuery and Prototype.
On Tue, Mar 11, 2014 at 3:31 PM, vincent(a)massol.net <vincent(a)massol.net
users
wrote:
> -0 at this stage from me. IMO we need to first question our xwiki and do a
more thorough survey to understand who's using XWiki with IE8
and
> how they'd feel if we dropped support for it.
>
> According to
> IE8 is
one of the top IE versions used by users so it seems a bit early
to
> take a decision right now about this.
>
> Since XWiki is an Enterprise software it's all the more important to
> verify that Enterprises are ready to drop IE8 before taking that > IMO.
>
> Thanks
> -Vincent
> On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica) (
valicac(a)gmail.com
)
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-barthe
wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for
IE9,
so we should also adjust our support strategy by
supporting newer
browsers
(IE10, IE11) and dropping the support for old
ones (IE8, IE9).
According to Statcounter for the last 6 month period
> most popular IE browsers are IE10 (8.48%)
and IE8 (7.98%).
>
> While the market share is not neglectable there is something you need
to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query
support.
IE8 doesn't has support for media query
natively, we would need
Respond.js
> [2] to enable it.
> While this solution exist, 6.x will be ready at the end of 2014 when I
> suspect the market share for IE8 will drop.
>
> Additional to not having media query support, there are other CSS3
> properties and HTML5 elements that are not fully supported by IE8
> (border-radius, box-shadow, transition, etc.).
>
> This is my +1 to drop support for IE8 in 6.x
>
> Thanks,
> Caty
>
> [1] [2]
https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:36 a.m.
It seems to me this is a call for a census. Indeed as Vincent points out,
Enterprise can't upgrade really anything overnight... but we must beware
of user relationships which are not mutually beneficial.
If (for example) there is only one user who requires IE8 support and it
costs an additional 30 man/hours per month to continue support, IMO the
one user who requires it owes that time to the project.
I'm going to abstain from voting until I know:
#1 how many users need this (best if we can value the users in terms of
how much they contribute to the project, either directly or through
support contracts with developers who contribute).
#2 how many man/hours per month will be required in order to keep up IE8
support.
Does this seem logical?
Caleb
On 03/11/2014 03:12 PM, Ecaterina Moraru (Valica) wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for IE9,
so we should also adjust our support strategy by supporting newer browsers
(IE10, IE11) and dropping the support for old ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar the
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query support.
IE8 doesn't has support for media query natively, we would need Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
8:46 p.m.
Hi,
2014-03-12 10:36 GMT+01:00 Caleb James DeLisle <cjd(a)hyperboria.ca>ca>:
It seems to me this is a call for a census. Indeed as
Vincent points out,
Enterprise can't upgrade really anything overnight... but we must beware
of user relationships which are not mutually beneficial.
If (for example) there is only one user who requires IE8 support and it
costs an additional 30 man/hours per month to continue support, IMO the
one user who requires it owes that time to the project.
I'm going to abstain from voting until I know:
#1 how many users need this (best if we can value the users in terms of
how much they contribute to the project, either directly or through
support contracts with developers who contribute).
That doesn't seem really logical to me ... If 10% users contribute and use
IE10, but 90% of users do not contribute but use IE8, you would be ready to
cut yourselves from 90% of your users ?
#2 how many man/hours per month will be required in order to keep up IE8
support.
IMO that's the only really important point for you, I would say. It is
known that IE8 is 4 years old, less and less used and so on. If you can't
affort supporting it, I think any user can understand that. If workload is
very limited, then you have advantage to keep supporting it. And if some
users really need IE8, they can add missing support through contribution I
suppose (given, it's not of overwhelming complexity, of course). But you
could also stop supporting IE8 AND integrate Respond.js as a "best effort"
approach, seems almost independant to me (depending, of course, on the cost
of integrating Respond.js).
Does this seem logical?
Caleb
On 03/11/2014 03:12 PM, Ecaterina Moraru (Valica) wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for
IE9,
so we should also adjust our support strategy by
supporting newer
browsers
(IE10, IE11) and dropping the support for old
ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-barthe
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query
support.
IE8 doesn't has support for media query
natively, we would need
Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
14 Mar
14 Mar
10:30 a.m.
A possible thought for the future:
During installation and in Admin panel:
[x] Help developers improve XWiki by sending anonymized statistics ?
Thanks,
Caleb
On 03/12/2014 08:46 PM, Jeremie BOUSQUET wrote:
Hi,
2014-03-12 10:36 GMT+01:00 Caleb James DeLisle <cjd(a)hyperboria.ca>ca>:
It seems to me this is a call for a census.
Indeed as Vincent points out,
Enterprise can't upgrade really anything overnight... but we must beware
of user relationships which are not mutually beneficial.
If (for example) there is only one user who requires IE8 support and it
costs an additional 30 man/hours per month to continue support, IMO the
one user who requires it owes that time to the project.
I'm going to abstain from voting until I know:
#1 how many users need this (best if we can value the users in terms of
how much they contribute to the project, either directly or through
support contracts with developers who contribute).
That doesn't seem really logical to me ... If 10% users contribute and use
IE10, but 90% of users do not contribute but use IE8, you would be ready to
cut yourselves from 90% of your users ?
#2 how many man/hours per month will be required in order to keep up IE8
support.
IMO that's the only really important point for you, I would say. It is
known that IE8 is 4 years old, less and less used and so on. If you can't
affort supporting it, I think any user can understand that. If workload is
very limited, then you have advantage to keep supporting it. And if some
users really need IE8, they can add missing support through contribution I
suppose (given, it's not of overwhelming complexity, of course). But you
could also stop supporting IE8 AND integrate Respond.js as a "best effort"
approach, seems almost independant to me (depending, of course, on the cost
of integrating Respond.js).
Does this seem logical?
Caleb
On 03/11/2014 03:12 PM, Ecaterina Moraru (Valica) wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for
IE9,
so we should also adjust our support strategy by
supporting newer
browsers
(IE10, IE11) and dropping the support for old
ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-barthe
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query
support.
IE8 doesn't has support for media query
natively, we would need
Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2 May
2 May
8:54 a.m.
Some recent stats:
http://thenextweb.com/insider/2014/05/01/ie11-market-share-passes-ie10-ie9-…
So IE8 is 20% in IE browsers, and IE is 57% of total browser shares.
Good news is that IE11 is growing up quickly :)
Thanks
-Vincent
On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica)
(valicac@gmail.com(mailto:valicac@gmail.com)) wrote:
Hi devs,
This mail is about voting to drop support for IE8 in 6.x cycle.
The issue is more complicated, since according to our 'Browser Support
Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
Chrome (+ Safari5).
IE8 was released in March 2009 (4 years ago)
IE9 - March 2011 (2 years ago)
IE10 - Sept 2012 (17 months ago)
IE11 - Oct 2013 (4 month ago)
With the release of IE11 some companies also dropped their support for IE9,
so we should also adjust our support strategy by supporting newer browsers
(IE10, IE11) and dropping the support for old ones (IE8, IE9).
According to Statcounter for the last 6 month period
http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar the
most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
While the market share is not neglectable there is something you need to
consider:
In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
responsive. In order to assure responsiveness we need media query support.
IE8 doesn't has support for media query natively, we would need Respond.js
[2] to enable it.
While this solution exist, 6.x will be ready at the end of 2014 when I
suspect the market share for IE8 will drop.
Additional to not having media query support, there are other CSS3
properties and HTML5 elements that are not fully supported by IE8
(border-radius, box-shadow, transition, etc.).
This is my +1 to drop support for IE8 in 6.x
Thanks,
Caty
[1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
[2] https://github.com/scottjehl/Respond
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
8:59 a.m.
On 2 May 2014 at 08:54:38, vincent(a)massol.net
(vincent@massol.net(mailto:vincent@massol.net)) wrote:
Some recent stats:
http://thenextweb.com/insider/2014/05/01/ie11-market-share-passes-ie10-ie9-…
So IE8 is 20% in IE browsers, and IE is 57% of total browser shares.
"IE8 fell 0.29 percentage points, but it’s still the world’s most popular browser at
20.85 percent”
Thanks
-Vincent
Good news is that IE11 is growing up quickly :)
Thanks
-Vincent
On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica)
(valicac@gmail.com(mailto:valicac@gmail.com)) wrote:
> Hi devs,
>
> This mail is about voting to drop support for IE8 in 6.x cycle.
>
> The issue is more complicated, since according to our 'Browser Support
> Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
> Chrome (+ Safari5).
>
> IE8 was released in March 2009 (4 years ago)
> IE9 - March 2011 (2 years ago)
> IE10 - Sept 2012 (17 months ago)
> IE11 - Oct 2013 (4 month ago)
>
> With the release of IE11 some companies also dropped their support for IE9,
> so we should also adjust our support strategy by supporting newer browsers
> (IE10, IE11) and dropping the support for old ones (IE8, IE9).
>
> According to Statcounter for the last 6 month period
> http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar the
> most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
>
> While the market share is not neglectable there is something you need to
> consider:
> In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
> responsive. In order to assure responsiveness we need media query support.
> IE8 doesn't has support for media query natively, we would need Respond.js
> [2] to enable it.
> While this solution exist, 6.x will be ready at the end of 2014 when I
> suspect the market share for IE8 will drop.
>
> Additional to not having media query support, there are other CSS3
> properties and HTML5 elements that are not fully supported by IE8
> (border-radius, box-shadow, transition, etc.).
>
> This is my +1 to drop support for IE8 in 6.x
>
> Thanks,
> Caty
>
> [1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
> [2] https://github.com/scottjehl/Respond
9:02 a.m.
On 2 May 2014 at 08:59:11, vincent(a)massol.net
(vincent@massol.net(mailto:vincent@massol.net)) wrote:
On 2 May 2014 at 08:54:38, vincent(a)massol.net
(vincent@massol.net(mailto:vincent@massol.net)) wrote:
But also:
"IE8 fell 0.29 percentage points, but it’s still the world’s most popular browser at
20.85 percent. IE11 continues to mainly steal market share from IE10 and IE9, since
Windows XP users can’t upgrade past IE8, but now that support has ended for the ancient
OS, maybe that trend will finally change.”
Let’s hope that the fall will be brutal now that XP’s support has ended… :)
Thanks
-Vincent
Some recent stats:
http://thenextweb.com/insider/2014/05/01/ie11-market-share-passes-ie10-ie9-…
So IE8 is 20% in IE browsers, and IE is 57% of total browser shares.
"IE8 fell 0.29 percentage points, but it’s still the world’s most popular browser at
20.85 percent” Thanks
-Vincent
Good news is that IE11 is growing up quickly :)
Thanks
-Vincent
On 11 Mar 2014 at 15:13:04, Ecaterina Moraru (Valica)
(valicac@gmail.com(mailto:valicac@gmail.com)) wrote:
> Hi devs,
>
> This mail is about voting to drop support for IE8 in 6.x cycle.
>
> The issue is more complicated, since according to our 'Browser Support
> Strategy' [1] we are supporting IE8, IE9 and the latest versions of FF,
> Chrome (+ Safari5).
>
> IE8 was released in March 2009 (4 years ago)
> IE9 - March 2011 (2 years ago)
> IE10 - Sept 2012 (17 months ago)
> IE11 - Oct 2013 (4 month ago)
>
> With the release of IE11 some companies also dropped their support for IE9,
> so we should also adjust our support strategy by supporting newer browsers
> (IE10, IE11) and dropping the support for old ones (IE8, IE9).
>
> According to Statcounter for the last 6 month period
> http://gs.statcounter.com/#browser_version-ww-monthly-201309-201402-bar the
> most popular IE browsers are IE10 (8.48%) and IE8 (7.98%).
>
> While the market share is not neglectable there is something you need to
> consider:
> In 6.x we want to add a new skin: Flamingo. Ideally this skin should be
> responsive. In order to assure responsiveness we need media query support.
> IE8 doesn't has support for media query natively, we would need Respond.js
> [2] to enable it.
> While this solution exist, 6.x will be ready at the end of 2014 when I
> suspect the market share for IE8 will drop.
>
> Additional to not having media query support, there are other CSS3
> properties and HTML5 elements that are not fully supported by IE8
> (border-radius, box-shadow, transition, etc.).
>
> This is my +1 to drop support for IE8 in 6.x
>
> Thanks,
> Caty
>
> [1] http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy
> [2] https://github.com/scottjehl/Respond
3790
days inactive
3842
days old
10 comments
6 participants
participants (6)
-
Caleb James DeLisle -
Denis Gervalle -
Ecaterina Moraru (Valica) -
Guillaume "Louis-Marie" Delhumeau -
Jeremie BOUSQUET -
vincent＠massol.net