Details
-
Type: Bug
-
Status: Closed
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: EE-1.8.2.GA_P10, EE-3.3.0.GA_P06, EE-4.3.0.GA
-
Fix Version/s: EE-1.8.2.GA_P11, EE-3.3.0.GA_P07, EE-4.3.0.GA_P01
-
Component/s: Bridge
-
Labels:None
-
Environment:Chrome 73.0.3683.103
-
Support Case References:
Description
reports of problems with dispose-views with latest update of Chrome
possible issue reported:-
https://chromium.googlesource.com/chromium/src/+/ae67f3d81e68cbe54942fb187a97e39225b36b00
could be related.
Was reported that could be reproduced using WindowsScope tutorial example. I tested on my Mac with latest Chrome and could not reproduce with either 3.3.0_P06 or 4.3.0_EE versions....so wondering if this is a windows/Chrome issue?
Will also attach other relevant info from support cases to this Jira.
possible issue reported:-
https://chromium.googlesource.com/chromium/src/+/ae67f3d81e68cbe54942fb187a97e39225b36b00
could be related.
Was reported that could be reproduced using WindowsScope tutorial example. I tested on my Mac with latest Chrome and could not reproduce with either 3.3.0_P06 or 4.3.0_EE versions....so wondering if this is a windows/Chrome issue?
Will also attach other relevant info from support cases to this Jira.
Use Navigator.sendBeacon native function when available to avoid using a synchronous XHR.
Chrome will not issue a XHR request anymore when is issued right before the page unloads. Also see https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API/Using_the_Beacon_API.