Guillaume Chau
Guillaume Chau
You can put `:triggers=[]` and control the popper however you like, for example by adding event listeners on the button in the default slot.
Could you try putting the usage of it inside a component or wrap it using [!isCollecting()](https://histoire.dev/reference/client.html#iscollecting)?
I have the same issue and I tried to create a reproduction without success for now. https://github.com/Akryum/cypress-issue-26431
I repeatedly ran one specific test in the project at work, and got this error 11 times out of 20. It's making the tests very flaky :( It is basically...
Interestingly if I only run one test in that test file, I never get the error out of the 20 runs: Details ```shell ==================================================================================================== (Run Starting) ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Cypress: 13.1.0...
I'm able to reproduce the error in the reproduction I shared above (https://github.com/Akryum/cypress-issue-26431) (updated today) Example of terminal output: Details ```shell ==================================================================================================== (Run Starting) ┌────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Cypress: 13.1.0 │ │...
Putting `.only` on the first test in `Meow.cy.js` seems to significantly reduce the number of error (I don't get any on 20 runs).
Try to use ESM version of `@vue/apollo-composable`
See a working example [here](https://github.com/vuejs/apollo/blob/v4/packages/test-e2e-composable-vue3/src/stores/channel.ts) that is passing in our automated tests.
@qwertyuiopngsdfg It looks like it's an issue in Apollo Client: https://github.com/apollographql/apollo-client/blob/9b22974b3e0f131a50c2618cc08ea6745e79a653/src/core/types.ts#L143