Latest Contributions by AnneFitz

@Insa_bel Thank you so much for these examples (and the screenshots). Really helps us better understand the use cases for these slots / custom content.  For the Time Slider popovers - are these just used to configure the start and end values of the Time Slider? Custom actions in Sketch and Feature Table make sense - we'll look into this 😊 For the select-all button in Feature Table, we can see the use case especially for smaller layer types. We don't have any immediate plans to add this, but will look into it as well.  ... View more

As we have many custom project requirements, we are making some custom DOM changes to the custom components like TimeSlider, Sketch, Editor or FeatureTable. These changes include for example adding actions to the component DOM. With currently no slots being available, we do not see alternative options to manually altering the components' shadowDOM after the component finished rendering.  Hi @Insa_bel -- could you please share more information about what type of customization is needed and where you are adding custom content in these components? (screenshots would be helpful). We're working on gathering requirements to support slots in these components in the future. Thanks 🙂 ... View more

Hi Michael -- Unfortunately this is currently a known limitation with symbols and real world size visual variables. When the symbols start to take up the majority of the visible map (spanning multiple tiles under the hood), they can get cut off. We are investigating ways to fix this issue in the future, but it's currently a limitation. ... View more

@JonathanDawe_BAS this issue was fixed in today's patch, 5.0.10! Let us know if you are still running into any issues. ... View more

This issue was fixed in patch 5.0.9. See the patch fixes in the release notes (5.0.9 should be up by the end of the day!) Let us know if you're still running into issues. ... View more

I will add that I set my Expand components' mode to "floating" as you suggested and it does appear to address the issue. However, I am not wholly sure what sort of impact this will have on non-mobile screens. There should be no impact on non-mobile screens. The default "mode" is "auto" - which switches between "floating" on non-mobile, and "drawer" in mobile mode. Changing the mode to "floating" will only impact the behavior on mobile, since the default is already "floating" for non-mobile! See the documentation for more information: https://developers.arcgis.com/javascript/latest/references/map-components/components/arcgis-expand/#mode Thanks! ... View more

Hi @DECCA_Jimmy - thanks for reporting this, we'll look into it. ... View more

Hi @MichelleStuart - try adding the apiKey directly to the FeatureLayer you want to edit (using FeatureLayer.apiKey) instead of applying it globally via esriConfig.  ... View more

Hi, the issue that you're experiencing seems to be related to the components being wrapped in arcgis-expand, which uses the "drawer" mode by default in mobile view. To change the default, set the expand component's `mode` to "floating". This is not related to arcgis-expand or any custom UI—happens with the measurement component placed directly in the scene. We were not able to reproduce this issue when the component was added directly to the scene. Could you share a Codepen or some sort of reproduction case if you are still experiencing this issue? Thanks!     ... View more

In the upcoming 5.0 release, we’ll support a CSS variable to customize the focus outline around the map/scene component: --arcgis-view-color-focus. We recommend avoiding removing the focus outline entirely, as it plays an important role in accessibility, especially for keyboard and assistive technology users. ... View more