ER: Remove unused search id query selectors

@ldaws003

Emergent Requirement - Problem

In assets/js/current-projects.js, there are two query selectors that select an id named search. However, in _includes/current-projects.html, there is no existing id for search.

We must remove any query selectors for search in assets/js/current-projects.js since it is an unused id.

Issue you discovered this emergent requirement in

Mobile View: Page Reset and Filter Bar Closing After Search #8466
Issue was pointed out in this comment for the PR of the original issue

Date discovered

9/19/2026

Did you have to do something temporarily

YES
NO

Who was involved

@ldaws003 @castillios

What happens if this is not addressed

Any deprecated IDs may continue to bloat the codebase if left unaddressed.

Resources

Use this template to create your issue: Blank Issue Template
Tutorial on Chrome's Dev Tools to test for mobile views: https://developer.chrome.com/docs/devtools/device-mode

Recommended Action Items

Make a new issue
Discuss with team
Let a Team Lead know

Potential solutions [draft]

Create a small issue that lists the 2 instances of document.querySelector('#search') to be removed from assets/js/current-projects.js.

In your issue body under the Instructions section, include before and after code snippets as follows:

Before:

const allInputEl = Array.from(document.querySelectorAll('#search-desktop, #search-mobile, #search'));

After removing #search:

const allInputEl = Array.from(document.querySelectorAll('#search-desktop, #search-mobile'));

Before:

function searchCloseEventHandler(e){
    e.preventDefault();
    const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile') || document.querySelector('#search');
    if (input) input.value="";
}

After removing document.querySelector('#search'):

function searchCloseEventHandler(e){
    e.preventDefault();
    const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile');
    if (input) input.value="";
}

After listing implementation details, include an action item to test and verify that the changes still work by performing a search in both mobile and desktop views on the Projects and Projects-Check pages
Ensure your issue labels match this parent ER (with the exception of Issue Making: Level 1, ER and non-PR contribution)
Once the overall issue has been drafted, in the sidebar under Relationships, add this ER as a parent to your issue
Review and if ready, apply the ready for merge team label

@yepezjuan

Hi @yepezjuan, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

Availability: M, Th, F (5-7pm)
ETA: Thurs, Oct 8, 2026

@yepezjuan

Hi @yepezjuan! Thanks for creating the issue for this ER. I have a bit of feedback before I mark it as Ready for Prioritization.

Be sure to add capitalization to each of the action items for consistency
There's a minor spelling error, not a big deal!: 'asstes/js/current-projects.js' should be 'assets/js/current-projects.js'

Our Blank Issue Template unfortunately doesn't contain the Prerequisite section. Would you be able to add the following before the Overview section?:

###Prerequisite
1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started page](https://www.hackforla.org/getting-started) and attend an onboarding session.
2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md).

This one's on me for not initially including it in the ER, but could you add these links to the Resources section? These are the pages that will need to be tested on the devs localhost:
- Hack for LA Projects Page: https://www.hackforla.org/projects/
- Hack for LA Projects Check Page: https://www.hackforla.org/projects-check/

Thanks for your patience and work on this issue! Feel free to ping me on Slack once the edits have been made and I'll re-review ASAP.

@yepezjuan

Hi @yepezjuan, thanks for making those changes! I've marked your issue as Ready for Prioritization and will close this ER.

Navigation Menu

Repository navigation

ER: Remove unused `search` id query selectors #8803

Emergent Requirement - Problem

Issue you discovered this emergent requirement in

Date discovered

Did you have to do something temporarily

Who was involved

What happens if this is not addressed

Resources

Recommended Action Items

Potential solutions [draft]

1 remaining item

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

ER: Remove unused search id query selectors #8803

Description

Emergent Requirement - Problem

Issue you discovered this emergent requirement in

Date discovered

Did you have to do something temporarily

Who was involved

What happens if this is not addressed

Resources

Recommended Action Items

Potential solutions [draft]

Activity

daras-cu commented on Sep 26, 2026

1 remaining item

castillios commented on Sep 27, 2026

daras-cu commented on Sep 27, 2026

castillios commented on Oct 1, 2026

HackforLABot commented on Oct 1, 2026

yepezjuan commented on Oct 1, 2026

castillios commented on Oct 7, 2026

castillios commented on Oct 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

ER: Remove unused `search` id query selectors #8803