[#45229] - [5.3] Fix description positioning in search bar
- Closed
- 15 Apr 2025
- Medium
- Build: 5.2-dev
- # 45229
- Diff
- Hemang360:5.2-dev
User tests: Successful: Unsuccessful:
Pull Request for Issue #44086.
Summary of Changes
-
Fixed an issue where the search bar description was partially visible
-
Changed bottom: 100% to top: 100%; bottom: auto;, ensuring the description appears completely without obstructing the search input.
Testing Instructions
-
Go to the media manager or any relevant page with a search bar.
-
Hover over the search bar to view the description tooltip.
-
Ensure the description appears below the search bar and does not overlap.
Actual result BEFORE applying this Pull Request
The description was partially visible.
Expected result AFTER applying this Pull Request
The description appears fully below the search bar.
Link to documentations
Please select:
-
Documentation link for docs.joomla.org:
-
No documentation changes for docs.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Repository NPM Change |
| Labels |
Added:
NPM Resource Changed
PR-5.2-dev
|
||
@Hemang360 please rebase your PR to the 5.3-dev branch. It will then probably come in 5.3.1.
@tecpromotion @brianteeman I have rebased it to 5.3.
| Title |
|
||||||
I have tested this item ✅ successfully on 8a8e643
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/45229.
I have tested this item ✅ successfully on 8a8e643
For test used custom update server.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/45229.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/45229.
| Labels |
Added:
RTC
|
||
Why I am seeing merging is blocked
Why I am seeing merging is blocked
@Hemang360 Because the 5.3-dev branch is locked until we have released 5.3.0 stable tomorrow. After that, the branch will be unlocked again. Not related to your PR, and nothing you should worry about.
| Status | Ready to Commit | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-04-15 13:39:36 |
| Closed_By | ⇒ | Hemang360 | |
| Labels |
Added:
PR-5.3-dev
Removed: PR-5.2-dev |
||
@Hemang360 Why have you closed this PR and deleted your fork of the repository?
The pull request was ready to commit, which means it would be merged after the release when the branch would have been unlocked.
@richard67 Sorry about that, I had opened the PR a long time ago and didn’t check back for a while. When I finally did, my fork was way behind and I was running into a lot of conflicts trying to sync it up. I tried resolving them, but things got messy and I thought the safest option would be to refork the repo from scratch.
I didn’t realize that would auto-close the PR...definitely my bad. I am opening a new PR with the same changes ASAP.
Apologies again for the trouble!
Nice work.
@richard67 @rdeutz I assume that this needs to be rebased to a different branch as there will be no further 5.2 releases. please can you let @Hemang360 know which branch that should be as I have no clue anymore as its so inconsistent