sindresorhus/element-ready

Issues

• Simple `element-ready`

  #51 opened 2 months ago by fregante
  0

• Accept array of selectors

  #49 opened 2 months ago by fregante
  1

• Include `typed-query-selector`

  #50 opened 2 months ago by fregante
  0

• `observeReadyElements`: Handle `{stopOnDomReady: true}` when called after DOM ready

  #46 opened 10 months ago by sindresorhus
  0

• Support document's readyState individually

  #42 opened 5 months ago by 134130
  4

• Support `AbortSignal`

  #45 opened a year ago by sindresorhus
  0

• Update many-keys-map to v2 ESM

  #43 opened a year ago by muuvmuuv
  0

• Subscribe to new elements on the page

  #22 opened 3 years ago by fregante
  8

• Allow specifying a predicate function to only resolve on a more specific element

  #37 opened 3 years ago by bengry
  1

• Include `typed-query-selector`?

  #34 opened 4 years ago by fregante
  1

• `waitForChildren` might still not be reliable

  #33 opened 4 years ago by fregante
  5

• Use types directly from querySelector, without copying them

  #32 opened 4 years ago by fregante
  0

• Wait for an element’s contents, not just the element

  #29 opened 4 years ago by sindresorhus
  7

• Sometimes it can't capture the matching elements with `stopOnDomReady=true`

  #27 opened 5 years ago by riophae
  0

• Automatically stop on dom ready

  #8 opened 6 years ago by fregante
  14

• Add `timeout` option

  #19 opened 6 years ago by sindresorhus
  2

• MutationObserver

  #2 opened 6 years ago by zzarcon
  5

• Found elements are not uncached

  #12 opened 7 years ago by fregante
  5

• Returns the wrong element when calling it with the same selector, but in different targets

  #10 opened 7 years ago by reyronald
  0

• Timeout or CancelablePromise

  #6 opened 8 years ago by fregante
  1

• requestAnimationFrame instead of setInterval

  #4 opened 8 years ago by fregante
  1

• Needs compilation step

  #1 opened 9 years ago by fregante
  2