[BUG] : Unescaped Search Query Special Characters Regex Exception in SpeechHistory

[hrshjswniii]

🚀 Program

GSSoC

🐛 Describe the bug

In SpeechHistory.jsx, when users filter their speech history using the search bar, entering regex special characters (such as (, [, *, +, ?, \) without sanitization into a new RegExp(query, "i") constructor throws a fatal SyntaxError: Invalid regular expression crash, breaking the speech history rendering view.

---

🔁 Steps to Reproduce

Steps to reproduce the behavior:

1. Go to the Speech History drawer or page.
2. Type ( or [ in the search input box.
3. See error with white screen or SyntaxError: Invalid regular expression in DevTools console.

---

✅ Expected Behavior

Search queries should escape special regex characters or perform case-insensitive String.prototype.includes() matching to prevent regex syntax crashes.

---

❌ Actual Behavior

Typing special regex characters into the search bar throws a unhandled SyntaxError exception that crashes the history panel.

---

🌱 Contributor Checklist

• I am participating via GSSoC
• I have read the contribution guidelines
• I checked for existing issues before creating this

---

💻 Environment

• Browser: Chrome, Firefox, Edge, Safari
• Device: Desktop, Laptop
• OS: Windows, macOS, Linux

---

📝 Additional Context

Replacing new RegExp() with sanitized string escaping or text.toLowerCase().includes(query.toLowerCase()) fixes the search crash.

[github-actions]

❌ Action Required Before Review

Caution

1 item needs fixing before a mentor can be notified.

Hey @hrshjswniii! 👋 Thanks for submitting your issue — almost there. Please update the issue body:

#	Problem	How to Fix
💬	Not enough detail	Replace placeholder text with real context, clear reproduction steps, and expected vs. actual behavior

To run the checks again: edit the issue body → save. This comment updates automatically ✅

💡 Tip: You can edit this issue directly — or start fresh with your GSSoC template: 📋 Bug Report · ✨ Feature Request.

---

_{🤖 VoiceForge Automation · Updates automatically on edits}

[github-actions]

🧠 Triage Suggestion — Looks Good

Tip

This issue looks valid, actionable, and ready for maintainer review.

Hey @hrshjswniii! 👋 Thanks for opening this issue.

The issue clearly describes a reproducible bug with steps to reproduce, expected vs actual behavior, and a suggested fix for escaping regex special characters in the search query. It is actionable and specific to the SpeechHistory component's search functionality.

Similar Issues:
No close match found.

Suggested maintainer action: go ahead

⚠️ This is only a suggestion. A maintainer will make the final decision.

---

_{🤖 VoiceForge Automation · Updates automatically on edits}

[github-actions]

🚀 You're Good to Go!

Important

Work is officially approved. Please read everything below before you start.

Hey @hrshjswniii! 🎉 This issue has been reviewed and approved by the maintainer team.

📋 Before you start

• 🏷️ Priority: priority: medium
• 🎯 Difficulty: level: medium
• 🔗 PR: use the matching program template and include Closes #1189

If you can no longer continue, please comment here so maintainers can reassign this issue.

---

_{🤖 VoiceForge Automation · Updates automatically on edits}