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

[Navigation Logo/Navigation User] Truncate text for smaller widths, such as mobile devices #9398

Open
2 of 6 tasks
geospatialem opened this issue May 22, 2024 · 0 comments
Open
2 of 6 tasks
Assignees
Labels
1 - assigned Issues that are assigned to a sprint and a team member. Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. estimate - design - sm Small design effort; 1-4 days of design work impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p - low Issue is non core or affecting less that 10% of people using the library spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.

Comments

@geospatialem
Copy link
Member

Check existing issues

Description

Support navigation-logo and navigation-user use cases where longer app titles and usernames are present, in particular on mobile, by supporting text truncation.

Acceptance Criteria

Support truncation for longer titles for navigation-logo and usernames for navigation-user

Relevant Info

Related to a larger epic for late 2024 in #6661.

Surfaced while adding navigation to our Developer site tutorials.

Which Component

  • Navigation Logo
  • Navigation User

Example Use Case

To accommodate more use cases, in particular on mobile for longer application title names and usernames:

  • Navigation Logo: application names
  • Navigation User: usernames

Very broad example: https://codepen.io/geospatialem/pen/LYoZxPG

Current approach

image

Priority impact

impact - p2 - want for an upcoming milestone

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-angular
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/eslint-plugin-calcite-components

Esri team

Calcite (design)

@geospatialem geospatialem added enhancement Issues tied to a new feature or request. design Issues that need design consultation prior to development. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels May 22, 2024
@github-actions github-actions bot added impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. labels May 22, 2024
@DitwanP DitwanP added p - low Issue is non core or affecting less that 10% of people using the library estimate - design - sm Small design effort; 1-4 days of design work and removed needs triage Planning workflow - pending design/dev review. labels Jun 13, 2024
@DitwanP DitwanP added this to the Design Backlog milestone Jun 13, 2024
@DitwanP DitwanP removed this from the Design Backlog milestone Aug 8, 2024
@geospatialem geospatialem added the spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. label Sep 16, 2024
@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - assigned Issues that are assigned to a sprint and a team member. Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. design Issues that need design consultation prior to development. enhancement Issues tied to a new feature or request. estimate - design - sm Small design effort; 1-4 days of design work impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone p - low Issue is non core or affecting less that 10% of people using the library spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Projects
None yet
Development

No branches or pull requests

3 participants