I tried to buy a hoverboard but it failed with an error :(

overboard

I can’t buy a board :(

Notice how when the panel changes the hoverboard is re-mounted

https://app.replay.io/recording/replay-devtools-flickers--6f3477e1-057a-4bd0-b6fb-2d003791070d?point=14603334915665569610340638706894161&time=5472

good first issue

devtools

Hoverboard flickers on load

Hey hey, just wanted to let you know this counter doesn't increment.

broken-counter

Counter doesn't increment

![image](https://user-images.githubusercontent.com/87003751/222906320-80bb96fe-626f-471f-b21e-3092b798e6f8.png)


Protocol-Examples

react mount detection demo error

**Description:**
Done and Edit  button's border is not positioned properly . when click the done or Edit button ,the border is not fully visible.


* Screenshots:
<img width="1093" alt="Screenshot 2023-02-28 030418" src="https://user-images.githubusercontent.com/81948346/221690688-8efe08ef-233a-4233-9d90-01a652b102be.png">

<img width="1080" alt="Screenshot 2023-02-28 233358" src="https://user-images.githubusercontent.com/81948346/221939972-468f1777-9008-4ee0-a4b9-e38fa67269ba.png">


* Video (Loom):
* Replay ([replay.io/record-bugs](https://replay.io/record-bugs) for instructions):
* https://app.replay.io/recording/border-is-not-fully-visible-when-clicked--10c39501-ab18-4d74-b29c-926b83aa56d3


Library section focus outline clipped

### Description

While I was attempting to create an example of Classic Widget import I noticed that when I reduced the width of my window the template that I was editing switched to the front page.
When I re-adjusted the width it toggled back to the original template.

The problem occurs with WordPress 6.2-RC1 and Gutenberg 15.3.1
I do have other plugins activated and a custom FSE theme. 

### Step-by-step reproduction instructions

1. Open Site Editor
2. Add a new template eg page-widgets
3. Add an empty template part
4. Adjust the width of the window down - make it narrower
5. Notice that at some width the contents changes to the default template ( front page )
6. Adjust the window width up - wider and then narrower
7. Notice the contents toggles between the new template and default template ( front page )

### Screenshots, screen recording, code snippet


![site-editor-sizing](https://user-images.githubusercontent.com/2474435/224748468-ad42629e-5432-4475-9927-646c8b2c907e.gif)

A bit fast but it changes from page-widgets to front-page and then back again as I reduce the width then increase it again, then reduce it again.


### Environment info

- WordPress 6.2-RC1
- Gutenberg 15.3.1
- Custom theme: Fizzie
- Other plugins are activated.

### Please confirm that you have searched existing issues in the repo.

Yes

### Please confirm that you have tested with all plugins deactivated except Gutenberg.

No

[Type] Bug

[Status] Needs More Info

[Feature] Site Editor

[Feature] Template Editing Mode

gutenberg

Site Editor switches template when window width reduced or increased

We do a search if app.replay.io/recording exists in the issue, but only capture if it is included in the description. We could also pull in comments to capture replays posted there so all rows have a link.

replayable

Capture replay links from comments

Thread:

- https://twitter.com/k_woodhouse93/status/1585713986569637888
- https://twitter.com/k_woodhouse93/status/1585921284902252545
- Repro: https://twitter.com/k_woodhouse93/status/1586308416871489537
  - https://github.com/kwoodhouse93/ink-redux-repro
  - Replay (possibly crashing): https://app.replay.io/recording/replay-of-distclijs--797ca851-8c51-44c5-ba2f-ece05da30960

react-redux

Possible issue with either RTKQ or React-Redux with Ink

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:29 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T8101
    Binaries:
      Node: 16.14.2
      npm: 8.5.0
      Yarn: 1.22.19
      pnpm: 6.11.0
    Relevant packages:
      next: 13.2.4-canary.9
      eslint-config-next: 13.2.3
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

SWC minifier (swcMinify: true)

### Link to the code that reproduces this issue

https://github.com/ryanjduffy/nextjs-bug-react-tooltip

### To Reproduce

1. `npm create next-app`
2. `yarn add react-tooltip`
3. Add the tooltip component to `index.js`
4. `next build && next start` the app and trigger the tooltip

### Describe the Bug

When using `react-tooltip` (v5.10) with a new next.js app (v13.2) (created with `npm create next-app`), the compiled output when `swcMinify: true` of `react-tooltip` by SWC overwrites global variables breaking other module imports.

The replay below includes some comments pointing out the execution behavior in which `a` points to the react jsx runtime import on one render and then to an integer in a future render.

https://app.replay.io/recording/nextjs-react-tooltip-build-failure--78392709-938c-4efb-993d-40798eff5e7e

And a loom of me walking through the replay

https://www.loom.com/share/6815156c9ff14eb8ad6cbd7b7321d785

### Expected Behavior

Globals are not overwritten :)

### Which browser are you using? (if relevant)

n/a

### How are you deploying your application? (if relevant)

n/a

area: SWC Minify

next.js

Compiling react-tooltip in a next.js app can overwrite globals when swcMinify is true

This does not seem to cause any problems while recording, but we crash when attempting to replay it. Personally, I think it would be reasonable to just disable the print dialog from Replay because that doesn't feel like a feature that people will run into much (if anything they are likely to accidentally bring up the dialog like me and accidentally mess up their recording), but we could also fix it  for full marks 😄 

Recording: https://app.replay.io/recording/please-consider-the-environment-before-printing-this-replay--aacb2af2-2107-492d-82ab-69dd4ca2d4c7?point=60684969543474293057435418937531463&time=60857&hasFrames=false (crash happens between 30 and 40 seconds I think)

limitation

linear

gecko-dev

Opening the Print Dialog cannot be replayed

We made a Replay of this behavior 😛: https://app.replay.io/recording/dc020aef-64e2-4a4b-9a0d-1475ea12aebf you can click through to see a video.

I made an attempt to figure it out, and you can see my thought process in the replay. Afaict it's happening in the call to `sort` in `mergeObjectUpdates`, but I can't tell why.

https://github.com/tilt-dev/tilt/blob/master/web/src/HUD.tsx#L388

tilt

Resources reordering rapidly in sidebar

### Version

v14.17.6

### Platform

Darwin Nates-MacBook-Air.local 21.4.0 Darwin Kernel Version 21.4.0: Mon Feb 21 20:36:53 PST 2022; root:xnu-8020.101.4~2/RELEASE_ARM64_T8101 x86_64

### Subsystem

_No response_

### What steps will reproduce the bug?

As a possible workaround for https://github.com/RecordReplay/node/issues/28 I used process.exit to exit my script as a desirable point. The command I used to run the recording is `replay-node --exec ts-node ./src/index.ts `. 

### How often does it reproduce? Is there a required condition?

Seemingly every time 

### What is the expected behavior?

Replay should pause at the specified breakpoint

### What do you see instead?

Replay seems to be pausing at an unrelated breakpoint

### Additional information

The replay I'm experiencing this bug on is https://app.replay.io/recording/replay-of-ts-node--2833115f-26fd-4160-8b1d-ec19f86d8d16

Replay of the bug occurring is at https://app.replay.io/recording/replay-misidentifying-where-to-pause-for-breakpoint--3668d82a-b2e6-49cd-a1cb-0ba103cdcd85 

Reported on Discord at https://discord.com/channels/779097926135054346/798693728999047203/980889833998282792

Screen recording uploaded to Discord at https://discord.com/channels/779097926135054346/798693728999047203/980890518898753566 

node

Replay not pausing at correct position in call stack for breakpoint

### Description

When using Stately Studio on Windows 11 (22H2) with either Chrome (107.0.5304.63) or Firefox (106.0.1), zoom in and zoom out actions (by pressing Ctrl + Mouse Wheel Up or Down) are zooming in or zooming out way too much.

### Expected result

When pressing Ctrl button and scrolling mouse wheel button, on every tick the zoom should change by a reasonable distance, that's roughly equal between ticks.

### Actual result

When zooming in, zoom percentage seems to double on every tick. When zooming out, zoom percentage always goes to 10%.

### Which browsers are you seeing the problem on?

Firefox, Chrome

### Additional details

Here's a link to a Replay recording: https://app.replay.io/recording/search-box-or-search-box-or-stately-studio--c6f61ac4-f6b7-4d67-80fe-f52635cb8a5d

studio-issues

Bug: unexpected zoom behavior on Windows 11

Hi there,

With small size images, I get an issue like below:

![image](https://user-images.githubusercontent.com/94069932/150785560-7ba16f05-367d-4db8-bcf5-4fe4066034f2.png)

Can anybody help me?
Thanks in advance.

masonry

Issue with small size images

Probably a bug in visibility detection. 

Steps to repro:

1. https://excalidraw.com/#json=5236195592241152,nBFUdjjvd2rZyqpNHBMKUg
2. zoom on the ~center of the rectangle to 1000%

excalidraw

zooming on a shape stops rendering it

**Description**
Want to create Code Highlighting block with changing code language on every block. But got an error: 
`Error: Cannot resolve a Slate point from DOM point: [object Text],1`

**Recording**


https://user-images.githubusercontent.com/49220993/175454278-56800975-01bc-4d7d-89d3-31a51a8ef84b.mov



**Sandbox**
https://codesandbox.io/s/slate-reproductions-forked-rzgecw

**Steps**
To reproduce the behavior:
1. Click on custom block
2. Type something
3. See error (And also can't delete typed text)

**Expectation**
Edit text inside block without errors

**Environment**
- Slate Version: 0.80
- Operating System: Mac OS 12.1
- Browser: Safari 15.2

**Context**
Created custom block with code highlighting feature. 
Main difference with Slate Code Highlighting Example (https://github.com/ianstormtaylor/slate/blob/main/site/examples/code-highlighting.tsx) that I want to blocks with different languages in each custom block.


slate

Error: Cannot resolve a Slate point from DOM point: [object Text],1

I'm debugging this recording:
https://app.replay.io/recording/21594023-f9ae-4787-912c-c391a68304aa

and I've noticed that sometimes I'm not able to step into certain functions. Take a look at this loom:
https://www.loom.com/share/9628264e684a4d0eb66e5176296972e5

Notice how I've wanted to step into `reportImplicitAny` but I was taken out of this frame, to the point after the call to the `reportImplicitAny`'s caller.

One additional thing I've noticed here is that 0 hits are reported on the line containing that `reportImplicitAny`
<img width="953" alt="Screenshot 2021-09-21 at 13 24 01" src="https://user-images.githubusercontent.com/9800850/134162769-40a1f617-a18e-4586-a954-1229a043f322.png">

This is clearly incorrect as I was paused at this line of code.

0 hits reported incorrectly

**Description:**

In terminal this gets logged like this:
```
check node0: 9.372ms
check node1: 7.057ms
check node2: 0.559ms
check node3: 834.786ms
```
whereas in Replay we can see this:
```
"%s: %s", "check node", "0 9.372ms"
%s: %s check node1 7.057ms
%s: %s check node2 0.559ms
%s: %s check node3 834.786ms
```

**Steps to Reproduce:**

```js
console.time('check node'+i)
someCall()
console.timeEnd('check node'+i)
```

**Expected Result:**

This being consistent with the observed output in the real console.

**Additional Context:**

* Replay: can be seen [here](https://app.replay.io/recording/replay-of-tsc--8977288b-162f-4b6d-87d2-2ce054bf880c)


icebox

`console.time` logged weirdly with formatting specifiers (or similar)

### What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

- React: 0.0.0-experimental-e7d0053e6-20220325
- ReactDOM: 0.0.0-experimental-e7d0053e6-20220325
- Redux: 4.2.0
- React Redux: 8.0.2

Here is a Replay recording of this bug with some annotations from me:
http://app.replay.io/recording/replay-failing-reactdevtools-e2e-repro--3351989d-95d4-4035-80af-07d813a623aa

Here is a Loom (it's long) where I use Replay to investigate the problem:
https://www.loom.com/share/3d60c14466184b03acc9af7b80e9eff8

Also note that this issue is specific to an experimental React API, `Offscreen`. The React team has [published some early documentation](https://github.com/reactwg/react-18/discussions/19) about this API but it has not been released in a stable form yet.

### What is the current behavior?

A _connected_ component misses updates that are fired while it is inside of a hidden `Offscreen` component.

I believe this is because the component unsubscribes when it is _unmounting_ and does not check for missed updates when it is later remounted. (The selectors passed tot he map-state-to-props function were not executed.)

### What is the expected behavior?

The _expected_ behavior is perhaps up for debate. Should the component process Store updates (at a lower priority) while hidden or should it wait to render them only if it's later re-shown? In a sense, this question isn't worth debating _yet_ because I don't think React currently provides an API (even an experimental one) to _stay subscribed_ while in a hidden state.

That being said, I think the currently expected behavior is that when then `Offscreen` tree is later _re-shown_, React Redux `connect` should check the Store for the latest values and re-render if they have changed since the component was last rendered.

### Which browser and OS are affected by this issue?

Presumably all of them

### Did this work in previous versions of React Redux?

- [ ] Yes

Connect HOC misses store changes when "offscreen"

It seems that pressing shift key while scrolling the mouse wheel has no effect on Windows, contents of the canvas move up or down, instead of left or right. On Mac it works as expected.

I was able to reproduce this with the latest versions of Chrome and Edge on Windows 10.