Releases: iansan5653/dom-input-range
v2.0.1
v2.0.0
Replaces the InputStyleCloneElement
custom element with a new InputStyleClone
class. This no longer uses a custom element under the hood, avoiding issues with conflicting custom element registration. The underlying clone element can still be accessed using InputStyleClone#element
.
There are no migration steps required for consumers using only the InputRange
API. Consumers relying on the InputStyleCloneElement
API will need to migrate to InputStyleClone
.
v1.2.0
What's Changed
-
Allow
InputStyleCloneElement
to be constructed directly (#6). This fixes errors thrown when cloning the element and also allows for direct construction when using the registry is not possible:const clone = new InputStyleCloneElement() clone.connect(targetInputElement)
Full Changelog: v1.1.6...v1.2.0
v1.1.6
- Fix error thrown when element already registered (on soft navigation) in #4
Full Changelog: v1.1.5...v1.1.6
v1.1.5
v1.1.4
v1.1.3
Fixes a bug where the clone element would intercept pointer events and prevent the user from interacting witht the underlying input
v1.1.2
Improve input event handling to react faster, so that consumers can also react to input events and work with updated information
v1.1.1
- Update documentation
- Slightly tweak how changes to the input are handled by triggering layout recalculations on value changes
v1.1.0
Bug Fixes
- Fixes layout discrepancies in Firefox, particularly when a vertical scrollbar is visible, and makes logic more robust to avoid any potential future errors
New Features
- Adds a new exported class that was previously internal:
InputStyleCloneElement
. This custom element clones and syncs with aninput
ortextarea
element pixel for pixel in order to operate on the contents of that input. This lower-level API may be useful in some cases whereInputRange
is insufficient.
Full Changelog: v1.0.3...1.1.0