Skip to content

Fix chat input box aligment

Tomas Bulvarequested to merge
tbulva-input-button into main

What does this MR do?

fixes: gitlab#571974 related to: https://gitlab.com/gitlab-org/duo-ui/-/issues/98

This change updates the visual design of two chat input components to give them a more modern "project studio" appearance. The main improvements include:

  • Repositioning the send/cancel buttons to float over the input area in the bottom-right corner in a way that doesn't cover the input field
  • Moving the character count display to be smaller and positioned within the input area rather than below it
  • Realigning the input area within the outline

Screenshots or screen recordings

before after
image image
image image
image image

Integration merge requests

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by Tomas Bulva

Merge request reports