Skip to content

Conversation

@stefan-dragomir
Copy link
Collaborator

@stefan-dragomir stefan-dragomir commented Jul 24, 2025

Description

Related Issue

https://jira.corp.adobe.com/browse/FORMS-18740

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Before

Wizard Desktop and Mobile
Wizard Before - Desktop
Wizard Before - Mobile

Horizontal Tabs Desktop and Mobile
Horizontal Tabs Before - Desktop
Horizontal Tabs Before - Mobile

Vertical Tabs Desktop and Mobile
Vertical Tabs Before - Desktop
Vertical Tabs Before - Mobile

After

Wizard Desktop and Mobile
Wizard After - Desktop
Wizard After - Mobile

Horizontal Tabs Desktop and Mobile
Horizontal Tabs After - Desktop
Horizontal Tabs After - Mobile

Vertical Tabs Desktop and Mobile
Vertical Tabs After - Desktop
Vertical Tabs After - Mobile

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes and the overall coverage did not decrease.
  • All unit tests pass on CircleCi.
  • I ran all tests locally and they pass.

@stefan-dragomir
Copy link
Collaborator Author

Clones PR #18


&--active {
color: $accent;
color: $black;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stefan-dragomir It is ok to change to black from accent color of theme, if design team has recommended, as you mentioned in JIRA. Please check, are tabs(tabsontop and vertical) also facing same issue of contrast? They use same colors. Or you can also check with design team, if we should make both follow similar color scheme, as is the case now

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stefan-dragomir

Please add the screenshots and mention the discussion which you had with the designer.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussion archive link added in PR comment and Jira.

@stefan-dragomir stefan-dragomir changed the title FORMS-18740: State of active component lacks 3 to 1 contrast ratio @s… FORMS-18740: State of active component lacks 3 to 1 contrast ratio @sunnym @vavarshn Aug 7, 2025
@stefan-dragomir
Copy link
Collaborator Author

Approval still pending, new changes will come.

display: flex;
align-items: center;
flex-flow: wrap;
align-items: end !important;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stefan-dragomir Could you please show in screenshots, what change has it resulted in ?

Copy link
Contributor

@akshayvas akshayvas Sep 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stefan-dragomir since we are changing default-tab mixin, please add screenshots as to how vertical and horizontal tabs look, in desktop as well as mobile device. Also please add screenshots for wizard mobile resolution too.
cc: @vaibhav2601

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All screenshots added in ticket descriptions and Jira.

@stefan-dragomir
Copy link
Collaborator Author

stefan-dragomir commented Sep 10, 2025

Discussion thread:
https://cq-dev.slack.com/archives/D04G5JRE6UE/p1754988479233569

Discussion printscreen:
Screenshot 2025-09-10 at 15 18 19

display: flex;
align-items: center;
flex-flow: wrap;
align-items: end !important;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stefan-dragomir All changes seem fine in the PR. For this one, could you please elaborate why did we need to change flex-flow and alignment? Are we trying to align elements to end ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I needed to align to end instead of center because I added an ::after element as an underline right under the tab labels. This addition was pushing the label up, so aligning everything to bottom would keep the label in the same spot as before.

display: flex;
align-items: center;
flex-flow: wrap;
align-items: end !important;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stefan-dragomir We can change end to flex-end. Works same here, but it is the correct value for vertical alignment.
also, for pseudo element, border-bottom instead of border-top will help prevent confusion.
Although the pseudo element approach is also correct for showing active tab, we could also have used border-bottom on tab itself to avoid having to add an extra pseudo element and its styling overhead. For now, you can choose to keep pseudo element.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Align and Border updated.
The pseudoelement was added while the shape and the background of the tab were still visible, and a colored border bottom would have had rounded corners as well. I'll keep it as it is since it already matches design.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @stefan-dragomir Background, Round borders can be managed by setting border bottom left and right radius values to zero.
But approving the PR for now as this approach is also not wrong, and alignments can be managed with applied CSS.
@vaibhav2601

@vaibhav2601 vaibhav2601 merged commit eaa4135 into main Sep 18, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants