chakra-ui-vue-next icon indicating copy to clipboard operation
chakra-ui-vue-next copied to clipboard

BUG: CPopper component loses reference element during HMR

Open codebender828 opened this issue 4 years ago • 2 comments

Bug report

There's a weird bug I've spent a lot of time trying to figure out but haven't had much progress on yet.

When initially loading the page, the vue-popper composable hook works just fine. However during development(HMR with tie), when the template is changed where it's consumed, the referenceElement is no longer found by popperjs, even though it can be logged into the DOM.

TODO: Add reproduction

Describe the bug

To reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Minimal reproduction

Expected behavior

Screenshots

System information

  • OS: [e.g. macOS, Windows]
  • Browser (if applies): [e.g. Chrome, Safari]
  • Version of @chakra-ui/core: [e.g. 1.0.0-rc.3]
  • Version of Node.js: [e.g. 12.11.1]

Additional context

codebender828 avatar Mar 18 '21 18:03 codebender828

I can take a look, do you have the latest changes on feat/popover branch?

koca avatar Mar 18 '21 21:03 koca

Thanks, @koca. Yes. You can run yarn build to build all packages and then yarn dev to start the playground.

See the popper-with-transition.vue file for the latest changes

codebender828 avatar Mar 19 '21 01:03 codebender828

Will not fix. Closing in favour of Zag.js

codebender828 avatar Feb 17 '23 15:02 codebender828