vicidial.org

Anyone noticing weird behavior with Microsoft Edge and submitting form data such as campaign detail changes? For instance values that are DISABLED posting as DISABLEDm or fields being posted as blank/null?

I think it may be with the new edge update. At first I thought it was 1 computer having the issue, then I had it on multiple workstations and thought it may be the server... Now I have had it happen on several clusters when I just happen to be using Edge instead of Chrome.

Versions I have experienced it on:
VERSION: 2.14-619a
BUILD: 170613-0851

VERSION: 2.14-645a
BUILD: 171214-2045

VERSION: 2.14-585a
BUILD: 170114-1356

We don't recommend Edge browser in combination with Vicidial. I think Matt and his team will test the proper functionality only on Chrome/Firefox and perhaps some older versions of Internet Explorer. Just go with Chrome or Firefox.

Correct, at this point we only really test with the widely-used, multi-platform Chrome and Firefox web browsers. We don't spend too much time testing with the OS-specific web browsers.

mflorell wrote:Correct, at this point we only really test with the widely-used, multi-platform Chrome and Firefox web browsers. We don't spend too much time testing with the OS-specific web browsers.

Edge is multi-os now, you can get it on iOS, MacOS, etc. lol

Anyhow just to re-iterate. This doesnt even have to do with agent interface stuff. This is admin interface changes. So there is a very high likely-hood that people will start encountering this in bulk. It is completely breaking to Vicidial since it will do stuff like disable Outbound Auto Dial in System Settings by setting it to ' ', put concurrent transfers to blank in campaign detail, etc. Anyhow just throwing it out in case other people start to see it. See link for an example.

https://drive.google.com/open?id=1CpWpCBTDQtmZgu0Cb_Yy5SCLGQhh6KY5

Acidshock - what version of Edge were you seeing this on? Also, do you run any extensions or whatever they're called on Edge?

Seems to relate to this bug:

https://developer.microsoft.com/en-us/m ... /17477791/
https://developer.microsoft.com/en-us/m ... /17358578/

Nearly 2 months now and no fix yet for such a critical issue. Well done Microsoft, as usual...

Thanks for finding and posting those okli, that certainly does nothing to improve my already dismal opinion of Microsoft-based web browsers

okli wrote:Seems to relate to this bug:

https://developer.microsoft.com/en-us/m ... /17477791/
https://developer.microsoft.com/en-us/m ... /17358578/

Nearly 2 months now and no fix yet for such a critical issue. Well done Microsoft, as usual...

Awesome job finding that! Thank you! Typical MS. I would think that a bug of this caliber would warrant an emergency hotfix.