fix: use onchange instead of oninput for checkbox/select elements (fixes #1000)

[wahajahmed010]

Summary

Fixes issue #1000 where buttons/options in the extension settings page were not responding to clicks.

Root Cause

The options page (src/options/options.js) used .oninput event handlers for:

• <input type="checkbox"> elements (service enable toggles like DeepL)
• <select> dropdown elements ("useAlternativeService", "enableDiskCache")

The input event is not standard for checkboxes in some browsers (including Firefox), which prevents the event handler from firing when users click checkboxes or select options. This matches the cross-browser symptoms reported in #1000 (Firefox, Chrome, Ungoogled Chromium, Cromite, Fennec on Android).

Fix

Changed .oninput to .onchange for all affected elements:

• #useAlternativeService (select)
• #btnEnableGoogle, #btnEnableBing, #btnEnableYandex, #btnEnableDeepL (checkboxes)
• #enableDiskCache (select)

onchange is the standard, cross-browser-compatible event for both <input type="checkbox"> and <select> elements.

Files Changed

• src/options/options.js — 3 line changes (3 deletions, 3 insertions)

Verification

• No existing test suite in the repository.
• Fix verified by code review: all other checkbox/select handlers in the same file already correctly use .onchange.

AI-assisted

This fix was identified and implemented with AI assistance.

Fixes #1000