Marco Ciampini

After #40740, there are two different props in the `Popover` component to affect is position: `position` (legacy) and `placement` (new) In order to deprecate the legacy `position` prop from the...

Popover: polish component after recent refactor

8

The recent [refactor](https://github.com/WordPress/gutenberg/pull/40740) of the Popover component to use `floating ui` has caused a few regressions, and still feels partially incomplete. **Known regressions (either issues, or PRs containing a fix):**...

Link format Popover: use placement prop instead of legacy position prop

1

## What? ## Why? ## How? ## Testing Instructions ## Screenshots or screencast

URLPopover: use new placement prop instead of legacy position prop

1

## What? TODO: verify if instead we need to make a non-breaking change (introduce placement, deprecate position, convert from position to placement internally) ## Why? ## How? ## Testing Instructions...

Image format popover: use placement prop instead of legacy position prop

1

## What? ## Why? ## How? ## Testing Instructions ## Screenshots or screencast

Autocompleter Popover: use placement prop instead of legacy position prop

1

## What? ## Why? ## How? ## Testing Instructions ## Screenshots or screencast

Navigation Submenu Popover: use placement prop instead of legacy position prop

1

## What? ## Why? ## How? ## Testing Instructions ## Screenshots or screencast

Navigation Link Popover: use placement prop instead of legacy position prop

1

## What? ## Why? ## How? ## Testing Instructions ## Screenshots or screencast

Button block Popover: use placement prop instead of legacy position prop

1

## What? ## Why? ## How? ## Testing Instructions ## Screenshots or screencast

URL Input Popover: use new placement prop instead of legacy position prop

1

## What? ## Why? ## How? ## Testing Instructions ## Screenshots or screencast