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

[WebToolsE2E][Aspire] The "Actions" section and 'Column width' of the Resources, Structured, and Traces pages in the dashboard is not localized in non-ENU OS. #6520

Open
v-reinawang opened this issue Oct 28, 2024 · 2 comments
Milestone

Comments

@v-reinawang
Copy link

v-reinawang commented Oct 28, 2024

INSTALL STEPS

  1. Clean machine: Win11 x64 23h2 CHS
  2. Install VS 17.12 GA
  3. Install Aspire 9.0.0

REPRO STEPS

  1. Create Aspire Starter App
  2. Build solution and run the project

NOTE: This issue also repro on KOR OS and DEU OS.

ACTUAL:
The "Actions" section of the Resources, Structured, and Traces pages in the dashboard is not localized.
Image
Image
Image
The 'Column width' of the Resources, Structured, and Traces pages in the dashboard is not localized
Image

EXPECTED:
The "Actions" section and 'Column width' are localized.

@v-reinawang v-reinawang changed the title [WebToolsE2E][Aspire] The "Actions" section of the Resources, Structured, and Traces pages in the dashboard is not localized. [WebToolsE2E][Aspire] The "Actions" section of the Resources, Structured, and Traces pages in the dashboard is not localized in non-ENU OS. Oct 28, 2024
@v-reinawang v-reinawang changed the title [WebToolsE2E][Aspire] The "Actions" section of the Resources, Structured, and Traces pages in the dashboard is not localized in non-ENU OS. [WebToolsE2E][Aspire] The "Actions" section and 'Column width' of the Resources, Structured, and Traces pages in the dashboard is not localized in non-ENU OS. Oct 28, 2024
@balachir balachir added this to the 9.0 milestone Oct 28, 2024
@balachir
Copy link

Do we need to fix this for Aspire 9.0 GA? @joperezr @JakeRadMSFT

@joperezr
Copy link
Member

Great find, but I don't think we'll be able to take this in for 9, especially since we'd need the loc team to fix this so sounds like something we should target for our first servicing. @JakeRadMSFT thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants