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

Handle the Disable State for Binary, File, and Image Fields #31497

Open
nicobytes opened this issue Feb 27, 2025 · 0 comments
Open

Handle the Disable State for Binary, File, and Image Fields #31497

nicobytes opened this issue Feb 27, 2025 · 0 comments

Comments

@nicobytes
Copy link
Contributor

Parent Issue

#31494

Task

The Binary, File, and Image fields should correctly handle the disabled state when the lock feature is activated. Users should not be able to upload, drag and drop, select existing files, or create new files when the system is locked. This ensures that no unauthorized changes can be made while in a locked state.

Image

Proposed Objective

Code Maintenance

Proposed Priority

Priority 3 - Average

Acceptance Criteria

  • The Binary, File, and Image fields should be completely disabled when in the locked state.
  • Users should not be able to drag and drop files, choose a file, import from a URL, or create/select existing files.
  • The UI should visually indicate that the fields are disabled.
  • When unlocked, the fields should return to their normal interactive state.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

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

No branches or pull requests

1 participant