Not sure what this could be related to, but since upgrading to v2019 I’ve been getting this error occasionally:
This is when using PHP 7.3 - not yet sure if it happens with v7.2, but I’ve never come across it before in v2018
Also, a totally separate issue, I’m occasionally having problems placing the cursor in text fields, most of the time it works fine and I can type into them as normal, but occasionally when I click into a text field, the cursor doesn’t appear and it’s impossible to type. The only way to get it to work again is by closing my app and restarting the exe. When the problem occurs, it affects all text fields within the entire app, even those on totally separate pages.
Could this new setting in V2019 be anything to do with it?:
By default, internal resources cannot be downloaded anymore (for instance, Download menu on default HTML5 video player). You can allow downloads by setting the global variable exointdownload to 1 at runtime (search in documentation for example)."
Any clues?
EDIT: So regarding the text field issue, I’ve found a way to reproduce it & think it might be something to do with the way the new version of cef hadles certain javascript functions - I could be wrong, but I’ll report back after more testing…
This error message is the same as you got previously (index out of bounds). Instead, we replaced it.
Looks also like that the CEF version we used had some bugs, as an updated CEF has been released since. We’ll integrate it to the next update 2019.1.
So is this possibly the cause of the text area focus issue - or should I investigate further and report back with more info? - apart from upgrading to php7.3, nothing has changed in my code since v2018.3 which worked fine.
@gdgsupport Okay, while I can easily reproduce the text field issue here, because there’s so much going on in my app I still haven’t had time to pinpoint exactly what’s causing it - I will track it down and let you know as soon as I can.
However, what I can tell you so far is that to resolve the problem all I have to do is click away from the apps main window on the desktop then click back to the app and text field focus begins to work again as expected.
I’ve figured it out… there may be other ways the problem could occur, but this is a basic example where a javascript alert causes the problem…
This code should reproduce the issue:
Compile the code and try to type in textarea - at first it will work fine, then click the button to trigger the JS alert message, then close the message and try get focus on the textarea - it won’t work.
The only way to get focus back is by clicking away from the window, and back again and it will begin working
Hopefully they’ll track it down soon, from reading through other bug reports it looks like a few of them could be related.
In my case it’s not a complete showstopper, I only use alerts for occasional debugging, and now I know what to do I can easily click away from the window and back again and everything’s okay - but in some people’s apps that might not be the case - it affects confirm dialogs too.
I’ve now posted an actual HTML file that should reproduce the issue on Win7 to the bug report thread - but not yet tested on Win 8 or 10 - would be good if somebody here could try to reproduce on different systems.
@gdgsupport Regarding the Exchange File Empty error - you mentioned the Index Out Of Bounds error message was replaced with Exchange File Empty - what does “Exchange File Is Empty” mean? - I still get the error occasionally, but hard to say exactly what’s causing it - although it’s possibly still related to the technique I use to display images from a users PC here ?.
Fixed in master revision f85816f, 3683 branch revision 59d1f01 and 3626 branch revision ad428f3.
Tested in the latest testclient app, and all good at this end.
@gdgsupport Do you have a timeframe for the next ExeOut update? and would be great if you could let me know what the “Exchange File is Empty” error means - I’m still looking for clues to track down the cause of the issue!
Just to clarify, regarding the Exchange File Empty error; is that likely an issue with ExeOut at your end then or should I contiunue trying to find a consistent way to reproduce it here? One thing I have noticed is that it seems to be more likely to happen upon first run of a freshly compiled exe where I’d first cleared the CEF and PHP runtime cache via the button in General Settings.
That’s not to say it doesn’t happen at other times too (which I think may be related to the image display technique I use), but it does seem more likely to occur on first run of new exe compiled after clearing the runtiume caches.
Just a quick heads up for @gdgsupport regarding the next version of ExeOut - I’ve discovered a new issue (unrelated to this thread) that affects all builds of the latest version of CEF (3626) that I’m guessing you’ll be planning use in the update.
It’s quite major for me, and I’d imagine it’s likely to affect others here too - I posted a bug report here.
Would be great if some of you could download the 3626 cef testclient and test in Windows 10 and maybe even vote on the issue so we can get it fixed as soon as poss!
