laptop and a wrench

Bug

Using the ‘viewModel’ property to configure the Time Slider widget, and then using the ‘play()‘ method, causes the first date value defined in the ‘stops’ property to be skipped.

Last Published: September 22, 2021 ArcGIS API for JavaScript
Bug ID Number BUG-000141819
SubmittedJuly 29, 2021
Last ModifiedJune 5, 2024
Applies toArcGIS API for JavaScript
Version found4.20
Operating SystemWindows OS
Operating System Version10.0 64 Bit
StatusWill Not Be Addressed

Additional Information

This is not known limitation. When a timeSlider.play() function is called, the thumbs immediately jump to the next 'stop' and then pause for the playRate time period. The observed behavior when explicitly defining a ViewModel is by design. When properties are defined at the widget level there is a perceived pause. This is because the widget is still hydrating the view model and is unable to perform the first movement. This is the reason with the 5 seconds delay. To remove the delay, the user should wait for the widget to fully initialize as shown below. timeSlider.when(() => { timeSlider.play(); }); If the user would like to pause the playing for a prescripted about of time then I would suggest something like as follows. // Wait three seconds after TimeSlider has fully loaded to play. timeSlider.when(async () => { const pause = new Promise((resolve) => { setTimeout(() => { resolve(); }, 3000); }); await pause; timeSlider.play(); });

Workaround

  • Define all property values for the Time Slider widget directly, without using ‘viewModel’ property.
  • Do not use the ‘play()’ method to start the slider animation automatically.

Steps to Reproduce

Bug ID: BUG-000141819

Software:

  • ArcGIS API for JavaScript

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options