Skip to content

feat: remove border radius & extra content#4083

Open
filippovskii09 wants to merge 6 commits into
openedx:release-23.xfrom
filippovskii09:filippovskii/fix/styles-for-search-button
Open

feat: remove border radius & extra content#4083
filippovskii09 wants to merge 6 commits into
openedx:release-23.xfrom
filippovskii09:filippovskii/fix/styles-for-search-button

Conversation

@filippovskii09

@filippovskii09 filippovskii09 commented Jan 12, 2026

Copy link
Copy Markdown
Contributor

Description

In this PR was added style fixes for Search Submit Button

Issues

#2674
#4023

Before:
Знімок екрана 2026-01-12 о 11 42 19

After:
Знімок екрана 2026-01-12 о 11 34 11

@openedx-webhooks

openedx-webhooks commented Jan 12, 2026

Copy link
Copy Markdown

Thanks for the pull request, @filippovskii09!

This repository is currently maintained by @openedx/committers-paragon.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Jan 12, 2026
@netlify

netlify Bot commented Jan 12, 2026

Copy link
Copy Markdown

Deploy Preview for paragon-openedx-v23 ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 5a8f031
🔍 Latest deploy log https://app.netlify.com/projects/paragon-openedx-v23/deploys/69bc45169923c600087d7ba8
😎 Deploy Preview https://deploy-preview-4083--paragon-openedx-v23.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@codecov

codecov Bot commented Jan 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.39%. Comparing base (dfc69e2) to head (5a8f031).
⚠️ Report is 46 commits behind head on release-23.x.

Additional details and impacted files
@@              Coverage Diff              @@
##           release-23.x    #4083   +/-   ##
=============================================
  Coverage         94.39%   94.39%           
=============================================
  Files               242      243    +1     
  Lines              4296     4299    +3     
  Branches           1020      982   -38     
=============================================
+ Hits               4055     4058    +3     
  Misses              237      237           
  Partials              4        4           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@filippovskii09 filippovskii09 marked this pull request as ready for review January 12, 2026 09:52
Comment thread src/SearchField/index.scss Outdated
@filippovskii09 filippovskii09 changed the title feat: remove border radius & extra contetn & add capitalize feat: remove border radius & extra content Jan 15, 2026
Comment thread src/SearchField/index.scss Outdated
@mphilbrick211 mphilbrick211 moved this from Needs Triage to In Eng Review in Contributions Jan 16, 2026

@peterkulko peterkulko left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I checked, it seems to look much better now. Thanks for this fix!

Comment thread src/SearchField/index.jsx Outdated
export const SEARCH_FIELD_SCREEN_READER_TEXT_SUBMIT_BUTTON = 'submit search';
export const SEARCH_FIELD_SCREEN_READER_TEXT_CLEAR_BUTTON = 'clear search';
export const SEARCH_FIELD_BUTTON_TEXT = 'search';
export const SEARCH_FIELD_BUTTON_TEXT = 'Search';

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We should probably just remove this completely. We already have a default for buttonText in SearchField.SubmitButton

SearchFieldSubmitButton.defaultProps = {
variant: 'light',
submitButtonLocation: 'internal',
buttonText: 'Search',
};

So it'd be nice to not have this defined in 2 places.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The SEARCH_FIELD_BUTTON_TEXT variable has been removed

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think it would be good to have translations for the "Search" string.
Currently, we have an ongoing forum discussion about incorrect translations, which also concerns the SearchField component button text.

@filippovskii09 could you please wrap this text into translations?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@PKulkoRaccoonGang translation was added!

@itsjeyd itsjeyd added the waiting for eng review PR is ready for review. Review and merge it, or suggest changes. label Jun 25, 2026
@gabrieldamours

Copy link
Copy Markdown

Hi @brian-smith-tcril! Same here: would you mind giving this PR a quick check? We're hoping to unblock it as part of the ongoing PR spring cleaning hackathon. Thanks!

@brian-smith-tcril

Copy link
Copy Markdown
Contributor

Closing the loop on the Search vs search change before diving into a full review:

It appears the button used to display Search, but when #1154 landed (specifically 56ec789 with a commit message of "feat: export default strings as constants for use in consumer tests") the string added for export was set to search instead.

This makes be believe that Search is the intended text, and the change to search was a regression, so the change back to Search in this PR is appropriate.

@brian-smith-tcril brian-smith-tcril left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Overall this looks great! I left one tiny naming comment. Once that is resolved this should be good to land!

screenReaderText, icons, refs, value, disabled,
} = useContext(SearchFieldContext);
const intl = useIntl();
const defaultButtonText = buttonText ?? intl.formatMessage(messages.searchButtonText);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The default naming feels strange here. I think of intl.formatMessage(messages.searchButtonText) as the "default" so having the prop-supplied buttonText go into something named defaultButtonText feels off. I'd recommend resolvedButtonText as an alternative, but I'm open to other ideas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U waiting for eng review PR is ready for review. Review and merge it, or suggest changes.

Projects

Status: In Eng Review

Development

Successfully merging this pull request may close these issues.

8 participants