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

Content Truncated at 320 CSS Pixel Viewport Width #227524

Closed
Bluefish0558 opened this issue Sep 4, 2024 · 2 comments
Closed

Content Truncated at 320 CSS Pixel Viewport Width #227524

Bluefish0558 opened this issue Sep 4, 2024 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) stale Issues that have not been triaged in an appropriate amount of time triage-needed

Comments

@Bluefish0558
Copy link

Bluefish0558 commented Sep 4, 2024

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.92.2
  • OS Version: 14.6.1 (23G93)

Description: Certain content, such as "Show and run commands," "Go to symbols in editor," and "Search for text (Experimental)," gets truncated when the page is viewed at a 320 CSS pixel width, preventing users with low vision from accessing it.

Steps to Reproduce:

  1. Resize the VSCode window to a viewport width of 320 CSS pixels.
  2. Observe that content such as "Show and run commands" and "Go to symbols in editor" gets truncated.

User Impact: Users with low vision who resize text or adjust the viewport size will be unable to access this truncated content.

Expected Behavior: The page should reflow properly without requiring horizontal scrolling, ensuring that all content remains accessible at 320 CSS pixels.

Actual Behavior: Content is truncated, causing a loss of functionality and requiring horizontal scrolling.

Recommendation: Ensure the page reflows without two-dimensional scrolling at a viewport width of 320 CSS pixels. Alternatively, move content to a show/hide control, such as a hamburger menu, to maintain functionality.

Viewport

@vs-code-engineering vs-code-engineering bot added the stale Issues that have not been triaged in an appropriate amount of time label Sep 11, 2024
@Yoyokrazy
Copy link
Contributor

/duplicate #227503

@vs-code-engineering vs-code-engineering bot added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 11, 2024
Copy link

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2024
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Oct 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) stale Issues that have not been triaged in an appropriate amount of time triage-needed
Projects
None yet
Development

No branches or pull requests

3 participants