guardian/scribe

New 'input' event type for user input

Open

#303 opened on Dec 6, 2014

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (3,516 stars) (265 forks)batch import
enhancementformattershelp wanted

Description

Currently 'content-changed' is called when setHTML() is called. Typically 'change' events aren't fired after setters are called. For example, the HTML input field's input/change events aren't fired when the 'value' attribute is changed manually using JS.

It would be nice if Scribe had its own 'input' and 'change' events that only fired when the user did something, e.g. typed, undo, paste, etc.

Contributor guide

Tech stack
javascripthtmlcss
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
clear
Prerequisites
Understanding of JavaScript eventsFamiliarity with Scribe's event system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Examine how 'content changed' event is currently dispatched in the source code (likely in scribe.js or related modules). Determine where user interactions (typing, undo, paste) are handled and how to differentiate them from programmatic calls like setHTML(). Consider implementing new 'input' and 'change' events that only fire on user actions, following common web patterns.