SevenTV / Website

The 7TV Web App with the Vue framework
https://7tv.app
Other
38 stars 30 forks source link

chore(deps-dev): bump @floating-ui/dom from 1.1.0 to 1.2.5 #953

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @floating-ui/dom from 1.1.0 to 1.2.5.

Release notes

Sourced from @​floating-ui/dom's releases.

@​floating-ui/dom@​1.2.5

Bug Fixes

  • fix: don't skip initial ResizeObserver callback update in autoUpdate (#2232)

    This runs two updates on mount instead of one when elementResize is enabled. When dealing with frameworks that use inside-out (down-up) initialization of effects/rendering, like React, children are positioned before their parent positioned which meant they were positioned relative to the (0, 0) coordinates, which is incorrect. This problem only presents itself when the child and parent both try to position themselves at the same time on mount — for example, opening a menu and its submenu simultaneously.

    By not skipping this update, this issue isn't present since children reposition themselves after their parents have been positioned.

@​floating-ui/dom@​1.2.4

Bug Fixes

  • fix(getDimensions): measure <svg> arrows with CSS sizes instead of getBoundingClientRect() to avoid reading transformations (#2223)

@​floating-ui/dom@​1.2.3

Bug Fixes

  • fix(getOffsetParent): always return window for SVG elements (#2198)

@​floating-ui/dom@​1.2.2

Bug Fixes

  • fix(arrow): correctly take into account floating element border for <svg> arrows (#2195)

@​floating-ui/dom@​1.2.1

Bug Fixes

  • fix(getClippingRect): prevent fixed ancestors from creating a clipping ancestor (#2170)

  • fix(types): re-export middleware options types (#2175)

@​floating-ui/dom@​1.2.0

New Features

  • feat(platform): add ability to polyfill offsetParent access (in a pure way) to fix a platform gap where the incorrect value is returned inside shadow DOM. (#2160)

    This was previously done internally a while ago (1.0.1) but reportedly causes a performance issue in certain scenarios, meaning it cannot be a default. This allows the polyfill to be conditionally enabled by libraries. The polyfill and its usage is available here, which ideally would be made into its own package (that can be iterated on and potentially improved perf-wise).

  • feat(detectOverflow): accept virtual Rect boundaries (#2161)

Bug Fixes

  • fix(types): exported platform object now has all methods non-optional with Required<Platform> (#2166)

@​floating-ui/dom@​1.1.1

Bug Fixes

  • fix(types): allow SVGElement as the arrow element (#2146)

  • fix(arrow): re-allow SVGElements to be measured (#2146)

Commits
  • 4ab077a fix(dom): don't skip initial RO callback in autoUpdate (#2232)
  • be47d12 fix(FloatingArrow): prevent transparency overlap, vertical sizing, strokeWidt...
  • 07a9f4f fix(inline): merge rects on the same line (y coord) (#2220)
  • f811580 chore: update React playground
  • 1410f69 chore: fix circular deps
  • 79ba1cb fix: arrow hydration and svg offsetParent (#2198)
  • f09f6a7 chore: window.ts -> getWindow.ts
  • 62fb961 refactor: use rectToClientRect util
  • 254c8e1 chore: remove unused deps
  • 8de3b14 fix: type exports and comments (#2175)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #970.