You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
When looking into adding transition properties for layer attributes in #8015. I noticed that the style wide configuration of TransitionOptions in #7711 is not returning the same values as the value set. Eg. following test is failing:
longtransitionDuration = 1;
mapboxMap.setTransitionDuration(transitionDuration);
assertEquals("TransitionDuration should match", transitionDuration, mapboxMap.getTransitionDuration(), 0);
with
AssertionFailedWithCauseError: TransitionDuration should match expected:<1.0> but was:<1.0E9>
Looking at the style specification, it seems that the unit should be in milliseconds while it nows seems to be set in seconds and returned in nano seconds.
The text was updated successfully, but these errors were encountered:
it seems that the unit should be in milliseconds while it nows seems to be set in seconds and returned in nano seconds.
The intention was to match the expected time unit on the platform, regardless of the style specification’s units. On iOS and macOS, the expected unit would be seconds. It looks like the Android implementation suffered from a similar issue as #8264, which was subsequently fixed on iOS and macOS by correctly round-tripping seconds values.
When looking into adding transition properties for layer attributes in #8015. I noticed that the style wide configuration of TransitionOptions in #7711 is not returning the same values as the value set. Eg. following test is failing:
with
Looking at the style specification, it seems that the unit should be in milliseconds while it nows seems to be set in seconds and returned in nano seconds.
The text was updated successfully, but these errors were encountered: