Okay sounds good. We will hold off then. (Not that I like Edge any more than IE though … Ha ha ha …)
Thanks Christian. ~ Laz Peterson Paravis, LLC > On Aug 25, 2016, at 12:41 AM, Christian Mack (christian.m...@uni-konstanz.de) > <users@sogo.nu> wrote: > > Hello > > Am 25.08.2016 um 00:54 schrieb "Laz C. Peterson" (l...@paravis.net > <mailto:l...@paravis.net>): >> Hey there Christian, >> >> So the Angular/IE issues are affecting everyone, yes? > > Everyone using V3 of SOGo. > As V3 is based on Angular. > > >> I am so surprised searching in SOGo lists and documentation that there is >> not more squabble about how bad IE >> runs the SOGo web interface. Or I guess nobody is using IE … ? >> > > Partly. > I for one only know a handful of people using IE (we have ~18000 users). > And when using SOGo V2 you don't have that problem at all, as it is not > based on Angular. > >> Maybe it is time for an explicit “SOGo does not support Internet Explorer” >> message when the user loads on IE. >> > > It supports it, but only very slow ;-) > And Angular will support Edge better in the long run. > > > Kind regards. > Christian Mack > >> Bummer all the way around. >> >> ~ Laz Peterson >> Paravis, LLC >> >>> On Aug 24, 2016, at 7:40 AM, Christian Mack >>> (christian.m...@uni-konstanz.de) <users@sogo.nu> wrote: >>> >>> Hello >>> >>> Angular is provided/developed by Google delelopers. >>> They decided to not optimize it for IE. >>> >>> Before next year they don't add any new features to the current stable >>> Angular version, because they are concentrating on the next Version. >>> So there is nothing we or Inverse can do. >>> >>> >>> Kind regards, >>> Christian Mack >>> >>> Am 23.08.2016 um 20:23 schrieb Galian Kile >>> (julio.sandoval.teemkurr...@gmail.com >>> <mailto:julio.sandoval.teemkurr...@gmail.com> >>> <mailto:julio.sandoval.teemkurr...@gmail.com >>> <mailto:julio.sandoval.teemkurr...@gmail.com>>): >>>> Hello All, >>>> >>>> Just following up to see if anyone has any insight on this. I am still at a >>>> standstill. The performance is unbearable and we really want to take >>>> advantage of all the new features. Even though IE has only 5% of the >>>> browser marketshare, that’s still 5% of users that SOGo is entirely >>>> unusable for. >>>> >>>> Thank you all for your time. >>>> >>>> Any help is appreciated. >>>> >>>> >>>> On Mon, Aug 22, 2016 at 7:24 AM, "Laz C. Peterson" <users@sogo.nu >>>> <mailto:users@sogo.nu>> wrote: >>>> >>>>> Ok, just tested with Edge … Definitely not as painful, but most definitely >>>>> still unacceptably slow. >>>>> >>>>> Microsoft really has their priorities twisted inside out. I can’t >>>>> understand how every other browser has no issues, but theirs is a total >>>>> train wreck. >>>>> >>>>> Any help or suggestion would be most greatly appreciated. Thank you all. >>>>> >>>>> ~ Laz Peterson >>>>> Paravis, LLC >>>>> >>>>> On Aug 22, 2016, at 7:09 AM, Laz C. Peterson (l...@paravis.net >>>>> <mailto:l...@paravis.net>) < >>>>> users@sogo.nu <mailto:users@sogo.nu>> wrote: >>>>> >>>>> Anyone have any insight to this? >>>>> >>>>> We’ve been doing a bit more testing with IE, and wow it is really >>>>> discouraging how much IE struggles. I don’t know much about debugging >>>>> webpage performance issues, so I couldn’t say whether the issue is related >>>>> to javascript or CSS. But I am very surprised nobody else has seen these >>>>> issues with SOGo version 3. >>>>> >>>>> A bit of Google searching brings a lot of IE/Angular issue results, but >>>>> that’s all a bit beyond me. >>>>> >>>>> Developers, is there something that can be disabled for IE-specific >>>>> clients? (I have not tested with Edge, but will do that today.) >>>>> >>>>> Though it doesn’t seem appropriate, but should a bug request be filed >>>>> submitted for something like this? >>>>> >>>>> ~ Laz Peterson >>>>> Paravis, LLC >>>>> >>>>> On Aug 19, 2016, at 9:45 AM, Laz C. Peterson (l...@paravis.net >>>>> <mailto:l...@paravis.net>) < >>>>> users@sogo.nu <mailto:users@sogo.nu>> wrote: >>>>> >>>>> Hey there — >>>>> >>>>> We have this issue as well. The performance in IE11 is unbelievably slow, >>>>> and it is completely unusable. We do not let our clients use Chrome or >>>>> Firefox, as the policies are not easy to enforce. And we definitely don’t >>>>> use IE because we love IE, in fact I really don’t like it at all … But >>>>> that >>>>> is our only option based on client requirements. >>>>> >>>>> So until we can figure out what will improve performance, we can’t >>>>> upgrade. And we would really like to, since the new interface is really >>>>> well done. >>>>> >>>>> We went live for a test run yesterday, and between the IE performance >>>>> issues and missing calendar events, the day did not go well. >>>>> >>>>> Please let me know if you figure anything out. >>>>> >>>>> ~ Laz Peterson >>>>> Paravis, LLC >>>>> >>>>> On Aug 19, 2016, at 9:34 AM, Galian Kile (julio.sandoval.teemkurrupt@ >>>>> gmail.com <http://gmail.com/>) <users@sogo.nu <mailto:users@sogo.nu>> >>>>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> We are having issues with Internet Explorer 11 and Angular JS. >>>>> >>>>> We have noticed that any other browser (Chrome, Safari, Firefox), the >>>>> website performs normal. >>>>> When ran on IE11, it has a massive lag. Switching between sections can >>>>> take over 8 seconds. >>>>> >>>>> Has anyone encountered this? What type of fixes are there to enhance the >>>>> performance of Angular JS in IE11? >>>>> >>>>> Thanks >>>>> >>>>> -- >>>>> Julio Sandoval > > -- > Christian Mack > Universität Konstanz > Kommunikations-, Informations-, Medienzentrum (KIM) > Abteilung Basisdienste > 78457 Konstanz > +49 7531 88-4416 -- users@sogo.nu https://inverse.ca/sogo/lists
