[#7957] - Extension manager search box doesn't clear
- Closed
- 27 Jan 2016
- Medium
- Build: master
- # 7957
Steps to reproduce the issue
type in a search word in extension manager->manage->search
complete search.
hit the X to clear the search field
delete keyword manually
Expected result
search keyword is removed
Actual result
screen flashes and word remains
System information (as much as possible)
Additional comments
removing cookie removes the keyword and once again displays the listing.
| Title |
|
||||||
zero-24
- | Title |
|
||||||
| Category | ⇒ | Administration UI/UX |
Yes, everything is working properly
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/7957.
no, its not.. I've done 3 clean installs all with same behavior in chrome
https://www.facebook.com/N6REJ/videos/924576100960469/?theater
problem still exists in 3.5.8 even on new install
Same issue with me. I have this on multiple installs all on the same server. Using Chrome or Safari same results. It happens no matter where I am searching, Modules, Articles, etc... No way to completely clear out the search once you have something in there. The only way to clear it is to logout of Joomla admin and back into it. It even affects the Intro Image and Full Article Image. Now that I have something specified in there I can not find a way to remove it. Click X the image path disappears and then click save and its back again.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/7957.
fix by upgrading suhosin the the very latest version available.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-01-27 10:14:23 |
| Closed_By | ⇒ | brianteeman |
closing as proven to be an issue with suhosin (resolved in latest release) and not joomla
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/7957.
I can not replicate this report. I am testing with a fresh install of 3.4.4, using Chrome and Firefox browsers on a Mac and everything is working normally as we would expect.
@N6REJ - is it a browser issue perhaps?