Latest Contributions by KrisKaplan1

Prior to 4.10, Graphic client side features added to a FeatureLayer could be hidden and shown by toggling the Graphic.visible property, but this no longer appears to work in 4.10.  I have tried changing 'visible' and calling FeatureLayer.applyEdits in the 'updateFeatures' value, but this does not appear to modify the property value (nor change the visibility). I know I can remove and re-add the feature from the layer instead of toggle the visibility, but for a few reasons it would be more convenient to just toggle the visibility.  Is this still possible in 4.10? Kris ... View more

When a map is displayed, it regularly uses CPU every second or two (timers triggering requestAnimationFrames).  In the Chrome task manager, a tab with a map view constantly bounces around 5% (from zero to ten).  Unfortunately, even if the window is not active. But I would at least expect to be able to stop this CPU usage by destroying the MapView, and/or the Map.  But this does not seem to be the case.  Detaching the MapView from it's container and releasing the view and the map does not stop the CPU usage.  But perhaps I'm not stopping the map view properly (but I didn't notice any official documentation or sample about this).  I can reproduce this with a sample in the sandbox (e.g. intro-mapview) by adding the following attempt to cleanup code. setTimeout(() => {     view.container = null     view.map = null     view = null     map = null }, 10000) This seems related to this discussion and the suggestion is that removing the container reference and releasing the references is all it should take.  Removing the container reference from the view does do the majority of the detach of the canvas and surface from the dom, but there seems to be a reference keeping the timers firing and reacting.  How can we fully release the view? Kris ... View more

With the 4.7 release, we are seeing errors coming from the onfocusout handler of the Search widget.  It was tracked down to be caused by an interaction with jQuery.  If a jQuery 'focusout' event listener is anywhere along the parent path of the search widget input, the widget's handler will error trying to walk up the parentNode path.  This is because the simulated bubble event fired by jQuery (apparently to work around some browser version focus event issues) fires with the target element at the top of the path (not the input).  The error is: dojo.js:2072 Uncaught TypeError: Cannot read property 'parentNode' of null at HTMLInputElement.d [as onfocusout] (dojo.js:2072) at Object.trigger (jquery-3.3.1.js:8255) at Object.simulate (jquery-3.3.1.js:8318) at HTMLDocument.handler (jquery-3.3.1.js:8352) This can be reproduced by added jQuery and a focusout listener to any element outside the search input.  For example to any sample with a Search widget add: <script src="https://code.jquery.com/jquery-3.3.1.js"></script> <script>   $(document).ready(() => $('body').on('focusout', () => {})); </script> Then click in the Search input control, and then click anywhere outside the Search input and check the console.  If you change the arcgisjs API version from 4.7 to 4.6 the error does not occur.  The following jsfiddle example demonstrates this.  http://jsfiddle.net/xrwfhc1n Kris ... View more