[5.4] Fancy select: mark already selected elements with checkmark

[Fedik]

Pull Request for Issue #45536 .

Summary of Changes

Mark already selected elements with checkmark, based on @travisrisner idea

Testing Instructions

Run npm install

Please follow #45536

Or open Articles list and filter by category (or few).
After filtering check the category filter dropdown. There should be marked already selected items.

Actual result BEFORE applying this Pull Request

Already selected items not marked

Expected result AFTER applying this Pull Request

Already selected items is marked

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

[richard67]

@Fedik The CSS linter complains: https://github.com/joomla/joomla-cms/actions/runs/18629158166/job/53111418382?pr=46328

[brianteeman]

Please use the logical css propery inset-inline-end instead of right or it will not work as intended in an RTL language

right

inset-inline-end

[Fedik]

updated

[brianteeman]

I have tested this item ✅ successfully on 20d03ae

---

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

[travisrisner]

I have tested this item ✅ successfully on 20d03ae

---

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

[richard67]

RTC

---

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

[muhme]

✅ Final test before merge with JBT 5.4-dev

• Before the PR
  • Installed Testing Sample Data, seen article view in selecting categories is not marking selected categories
• PR applied with gh pr checkout 46328 and npm ci
• Selected entries are marked, one and mulitple entries are mark-able, deselecting is working, tested with Firefox, Chrome, Safari and Edge

[muhme]

Thank you @Fedik for your contribution. Thank you @richard67 and @brianteeman for your support. Thank you @brianteeman and @travisrisner for testing.