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

Asset browser columns not resizeable in grid mode - Bug Report #17931

Open
thoraxe opened this issue May 17, 2024 · 0 comments
Open

Asset browser columns not resizeable in grid mode - Bug Report #17931

thoraxe opened this issue May 17, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/content Categorizes an issue or PR as relevant to SIG Content.

Comments

@thoraxe
Copy link

thoraxe commented May 17, 2024

Describe the bug
When the Asset Browser is in list mode, you cannot resize the columns. This can leave folder or file names cut-off, for example.

Steps to reproduce
Steps to reproduce the behavior:

  1. Set the asset browser to list mode.
  2. Try to resize a column

Expected behavior
Columns should be resizeable.

Actual behavior
Columns cannot be resized.

Screenshots/Video
image

Desktop/Device (please complete the following information):

  • Device: PC
  • OS: Windows 11
  • Version: O3DE 23.10.3
@thoraxe thoraxe added kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 17, 2024
@spham-amzn spham-amzn added sig/content Categorizes an issue or PR as relevant to SIG Content. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/content Categorizes an issue or PR as relevant to SIG Content.
Projects
None yet
Development

No branches or pull requests

2 participants