Remove chosen from com_search

[brianteeman]

Chosen is not accessible so we shouldnt use it unless it offers something useful.

In the search component in the front end there are potentially two lists Ordering and display #

Neither of these require or benefit from chosen so this simple PR returns them to regular and accessible lists

Pull Request for Issue #24469

[zwiastunsw]

I have tested this item ✅ successfully on aa618b8

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24623.}

[Quy]

I have tested this item ✅ successfully on aa618b8

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24623.}

[Quy]

RTC

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24623.}

[HLeithner]

Whats the reason to remove this without needs? The only thing what could happen is to break sites that expect chosen.

[brianteeman]

It is removed from this page because chosen breaks accessibility and we dont need any of the added features of chosen for the select lists here.

It cannot break an existing site

[wilsonge]

We don't in this view but the long standing opinion is removing this can affect ssites that were using it on other pages without the include. This was how we ended up basically rolling out chosen into every view in the backend (as well as the consistency argument). I agree with @HLeithner that this is something not to be fixed in 3.x sadly

[brianteeman]

We don't in this view but the long standing opinion is removing this can affect sites that were using it on other pages without the include.

I don't follow this logic. We are talking about a component so how it can affect other pages that are not com_search

[wilsonge]

No it doesn’t affect other pages but it does affect modules and plugins on that page

For the record I disagreed with this logic at the time. But it’s long been made standard. And especially given we should be trying to 3.x towards more support only mode in anticipation of 4.0 it doesn’t make sense to make changes like this

[brianteeman]

in which case the user can create a template override

[zwiastunsw]

@wilsonge : What kind of plugin? For which modules? Some example? Specifically? It was a very bad code!

[Fedik]

it was introduced as a fix #1653 for some issue, which no one know anymore
it seems was just a "styling"

[HLeithner]

I'm closing this because of the statements above not breaking user templates.

[brianteeman]

Shame that accessibility doesnt matter

[Quy]

RTC

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24623.}

[HLeithner]

Thx

[brianteeman]

thanks