easy-richtextarea 4.0.200 → 4.0.202
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -1
- package/example.js +349 -72
- package/lib/customEventTypes.js +12 -2
- package/lib/example/view/button.js +39 -0
- package/lib/example/view/richTextarea.js +39 -0
- package/lib/example/view.js +217 -30
- package/lib/example.js +1 -1
- package/lib/richTextarea.js +73 -43
- package/package.json +3 -3
- package/src/customEventTypes.js +5 -1
- package/src/example/view/button.js +15 -0
- package/src/example/{richTextarea.js → view/richTextarea.js} +11 -2
- package/src/example/view.js +64 -31
- package/src/example.js +1 -1
- package/src/richTextarea.js +106 -53
- package/lib/example/richTextarea.js +0 -39
package/README.md
CHANGED
|
@@ -2,7 +2,14 @@
|
|
|
2
2
|
|
|
3
3
|
A textarea element that handles and hands off events well.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
In the DOM API the active element is the one that has the focus.
|
|
6
|
+
That concept is twisted here somewhat.
|
|
7
|
+
A rich textarea is active if it has the focus but can remain active when it loses it.
|
|
8
|
+
Rich textareas are made for sitting behind a pretty printer that is still shown even when the focus is lost.
|
|
9
|
+
Scroll events still need to be handled, for example.
|
|
10
|
+
|
|
11
|
+
As well as a different concept of being active, rich textareas also have an improved change event mechanism that results in custom change events being fired not just whenever the content changes but when the selection changes to.
|
|
12
|
+
Again this makes them more suitable for sitting behind a pretty printer.
|
|
6
13
|
|
|
7
14
|
### JSX support
|
|
8
15
|
|