I added a v1 of this to the wiki
at https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix
Of course, feel free to make comments and edits :)
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group
Great, thanks Tom. I just reworked the page a bit into a table to help make
the information more quickly findable by readers.
Hope this suits you and others.
2014-08-26 15:06 GMT+02:00 Tom Fennelly tom.fenne...@gmail.com:
I added a v1 of this to the wiki at
On 26.08.2014, at 15:06, Tom Fennelly tom.fenne...@gmail.com wrote:
I added a v1 of this to the wiki at
https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix
Of course, feel free to make comments and edits :)
Any particular reason you list Firefox ESR as L2?
--
You
That's great, thanks Baptiste.
On Tuesday, August 26, 2014 2:26:18 PM UTC+1, Baptiste Mathus wrote:
Great, thanks Tom. I just reworked the page a bit into a table to help
make the information more quickly findable by readers.
Hope this suits you and others.
2014-08-26 15:06 GMT+02:00 Tom
Good question... no reason other than being hasty. I'll update it and make
it L1. In fact... is there a need to mention it specifically?
On Tuesday, August 26, 2014 6:14:05 PM UTC+1, Daniel Beck wrote:
On 26.08.2014, at 15:06, Tom Fennelly tom.fe...@gmail.com javascript:
wrote:
I
On 26.08.2014, at 19:39, Tom Fennelly tom.fenne...@gmail.com wrote:
Good question... no reason other than being hasty. I'll update it and make
it L1. In fact... is there a need to mention it specifically?
Well, it's outdated by ~3 months on average compared to the latest, so telling
On 07.08.2014, at 22:36, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
I think what we are after is 3 tiers:
- first class UX (we should aim to proactively fix these browsers and provide
an equal UX across all) - UI testing failures here are considered major UI
bugs
- best
Right, I think this is a good approach + the caveats Daniel suggests. I
think the policy around accepting patches should be along the lines of the
level of guarantee we plan to offer e.g. for no guarantee on support we
also offer no guarantee re accepting patches i.e. if we can reasonably
It would be best to try to degrade gracefully on older or less
functional browsers. If the page looks ugly, fine. If some JavaScript
tricks do not work, fine, so long as there is some other way to
accomplish the same task.
--
You received this message because you are subscribed to the Google
On Thursday, 7 August 2014, Jesse Glick jgl...@cloudbees.com wrote:
It would be best to try to degrade gracefully on older or less
functional browsers. If the page looks ugly, fine. If some JavaScript
tricks do not work, fine, so long as there is some other way to
accomplish the same task.
From a tools perspective I have always found browserling to be very useful.
Free and open source
On Aug 7, 2014 1:36 PM, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
On Thursday, 7 August 2014, Jesse Glick jgl...@cloudbees.com wrote:
It would be best to try to degrade gracefully
Hi Emeric. Thanks for the response. +1 to everything you said there.
On Friday, August 1, 2014 9:37:54 AM UTC+1, evernat wrote:
Hi Tom,
In my opinion, we should not try to support IE8 in UI refresh, because it
would be foolish for a user to still use IE8 even on WinXP.
Perhaps some
+1
The browser support matrix would be great. In addition to IE, it will allow
to limit the fun with custom browsers. Firefox, Chrome, Safari and IE
would be enough.
Unfortunately, many plugins have their own browser compatibility issues
(especially with IE11).
It could be useful to somehow
Hi Tom,
In my opinion, we should not try to support IE8 in UI refresh, because it
would be foolish for a user to still use IE8 even on WinXP.
Perhaps some slow companies still pretend that IE8 is their mandatory
browser [1] (and never respect that themselves). But in my opinion, your UI
14 matches
Mail list logo
