Latest Contributions by Noah-Sager

‎10-31-2025

‎10-30-2025

Hi @Brian_McLeer, thanks for posting your idea here. Do the color and theme properties work for your use case? If not, could you explain how a width property would work better?

‎10-24-2025

Yes, @JonathanDawe_BAS, the issue you pointed out is not ideal. The transition will still take us some time. For workarounds, is there any edge / position of the screen that you can place the docked Popup for 4.34?

‎10-24-2025

No problem, @AntonioMedrano. This is a big transition for all of us. Keep posting questions if you run into any issues. Your understanding is correct. The Popup component is like an opt-in experience. Here is the key part of the doc: https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-popup/

‎10-24-2025

Hi @JonathanDawe_BAS, thanks for also posting your question here. What you are seeing with the Popup behavior is by-design (shout-out @LaurenBoyd). The Popup component should always be top-most in the UI. When using a Map component, the Popup widget will display below the component(s). When we talk about the Popup widget with a Map (not a Map component), then we see the same behavior where the Popup widget should always be top-most in the UI. Example: https://developers.arcgis.com/javascript/latest/sample-code/sandbox/?sample=popup-docking-position So mixing the Popup widget and Popup component is a little confusing, but the new Popup component behavior matches our design and our previous Popup widget behavior.

‎10-23-2025

Hi @AntonioMedrano, nice, thanks for the reply. I understand the situation better now. I had to pull in some additional resources (shout-out @ReneRubalcava). So at 4.34, the Search component still uses the Popup widget. As such, we cannot dock the Popup widget inside the Search component logic. However, at the next release, we expect the Search component to use the Popup component, and then all the problems would be resolved as you thought. For now, what we can do is actually use the Popup widget and associate it with the map component. Then we tell the Popup to always open in the docked position. Now, the Search component will open a docked Popup widget. Example: https://codepen.io/noash/pen/WbrJGaY?editors=1000 However, if you want to go one step further, you can have both the Popup widget and the Popup component. This way the Search popups will be docked, but any clicked feature on the map will open the Popup component, and behave as expected (e.g. not docked): https://codepen.io/noash/pen/ogbdzVZ?editors=1000 Note, this is a 4.34 solution. I would advise you to revert this workflow and use the Search component and Popup component after we enhance them. Hope this helps!

‎10-23-2025

Hi @AntonioMedrano, thanks for posting your question here. We recently released the Popup component in beta: https://developers.arcgis.com/javascript/latest/release-notes/#popup-component-beta, so you might see some differences compared with working with the Popup widget. However, if you're working with the Popup and the Search widget/component, maybe I can help. The Search component still uses the Popup widget. Can you describe a bit more about what you are trying to do? If you have a simplified repro app that works at 4.33, I'd be happy to take a look.

‎10-23-2025

Hi @ClintOffutt1. This is good feedback. For multi segment measurements where each segment will be logged and/or labeled, this is currently on our roadmap. Can't make any timeline promises right now, but this functionality is targeted for a future release. For the coordinate system, in geographic coordinate systems (GCS) and in Web Mercator, measurements are computed geodetically. Web Mercator is the default spatial reference of the basemap in ArcGIS Online. In projected coordinate systems (PCS), apart from Web Mercator, measurements are computed in a Euclidean manner (in their respective PCS). So if you're using a state plane basemap, then your measurements should be handled accordingly. If the behavior you are seeing is different, please contact Technical Support (if you are able), and/or share a publicly accessible webmap (or JS SDK app hosted on Codepen, like this: https://developers.arcgis.com/javascript/latest/sample-code/webmap-basic/), and we can take a look.

‎10-23-2025

Hi @GeorgeB, thanks for posting your idea here. Just a couple clarification questions: Are you looking for this functionality in MapViewer, SceneViewer, or both? Would you expect a Sketch-like experience where previous measurements can be modified, or only added/deleted? Do you expect these measurements to be persisted when the map or scene is saved, or only temporary?

‎10-21-2025

Version 4.34 is here. By the numbers: we fixed 43 bugs, made 20 enhancements, added or updated 11 samples, and optimized 7 components. That’s a lot of numbers, but now we can offer even more numbers with the new and awesome Version Matrix. Ever wondered which version of the ArcGIS Maps SDK for JavaScript relates to what version of Arcade or the Web map spec or other related products? Well, now you’ll know: https://developers.arcgis.com/javascript/latest/version-matrix/ Also, we’re moving to semantic versioning! 4.34 will be the last release of 2025, and 5.0.0 will be the first release of 2026. Since semantic versioning is driving this update, and not underlying technological changes, there is no need to panic or grab a towel. The change is good and helpful and clearly explained in this blog article: https://www.esri.com/arcgis-blog/products/js-api-arcgis/announcements/arcgis-maps-sdk-for-javascript-is-moving-to-semantic-versioning After 5.0.0 releases in 2026, it’s time to get ready for the Esri Developer & Technology Summit, on March 10 – 13. Mark your calendars, it’ll be an awesome event. https://www.esri.com/en-us/about/events/devtech/overview Back to version 4.34 and components. Components are awesome, and this is the way forward from widgets: https://developers.arcgis.com/javascript/latest/components-transition-plan/. We have implemented slots and shadow DOM in our Map components for improved encapsulation and flexibility. This enhancement allows for better isolation of styles and functionality within the components. Instead of using position for placing components and other UI elements in your map/scene, we now recommend utilizing the slot attribute. This means that the Placement component is no longer needed, and themes can be configured via Calcite modes instead of linking to a CSS stylesheet. That’s pretty neat. https://developers.arcgis.com/javascript/latest/release-notes/#slots-and-shadow-dom Additionally, the Map, Scene, Link Chart, and Video components now provide CSS variables that reserve space around their content to prevent overlaying UI elements from obscuring slotted components. https://developers.arcgis.com/javascript/latest/release-notes/#layout-css-variables And our new Building your UI guide page pairs nicely with the above CSS enhancements. https://developers.arcgis.com/javascript/latest/building-your-ui/ To improve error handling and help make you more productive, the Map, Scene, and Link Chart components now support a loadErrorSources property and two new events: arcgisLoadError and arcgisViewReadyError. These additions help you detect and respond to loading issues with the component's underlying view or associated resources. https://developers.arcgis.com/javascript/latest/release-notes/#layout-css-variables Speaking of being more productive, Charts components are out of beta and ready for production use. There’s a new Heat Chart component that allows you to configure data in a matrix form to uncover patterns, relationships, and trends across large datasets. You can also declaratively load charts just like web maps. Lastly, we have updated the charts model usage pattern by transitioning from using only getters and setters to a clearer split between properties and methods. https://developers.arcgis.com/javascript/latest/release-notes/#charts-components Popup is now in beta as a component! https://developers.arcgis.com/javascript/latest/release-notes/#popup-component-beta 3D scenes now support the FlowRenderer! https://developers.arcgis.com/javascript/latest/release-notes/#flowrenderer-in-3d-scenes Editor now includes new split and merge workflows to improve feature editing flexibility. These workflows are currently supported in 2D only. The split workflow allows users to divide an existing feature into multiple parts during an update. The merge workflow enables users to combine multiple features into a single feature. https://developers.arcgis.com/javascript/latest/release-notes/#editing-enhancements The new animationsDisabled property on the Map component and animationsEnabled on MapView let you control all animations in a 2D view, including animated symbols, renderers, layers, and navigation. You can now disable animations in 2D Maps. Also, ARIA attributes are now supported on the Map and Scene components, as well as on MapView and SceneView, through the aria property. https://developers.arcgis.com/javascript/latest/release-notes/#accessibility-enhancements The new 3D VolumeMeasurementAnalysis (beta) lets you interactively measure and visualize ground surface volumes. This beta release introduces two measure types: cut-fill, which computes cut and fill volumes relative to a flat, horizontal surface defined by the input polygon, and stockpile, which calculates cut and fill volumes against a surface approximated from the polygon's coordinates. https://developers.arcgis.com/javascript/latest/release-notes/#new-volumemeasurementanalysis-beta And so much more. We have labeling enhancements, a new LastMileDelivery class, ParquetLayer (beta), the list goes on. Check out the official release notes to learn more. https://developers.arcgis.com/javascript/latest/guide/release-notes/index.html REFERENCES Release Blog https://www.esri.com/arcgis-blog/products/js-api-arcgis/announcements/version-4-34-of-javascript-maps-sdk-released 4.34 Release Notes https://developers.arcgis.com/javascript/latest/guide/release-notes/index.html Calcite September 2025 Release Summary https://developers.arcgis.com/calcite-design-system/releases/summaries/2025-09/ 4.34 Samples https://developers.arcgis.com/javascript/latest/sample-code/?tagged=4.34 Breaking Changes across all 4x releases https://developers.arcgis.com/javascript/latest/guide/breaking-changes/index.html ArcGIS Maps SDK for JavaScript is Moving to Semantic Versioning https://www.esri.com/arcgis-blog/products/js-api-arcgis/announcements/arcgis-maps-sdk-for-javascript-is-moving-to-semantic-versioning Esri Developer & Technology Summit [March 10 - 13, 2026] https://www.esri.com/en-us/about/events/devtech/overview

‎09-23-2025

Coming back to this topic, we anticipate making the `expanded` property public when we migrate the CoordinateConversion widget to component at the next release (October).

‎09-23-2025

Hi @mukecz1, thanks for posting your question here. It sounds like there is an issue with the URL passed to the print service. Here are the facts as I understood them: WMS raster layer from GeoServer. Prints correctly if the raster contains RGB values. Does not print if the raster only contains a grey index with a style. I have a hunch about what's going on, but it would be super helpful if you could share a test-app or test services so I could reproduce on my end and compare?

‎09-18-2025

My apologies @GaryB, I misunderstood. Hopefully, if I understand correctly now, what you want is the arcgisSelectResult event: https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-search/#arcgisSelectResult This event will fire when the user selects a result from the suggestions. Here is an example that prints the selected suggestion to the browser Console: https://codepen.io/noash/pen/EaPxPRK?editors=1000

‎09-18-2025

I think it would be interesting to conduct a poll and see where our users would like to receive updates and information from Esri Developers.

‎09-18-2025

Hi @GaryB, thanks for posting your question here. Since you're using a layer as the source in the example, it seems like you should use the LayerSearchSource instead of a custom source. Custom source is designed for 3rd party sources. Here is an example of LayerSearchSource: https://developers.arcgis.com/javascript/latest/sample-code/search-component-multisource/ Here is an example of a custom source: https://developers.arcgis.com/javascript/latest/sample-code/search-component-customsource/ And here is an example of using the layer from your app with LayerSearchSource: https://codepen.io/noash/pen/EaPxjQo?editors=1000

Online Status	Offline
Date Last Visited	Monday

My Ideas

Latest Contributions by Noah-Sager

Re: Add an option to support grid line width updates - Status changed to: Open

Re: Add an option to support grid line width updates - Status changed to: Needs Clarification

Re: Popup component properties do not apply to Search result Popups

Re: Popup component properties do not apply to Search result Popups

Re: Popup component properties do not apply to Search result Popups

Re: Popup component properties do not apply to Search result Popups

Re: Popup component properties do not apply to Search result Popups

Re: measurement tools needs work!

Re: Multiple measurements - Status changed to: Needs Clarification

ArcGIS Maps SDK for JavaScript – Version 4.34 Release

Re: CoordinateConversion

Re: Possible Bug with WMS Raster Layer Printing in ArcGIS Core 4.33.14

Re: Search component with custom source

Re: How about communicating on Mastodon @EsriDevs ?

Re: Search component with custom source

Re: How to create a "Geocode (stored)" key?

Re: AI on custom map?

Re: ArcGIS Maps SDK for JavaScript – Version 5.0 R...

Re: Default token expiration time when SAML is con...

Re: locationToAddress argument requestOptions quer...