[jira] [Resolved] (ACCUMULO-4762) Synchronous JS calls are deprecated

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-4762.
-----------------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 2.0.0)

OBE in master.

> Synchronous JS calls are deprecated
> -----------------------------------
>
>                 Key: ACCUMULO-4762
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4762
>             Project: Accumulo
>          Issue Type: Bug
>          Components: monitor
>    Affects Versions: 2.0.0
>            Reporter: Michael Miller
>            Assignee: Benjamin F
>            Priority: Major
>
> All of the javascript in the Monitor sets the async flag to false before loading some values in the monitor.  Once the values are loaded, we then set the flag to true.
> {code:javascript}
> $.ajaxSetup({
>     async: false
>   });
> //... load something
> $.ajaxSetup({
>     async: true
>   });
> {code}
> This currently gives a warning in Chrome since this behavior is deprecated:
> {code:javascript}
> [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
> {code}
> This may not be a problem now but upon further investigation this could be a problem in the future.  According to the [XMLHttpRequest standard|https://xhr.spec.whatwg.org/#synchronous-flag]:
> "...Developers must not pass false for the async argument when current global object is a Window object."  I look at this as using the Asynchronous JS in a way it was not intended to be used and we could probably do this better.
> Fixing this would require some redesign of the Monitor but it would be better to do this now before releasing 2.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)