Hi, I have a problem that only arises in IE shown here in what appears to be in Cincoms Appex Core.js. Any ideas ?? Regards, @+Maarten, PS this is 8.01 _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Maybe the problem is the drawbacks of the MS implementation of the event handler as described in this article: That notably states:
where our Appex JavascriptClass states: addEventListener(type, listener, useCapture) { // Simulate the EventTarget API return this.eventTarget().addEventListener(type, listener, useCapture || false); } @+Maarten,
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Maarten,
I successfully retested our EventSource demo in vw8.0.1 and IE11. The server was on Windows 7. Could you load AppeX-Examples and run Event-Source demo? It would be interesting to know if you can run it. Tamara Kogan Smalltalk Development Cincom Systems -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Maarten Mostert Sent: Tuesday, May 19, 2015 12:07 PM To: VW NC Subject: Re: [vwnc] Appex problem with IE11 Maybe the problem is the drawbacks of the MS implementation of the event handler as described in this article: http://www.quirksmode.org/js/events_advanced.html That notably states: 1. The event handling function is referenced, not copied, so the thiskeyword <http://www.quirksmode.org/js/this.html> always refers to the window and is completely useless. where our Appex JavascriptClass states: addEventListener(type, listener, useCapture) { // Simulate the EventTarget API return this.eventTarget().addEventListener(type, listener, useCapture || false); } @+Maarten, Le 19 mai 2015 à 12:54, Maarten Mostert <[hidden email]> a écrit : Hi, I have a problem that only arises in IE shown here in what appears to be in Cincoms Appex Core.js. https://www.dropbox.com/s/p46rz74t7m5l1fy/2015-05-19_12-45-28.png?dl=0 Any ideas ?? Regards, @+Maarten, PS this is 8.01 _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hi,
Sorry for late reply but actually I get blank pages when running the event source demo with IE11. This happens both on Windows 8.1 on Windows 7 and with both VW 8.0 and 8.01. I completely reinstalled both 8.0 and 8.01 and it happens in a vanilla image loading Appex tools, Sioux Tools and the examples. This is what I see on Windows 8.1 And on windows 7 Notice that the following gives a white page within IE, you need to refresh to see the form ?? which is not so nice … ExternalWebBrowser open: 'http://stakepoint.com/getLicense/' Regards, @+Maarten
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Maarten, what do you see in the ‘Network’ tab when loading the example? You should see a bunch of _appex_postClientEvent requests, then _appex_getServerEvents?sessionId=…., and then message-event?sessionId=… . Do they return at all, are they just waiting for a response? That’s what it kind of should look like - an EventStream keeps the connection open and just keeps reading event messages from it.
IE is notoriously non-compliant with specifications, and doesn’t have native support for EventStream - all the other mainstram browsers do. AppeX contains an EventStream emulator for IE that we have tested in our environments, but we don’t know what other factors may affect its functionality. Jerry Kott Smalltalk Development, Cincom Systems PGP fingerprint: 07D0987E142BE7D39A3F99D71DAF1CF392A9236F On 24-05-2015, at 11:24 AM, Maarten Mostert <[hidden email]> wrote:
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc signature.asc (507 bytes) Download Attachment |
Jerry and Tamara,
Please find enclosed 2 videos.
The first one is on Windows 7, actually the event-source demo works but only if I hit the refresh button otherwise the page stays white.
The second one starts on Mac creating a new image with the example and running it through Chrome all is oké. I then switch to Windows 8.1 on virtual box opening the same image that just worked on OSX. You can see the result is blank page first then an error when hitting refresh.
http://stakepoint.com/public/2015-05-26_21-21-54.mp4 http://stakepoint.com/public/2015-05-26_21-51-21.mp4
Hope this helps.
Regards.
Maarten MOSTERT
28 Av Alphonse Denis 83400 Hyères, France +33 676411296
Maarten, what do you see in the ‘Network’ tab when loading the example? You should see a bunch of _appex_postClientEvent requests, then _appex_getServerEvents?sessionId=…., and then message-event?sessionId=… . Do they return at all, are they just waiting for a response? That’s what it kind of should look like - an EventStream keeps the connection open and just keeps reading event messages from it.
IE is notoriously non-compliant with specifications, and doesn’t have native support for EventStream - all the other mainstram browsers do. AppeX contains an EventStream emulator for IE that we have tested in our environments, but we don’t know what other factors may affect its functionality.
Jerry Kott
Smalltalk Development, Cincom Systems PGP fingerprint: 07D0987E142BE7D39A3F99D71DAF1CF392A9236F
On 24-05-2015, at 11:24 AM, Maarten Mostert <[hidden email]> wrote:
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Maarten, we’ve been able to recreate it locally with IE11. It appears to be all in the client code (not the Smalltalk code running on the server), and is related to the combination of two factors:
1) IE does not implement EventSource natively. This is a known fact, and the AppeX framework compensates for this by creating an EventSource emulator JS class that we invoke instead. 2) The order of events after the EventSource is created in the client is different between the ‘good’ browsers and IE. This has *probably* something to do with the JS main thread event processing model, which I am not too deeply familiar with, and I’ll need to do some research. If it turns out that we need to just post an event to a queue to make sure the emulated EventSource doesn’t start its work until all the event registrations are in place, that would be great, but as I said, I have to look into it some more. If you haven’t done so already, please open a Cincom Smalltalk Support ticket for this so it can be tracked properly . Jerry Kott Smalltalk Development, Cincom Systems PGP fingerprint: 07D0987E142BE7D39A3F99D71DAF1CF392A9236F On 26-05-2015, at 1:15 PM, [hidden email] wrote:
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc signature.asc (507 bytes) Download Attachment |
Free forum by Nabble | Edit this page |