issues
search
sindresorhus
/
element-ready
Detect when an element is ready in the DOM
MIT License
436
stars
15
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Simple `element-ready`
#51
fregante
opened
3 weeks ago
0
Include `typed-query-selector`
#50
fregante
opened
3 weeks ago
0
Accept array of selectors
#49
fregante
opened
3 weeks ago
1
Stop earlier if dom was already ready
#48
fregante
closed
2 months ago
1
Clean getMatchingElement
#47
fregante
closed
3 months ago
0
`observeReadyElements`: Handle `{stopOnDomReady: true}` when called after DOM ready
#46
sindresorhus
opened
9 months ago
0
Support `AbortSignal`
#45
sindresorhus
opened
1 year ago
0
Simplify the logic by using async iterables
#44
sindresorhus
closed
9 months ago
1
Update many-keys-map to v2 ESM
#43
muuvmuuv
closed
1 year ago
0
Support document's readyState individually
#42
134130
closed
3 months ago
4
Update linter
#41
fregante
closed
1 year ago
0
Add extension to type import
#40
fregante
closed
1 year ago
0
Update dependencies
#39
Richienb
closed
2 years ago
0
Add support for specifying a predicate to find a specific element
#38
bengry
closed
3 years ago
14
Allow specifying a predicate function to only resolve on a more specific element
#37
bengry
closed
3 years ago
1
Add `observeReadyElements` method
#36
Richienb
closed
3 years ago
11
Make it more strongly-typed when used with TypeScript
#35
cheap-glitch
closed
3 years ago
3
Include `typed-query-selector`?
#34
fregante
closed
3 years ago
1
`waitForChildren` might still not be reliable
#33
fregante
closed
3 years ago
5
Use types directly from querySelector, without copying them
#32
fregante
opened
3 years ago
0
Use native querySelector types instead of copying them
#31
fregante
closed
3 years ago
3
Wait for children before resolving promise
#30
fregante
closed
3 years ago
4
Wait for an element’s contents, not just the element
#29
sindresorhus
closed
3 years ago
7
Fix sometimes missing the matching elements with `stopOnDomReady:true
#28
riophae
closed
5 years ago
9
Sometimes it can't capture the matching elements with `stopOnDomReady=true`
#27
riophae
closed
5 years ago
0
Drop p-defer
#26
fregante
closed
5 years ago
0
Add the `cancellable` option
#25
CvX
closed
5 years ago
7
Add `elementReady.subscribe()`
#24
qti3e
closed
4 years ago
10
Correct the return type when timeout is undefined
#23
CvX
closed
5 years ago
4
Subscribe to new elements on the page
#22
fregante
closed
3 years ago
8
Add `timeout` option
#21
fregante
closed
5 years ago
0
Add types for `stopOnDomReady` option
#20
fregante
closed
5 years ago
2
Add `timeout` option
#19
sindresorhus
closed
5 years ago
2
Require Node.js 8, refactor TypeScript definition to CommonJS compatible export
#18
BendingBender
closed
5 years ago
0
Add `stopOnDomReady` option, remove `.cancel()`, add `.stop()`
#17
fregante
closed
5 years ago
11
Simplify with `many-keys-map`
#16
fregante
closed
5 years ago
1
Update dependencies, add TypeScript definition
#15
BendingBender
closed
5 years ago
0
Add Flow types đŸ”¥
#14
reyronald
closed
6 years ago
2
Don't add elements to cache if they're found right away
#13
fregante
closed
6 years ago
5
Found elements are not uncached
#12
fregante
closed
6 years ago
5
Fix element selection when same selector is used in different targets
#11
reyronald
closed
6 years ago
10
Returns the wrong element when calling it with the same selector, but in different targets
#10
reyronald
closed
6 years ago
0
Allow specifying a target other than document
#9
fregante
closed
7 years ago
2
Automatically stop on dom ready
#8
fregante
closed
5 years ago
14
Add elementReadyPromise#cancel()
#7
fregante
closed
7 years ago
0
Timeout or CancelablePromise
#6
fregante
closed
7 years ago
1
Use requestAnimationFrame for FUOC-less resolution
#5
fregante
closed
7 years ago
1
requestAnimationFrame instead of setInterval
#4
fregante
closed
7 years ago
1
prevent multiple instantiation of intervals for one selector
#3
soenkekluth
closed
8 years ago
1
MutationObserver
#2
zzarcon
closed
5 years ago
5
Next