guardian/scribe

New 'input' event type for user input

Open

#303 创建于 2014年12月6日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)JavaScript (3,516 star) (265 fork)batch import
enhancementformattershelp wanted

描述

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.

贡献者指南

技术栈
javascripthtmlcss
领域
frontend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of JavaScript eventsFamiliarity with Scribe's event system
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
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.
New 'input' event type for user input · guardian/scribe#303 | Good First Issue