ER: Remove unused `search` id query selectors

[castillios]

Emergent Requirement - Problem

In assets/js/current-projects.js, there are three query selectors that select an id named search. However, in _includes/current-projects.html, there is no 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 3 instances of document.querySelector('#search') and their corresponding line numbers 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:

  Line 105 before:

  const inputEl = document.querySelector('#search-desktop') || document.querySelector('#search-mobile') || document.querySelector('#search');
  

  Line 105 after removing document.querySelector('#search'):

  const inputEl = document.querySelector('#search-desktop') || document.querySelector('#search-mobile');
  

  Lines 344-348 before:

  function searchEventHandler(e){
      e.preventDefault();
      const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile') || document.querySelector('#search');
      let searchTerm = input ? input.value : '';
  

  Lines 344-348 after removing document.querySelector('#search'):

  function searchEventHandler(e){
      e.preventDefault();
      const input = document.querySelector('#search-desktop') || document.querySelector('#search-mobile');
      let searchTerm = input ? input.value : '';
  

  Lines 376-380 before:

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

  Lines 376-380 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 and ER)

• 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

[daras-cu]

@castillios thanks for writing this! A couple notes:

• I think the P-feature should be Projects Page instead of Homepage.
• Let's provide a little more detail in the Potential Solutions section. Since we are usually low on IM1 issues we can give this to someone as one of their first issues to write if it's a little more specific. You don't have to write out the full action items, but maybe list the three lines that include the #search querySelector and what they should look like after removing it. And then mention that the issue should include testing performing a search in both mobile and desktop views on the Projects and Projects-Check pages.