honestbleeps/Reddit-Enhancement-Suite

RES should not run on error pages

Open

#2003 opened on Feb 2, 2015

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (3,922 stars) (899 forks)batch import
Difficulty-­2_MediumPriority-1_Little Interesthacktoberfesthelp wanted

Description

specifically 500s. maybe 400s.

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
browser extension basicsunderstanding of RES content scripts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate how RES currently determines when to run. The issue suggests that RES should not run on error pages (HTTP 500, possibly 400). Check the extension's background scripts or content script injection logic. Look for use of chrome.webRequest or similar to detect status codes. Consider the possibility of checking document.title or document.body content for error indicators. The issue is vague, so first clarify the exact definition of 'error pages' and whether this should be handled via manifest permissions or runtime checks.