Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CoordinateConversion widget Input coordinate format chooser as wrong spacing/CSS #302

Closed
2 tasks done
Calin-Geoinfo opened this issue May 23, 2024 · 3 comments
Closed
2 tasks done
Assignees
Labels
bug Something isn't working implemented

Comments

@Calin-Geoinfo
Copy link

IMPORTANT

  • My question is related to a new issue in the latest next release. For all other issues, open a ticket with Esri Technical Support, post your question in the community forum, or share your idea with the global community on ArcGIS Ideas.
  • I have checked for existing issues to avoid duplicates. If someone has already opened an issue for what you are experiencing, please add a 👍 reaction and comment as necessary to the existing issue instead of creating a new one.

Actual behavior

The coordinate format text is cut off. In an earlier version this was the case as well on the "main window", now only in the input coordinate window.

Expected behavior

The way it looks like in 4.29

Reproduction sample

https://developers.arcgis.com/javascript/latest/sample-code/sandbox/?sample=widgets-coordinateconversion add jsnext

Reproduction steps

Click on the pencil icon.

Reproduction browser

Chrome

SDK version (check your console)

20240523

Operating System (check https://whatsmyos.com)

Windows

@NoashX
Copy link
Collaborator

NoashX commented May 23, 2024

Thanks for reporting this @Calin-Geoinfo. I can reproduce the issue. We are investigating.

@NoashX NoashX self-assigned this May 23, 2024
@NoashX NoashX added bug Something isn't working under consideration and removed needs triage labels May 23, 2024
@NoashX
Copy link
Collaborator

NoashX commented May 31, 2024

Update: we have a fix in place, and this will be resolved at the 4.30 release. The fix should be testable via next in the coming days.

@Calin-Geoinfo
Copy link
Author

I can confirm it is fixed. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working implemented
Projects
None yet
Development

No branches or pull requests

2 participants