sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Remote desktop keybinding not working
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.72.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Remote dekstop keybinds not working

### ✔️ Expected Behavior

binded key to work what it is binded

### ❌ Actual Behavior

binded key works in this pc but not on remote connection pc

### Other Software

Normal windows remote desktop connection
Repository: storybook
Issue: [Bug]: Incorrect code in show code snippet when two props shares same prefix
Labels: bug,needs triage

### Describe the bug

Hello!

Let's take two props, label and labelClass. The second prop has a prefix same as first prop 'label'.  In this case, the show code snippet renders the incorrect code. 

Screenshots:
![image](https://github.com/storybookjs/storybook/assets/24287012/1ee660ed-6000-4d61-b5f6-6ad3fee7e5de)



### To Reproduce

https://stackblitz.com/edit/github-ka9jqq?file=src%2Fstories%2FButton.stories.ts&preset=node

### System

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz
  Binaries:
    Node: 18.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.6.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (116.0.1938.62)
  npmPackages:
    @storybook/addon-a11y: ^7.3.2 => 7.3.2
    @storybook/addon-designs: ^7.0.1 => 7.0.1
    @storybook/addon-essentials: ^7.1.0 => 7.2.1
    @storybook/addon-interactions: ^7.1.0 => 7.2.1
    @storybook/addon-links: ^7.1.0 => 7.2.1
    @storybook/blocks: ^7.1.0 => 7.2.1
    @storybook/testing-library: ^0.2.0 => 0.2.0
    @storybook/vue3: ^7.1.0 => 7.2.1
    @storybook/vue3-vite: ^7.1.0 => 7.2.1
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Incorrect code snippet when using v-bind to bind args inside a render() of a story.
Labels: bug,needs triage

### Describe the bug

Hello!

I am trying to use render() to write custom template for my story.  I am binding my args using 'v-bind' inside my template. However, when the show code renders, it still shows the 'v-bind' in the code snippet, which is wrong.  

When I copy the show code and use it in application, it won't work. For example, let's say I am binding 'label' prop of value 'test'. But the rendered code snippet displays it as 'v-bind:label=''test"'. But there isn't a const/val defined for test. 

**Screenshot**:
![image](https://github.com/storybookjs/storybook/assets/24287012/a6fadf65-c314-42a8-9d93-40bfdf6dd512)


### To Reproduce

https://stackblitz.com/edit/github-ka9jqq?file=src%2Fstories%2FButton.stories.ts&preset=node

### System

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz
  Binaries:
    Node: 18.17.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.6.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (116.0.1938.62)
  npmPackages:
    @storybook/addon-a11y: ^7.3.2 => 7.3.2
    @storybook/addon-designs: ^7.0.1 => 7.0.1
    @storybook/addon-essentials: ^7.1.0 => 7.2.1
    @storybook/addon-interactions: ^7.1.0 => 7.2.1
    @storybook/addon-links: ^7.1.0 => 7.2.1
    @storybook/blocks: ^7.1.0 => 7.2.1
    @storybook/testing-library: ^0.2.0 => 0.2.0
    @storybook/vue3: ^7.1.0 => 7.2.1
    @storybook/vue3-vite: ^7.1.0 => 7.2.1
```


### Additional context

_No response_
Repository: transformers
Issue: replace roberta embedding with bge_base
Labels: New model

### Model description

I'm experimenting Funsd like dataset using layoutLmv3, I'm trying to replace roberta embedding with new bge_large, Is it possible to replace the embedding? will it improve the accuracy?

### Open source status

- [ ] The model implementation is available
- [ ] The model weights are available

### Provide useful links for the implementation

_No response_
Repository: vscode
Issue: ghost text hover screen cheese
Labels: polish,inline-completions

* open https://github.com/microsoft/vscode/blob/3059063b805ed0ac10a6d9539e213386bfcfb852/src/vs/workbench/contrib/snippets/browser/snippetsFile.ts#L63
* type `mark`
* wait for ghost text
* trigger hover via keybinding
* 🧀 the hover looks bad, there is nothing between the arrows and a lone "any" atop

<img width="770" alt="Screenshot 2023-08-29 at 14 32 00" src="https://github.com/microsoft/vscode/assets/1794099/c0a1465b-d474-4715-879f-3014ec0f44d5">
Repository: flutter
Issue: Clear up differences between Form and TextField implementation approaches
Labels: a: text input,framework,f: material design,d: api docs,c: proposal,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

There are different approaches to changing some specific `StatefulWidget`'s state and it's not clear why is it done that way. At least I cannot find docs/comment about that.

When creating forms, recommended way to access form-related methods is to create `GlobalKey<FormState>` and access them from there.

When using `TextField`, recommended way to change field's value or selection is to use `TextEditingController`.

Question is, how come we don't access `TextField`'s methods using `GlobalKey<TextFieldState>` instead of `TextEditingController`? Or similarly, how come there's no `FormStateController`? Is the reason purely historical?

If writing similar widgets to `Form` and `TextField`, which approach should we prefer?

### Proposal

Add documentation/guidelines on what approach to prefer (and why) when designing more complex widgets like `Form` and `TextField` which require accessing methods on their state to do something related to them.
Repository: vscode
Issue: Moved code detection not always working
Labels: feature-request,diff-editor

Testing #191508

- set `"diffEditor.experimental.useVersion2": true` and `"diffEditor.experimental.showMoves": true` and reload VS Code
- clone the VS Code repo and replace `colorThemeData.ts` with the following content: https://gist.github.com/aeschli/9761c73c27de6551950b1b083025ee92
- open the diff editor and find the line starting with `private themeTokenScopeMatchers`



![Image](https://github.com/microsoft/vscode/assets/6461412/00cbb95a-2447-4eff-b8ca-51b526dd9273)

Note that the moved code was not detected

Now revert all changes and manually move the same 4 lines:

![Image](https://github.com/microsoft/vscode/assets/6461412/bace7185-dbfd-4a12-a25d-5f56e04cfe09)

Now the move is detected
Repository: flutter
Issue: [dart:ui] Implement containsRect method
Labels: c: new feature,framework,c: proposal,P2,team-engine,triaged-engine

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

I'm not sure this is the right place to open the issue, as `dart:ui` is, at least the name suggests, a dart library. However, it's hosted in the Flutter engine repo (why???), which does not allow opening issues, so I am opening here.

### Proposal

The suggestion is to implement a method `containsRect` in `Rect`, which would receive another `Rect` and return `true` if the `Rect` received by parameter is entirely contained in the callee `Rect`.

It could be implemented by applying `contains` to the `Rect` four points (`topLeft`, `topRight`, `bottomLeft` and `bottomRight`).
Repository: PowerToys
Issue: key remap is always running and not showing up on remap list
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.72.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

i was remapping some keys on my keyboard. ef_ry thing was working _ine until i restarted my pc after deleting the remaps. after i restated, the remaps were still enabled e_en when keyboard manager was disabled same with the entire process itself being disabled. please fix this i cant type properly :(

### ✔️ Expected Behavior

keyremapping to be deleted or disabled

### ❌ Actual Behavior

continues to remap after restarting with keyboard manager off and the entire process closed.

### Other Software

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: execute VAE on cpu to reduce vram usage in some cases
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Make selective option to do encoding/decoding fully on cpu, while diffusion process will be doing on gpu, this will reduce VRAM usage in some cases on extremely low VRAM amount cards if user don't wants to use taesd. I don't think it's difficult to do this.

### Proposed workflow

-

### Additional information

Similar feature request, but in invokeAI using diffusers https://github.com/invoke-ai/InvokeAI/issues/2408
Repository: TypeScript
Issue: Temp variable re-usage breaks JS when building into single file
Labels: Needs More Info

### 🔎 Search Terms

static

### 🕗 Version & Regression Information

- This changed between versions `5.2.0-beta` and `5.2.1-rc`. I found that this issue appeared in `5.2.0-dev.20230805` build, probably caused by merging https://github.com/microsoft/TypeScript/pull/55262


### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/PTAEGMEMBdwCwHTQM4ChwBtLOaAwjPKAN6qqgUAOArgEYYCW4oy0MToATgKaUD2naAFFOnUAF5QACgCUALlC0+fDN0gA7CQD4S5Cl27RqnTQViI+6kZwEBJddG4nIGABIaAJqs6yA3HoBffz0aeg5WdmZLazsHJ3UXd3UvJwlpeUVlVQ1tXX0DIxNQaE5qbn8KILIqOkZmCOgODz5uZAAlbgArbnBoNOwAT3VmWVzSfJ5CzQAzF2RuQP8AshBQDT5oOCcAWihzJDRMbFwAQXUNrc4zInGasPq2RuYefkEAZT4AW0M4BnUAczSsgUShUak04h0twok2MmjOFyc1ws6g+302f3+SRSPhkFVAVRCtXCjw4ljRP0x2O8QIyoOyEKhehhhjhxVK5UW1VAoTqLFJzGarQ63V6-WQQxGMjGzIKbNmGHmXOWqFW4C+lAYqmKW3moAATKBplrWqA-tA+GsWJjtZZuKAAO4MTagABEKGYe3gBzW502Oy9iBQoG22z41GgADETcVWtAEJ1cKHPnwPNRted1PbQ2xOP9DKBWvqAAwARgA7K6gA

### 💻 Code

```ts
// catch.ts
class Catch {

   public static reportErr = (): boolean => {
    return Catch.onErrorInternalHandler();
  };

  public static onErrorInternalHandler = (): boolean => {
    return true;
  };

  public static doesReject = async () => {
    return false
  };
}

// another-catch.ts
class AnotherCatch {
   public static reportSomething = (): boolean => {
    return AnotherCatch.onSomethingHandler();
  };

  public static onSomethingHandler = (): boolean => {
    return true;
  };

  public static doesReject = async () => {
    return false
  };
}

// compile these 2 files into a single one with "tsc catch.ts another-catch.ts --outFile test.js --module none --target es2017"
```


### 🙁 Actual behavior

In compiled JS it converts to:
```js
var _a;
class Catch {
}
_a = Catch;
Catch.reportErr = () => {
    return _a.onErrorInternalHandler();
};
Catch.onErrorInternalHandler = () => {
    return true;
};
Catch.doesReject = async () => {
    return false;
};
var _a;
class AnotherCatch {
}
_a = AnotherCatch;
AnotherCatch.reportSomething = () => {
    return _a.onSomethingHandler();
};
AnotherCatch.onSomethingHandler = () => {
    return true;
};
AnotherCatch.doesReject = async () => {
    return false;
};
```

Which leads to `_a.onErrorInternalHandler is not a function` error when trying to perform `Catch.reportErr()` later in the code.

### 🙂 Expected behavior

In `5.2.0-beta` it compiled to 
```js
var _a;
class Catch {
}
_a = Catch;
Catch.reportErr = () => {
    return Catch.onErrorInternalHandler();
};
```
And it worked well.

### Additional information about the issue

_No response_
Repository: material-ui
Issue: [docs-infra] TS versions of code is missing from docs
Labels: bug 🐛,scope: docs-infra

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: 

Steps:

1. open https://mui.com/material-ui/react-autocomplete/#country-select
2. select `ts` option
3. code should match with this file https://github.com/mui/material-ui/blob/master/docs/data/material/components/autocomplete/CustomizedHook.tsx but it is displaying code from this file https://github.com/mui/material-ui/blob/master/docs/data/material/components/autocomplete/CustomizedHook.js




### Current behavior 😯

(In chrome)
<img width="1440" alt="Screenshot 2023-08-29 at 6 57 59 PM" src="https://github.com/mui/material-ui/assets/60743144/f0bf8491-98a2-498c-9a66-20b2ea443fff">


### Expected behavior 🤔
(In safari)
<img width="1438" alt="Screenshot 2023-08-29 at 6 58 32 PM" src="https://github.com/mui/material-ui/assets/60743144/80b4a0c6-b966-41d8-ac6a-7e46aa3b4b5d">

Somehow it's working in safari, so i took expected screenshot from safari

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: TypeScript
Issue: `in` operator narrowing (`key in obj`) doesn't work properly when key type is a string union
Labels: Possible Improvement

### 🔎 Search Terms

in operator narrowing union

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about type narrowing

### ⏯ Playground Link

https://www.typescriptlang.org/play?ssl=39&ssc=4&pln=20&pc=1#code/MYewdgzgLgBAYgeQQfQNIFECaBlGBeGAbQHIAzYgGhmJGIF0YBDCGUSKAbgFgAoN6eEjRZsyBADkAMpjHj0+ImXpMW-TrwCWYKAFMATqUbAd8ECBgBvXjBsxSALhjQ9WgObcetmCEfO3HgF9eXjUYXQECAAotAAcAVyhHODMYAB9LAIBKfAA+S2tbRBQMHAA6UhA9dCMAC0jIgGsdAE9svDyrTy9bDVIYRpaYLSGweKhs-hAAGx1SqZBXaNGEwibmukyPLyytwqES0QlpWXRyyurgOoHW3Pyu7qG+65GRsYnwCGnZ+cXYlbWNrsbDteAEPMEeAB6SFhPTNNxhcx6HQxPQgAAmcWMYRqJlRIAARjMALYwADuGigNScGmJMRmehgcQgJmAzB0EHsEOhrHZMAAjCEPrADvyFCRGJRqATlMxWMKPKFCQArMUECyMRzESVUAlamVg3iis5VWrPdp3Ly9fprF4q-nvSBfOYLSL21YtQGgzbcmFslkwABMQvYMAOgfF2qlxBlDDlakVwu8BOVEfVmuoksNPHDJoudVtFs6VqetuGKsDjs+MxdiwrHvWmxgPIAKrh9Gi9CwybiwENYBAaiA4lN0WBiFAqHKySZGMimRAEQADLRLmBgOdoilgVxOcxUxiwKkmGPEGD4mL6KDNJjAYwQFjokAc8ewGqMGKXsDe8FQv18gBmEMBAOADI1jFR5XYRNQxVMD0y1LMOGbGFQJgJ8OXXEBYDYKBGGGRgwBvNYWBAPo4KNEQALzM1Cw6AobGtZ5yxTACq2dH43VYhtARQx4YDbGAO0qFhhn9ExAyoY8+0pJwhxHdEYFxecoBSAkEn7dDnwgV8YAAQgMn8gA

### 💻 Code

```ts
// case 1
const KEYS1 = ['a', 'b'] as const;
const obj1 = {a: 'a', b: 'b'};
KEYS1.forEach(key => {
    if (key in obj1) console.log(obj1[key]);
});

// case 2
const KEYS2 = ['a', 'b'] as const;
const obj2 = {a: 'a'};
KEYS2.forEach(key => {
    if (key in obj2) console.log(obj2[key]); // TS errors when it shouldn't, as we are using `in` narrowing so that the 'b' property access doesn't happen
});

// case 3
const KEYS3 = ['b'] as const;
const obj3 = {a: 'a'}; // KEYS3 does not contain any keys of obj3
KEYS3.forEach(key => {
    if (key in obj3) console.log(obj3[key]); // if TS errors in case 2, then it should here too but it doesn't !!!
});
```


### 🙁 Actual behavior

- in case 2  TS errors when it shouldn't, as we are using `in` narrowing so that there is no incorrect 'b' property access
- in case 3 TS doesn't give any errors, when consistency disctates that it should if it did in case 2...

### 🙂 Expected behavior

Typescript shouldn't detect any errors in case 2. The type narrowing with the `in` operator ensures that we are only accessing properties that actually exist.

### Additional information about the issue

_No response_
Repository: vscode
Issue: Go to Next/Previous in notification accessible view is not disabled
Labels: bug,accessibility,workbench-notifications

Testing #191345

1. Enable screen reader accessibility mode
2. Cause 1 notification to show (I did https://github.com/microsoft/vscode/issues/191619)
3. Focus the notification and `alt+F2`
4. The accessible view shows.
5. In the top right of the accessible view, there are go to next and previous actions. They are clickable, but they do nothing since there's only one notification. I would expect them to be disabled.
Repository: storybook
Issue: [Bug]: story rendering order influences the order of the CSS styles in the head
Labels: bug,core,sev:S2

### Describe the bug

As discovered some years ago in #13515 the name of the story defines in which order the imported styles from the component are added to the head. So if I change the name of a story, or delete the story, or force a rerender the look of a component could change.

### To Reproduce

https://stackblitz.com/edit/github-64tjnp

<img width="166" alt="image" src="https://github.com/storybookjs/storybook/assets/16589094/83c922ab-625d-42e2-92c9-d47975c6237d">

`AHeader` imports `header.module.scss` so it is added first in the head.
`ZHeader` imports `header.module.scss` again, but it's already in the head.
As a result, the button turns green because `button.modules.scss` is added to the head after `header.module.scss`.
<img width="523" alt="image" src="https://github.com/storybookjs/storybook/assets/16589094/8cffa90d-ca0c-41bd-9f34-b42271f842f9">

If I simply resize the window, the order changes and the button turns red.
![Kapture 2023-08-29 at 15 53 09](https://github.com/storybookjs/storybook/assets/16589094/6c52ed57-289d-4b7d-aa67-28b9239f8bfa)


### System

_No response_

### Additional context

_No response_
Repository: vscode
Issue: Keyboard binding suggested for open ended question does not bring over my question
Labels: bug,polish,quick-open,quick-chat

Testing #191496

Asking anything in command palette puts the chat option last with a keybinding. Invoking that does not take my question over though:



![Image](https://github.com/microsoft/vscode/assets/900690/57f6ac8d-6d5e-4001-9960-eb6b94e557be)
Repository: terminal
Issue: Running emacs in terminal leads to scrambled text input
Labels: Area-VT,Issue-Bug,Product-Terminal,Priority-2

### Windows Terminal version

1.17.230526001

### Windows build number

10.0.19045.0

### Other Software

"GNU Emacs 29.1 (build 1, x86_64-pc-linux-gnu)" with org-mode v9.6.8 (inside WSL2)

### Steps to reproduce

Configure emacs to use org-mode and type some text in a line.
Now move on that line to remove and insert text at arbitrary positions, i. e. type " a some characters ".

### Expected Behavior

The new text is exactly as typed.

### Actual Behavior

The cursor is jumping involuntary to the beginning of and back to typing position in line meanwhile garbling the text you already typed in unpredictable manner.
Repository: vscode
Issue: Consider a keyboard shortcut for changing quick chat size
Labels: feature-request,quick-chat

Testing #191496

For people that cannot use the mouse it would be nice to have keybindings to grow/shrink quick chat sizes.
Repository: rust
Issue: Failed to compile a project with LTO + PGO
Labels: A-LLVM,T-compiler,C-bug,A-LTO,A-PGO

In https://github.com/vectordotdev/vector/issues/15631#issuecomment-1694554798 I tried to optimize [Vector](https://vector.dev) with LTO + PGO enabled. But during the optimization phase (done with `cargo pgo optimize`) I get the following error: https://github.com/Kobzol/cargo-pgo/issues/32#issuecomment-1694445787 . I am not the only person with this error - https://github.com/llvm/llvm-project/issues/57501#issuecomment-1694392182 (@kevincox probably can provide more details about they project).

The only way to avoid the bug is disable LTO completely (switching from Fat to Thin mode does not help).

I expected to see this happen: Vector compiles successfully with LTO and PGO enabled.

Instead, this happened: Vector failed to compile with LTO + PGO.

### Meta
`rustc --version --verbose` (from https://github.com/vectordotdev/vector/blob/master/rust-toolchain.toml):
```
1.71.1
```
Other links:
* Possibly related bug in LLVM (but I am not sure): https://github.com/llvm/llvm-project/issues/57501
* A discussion in `cargo-pgo`: https://github.com/Kobzol/cargo-pgo/issues/32

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"DianQK"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: material-ui
Issue: [docs-infra] Double vertical scrollbars
Labels: design,scope: docs-infra

### Related page

- https://mui.com/joy-ui/react-autocomplete/
- https://mui.com/material-ui/react-autocomplete/

### Kind of issue

Other

### Issue description

Double vertical scrollbars

### Context 🔦

Going to any pages under Components sections on Joy page

I use Edge Version 116.0.1938.54 on linux-x64, the same with Firefox 116.0.3 on linux-x64
Docs version: v5.0.0-beta.4
Repository: flutter
Issue: [web] `EngineFlutterDisplay` should keep `size` and `refreshRate` up-to-date
Labels: engine,platform-web,P2,team-web,triaged-web

These values could change at any time. Examples:
- When the user resizes the window.
- When the user moves the window to another display.
Repository: ant-design
Issue: Antd Tabs Horizontal Scroll using Left Right buttons
Labels: Inactive,🧶 Low Priority

### What problem does this feature solve?

The proposed feature aims to address the need for horizontal scrolling within Ant Design's Tabs component using left and right navigation buttons. Currently, the Tabs component provides tab navigation primarily through clickable tabs. However, in scenarios where there are a large number of tabs and they don't fit within the available width, users may have difficulty navigating to tabs that are not immediately visible. Introducing horizontal scrolling with navigation buttons will enhance user experience by allowing them to scroll through hidden tabs and access all tab options easily.

### What does the proposed API look like?

The proposed API for implementing horizontal scroll using left and right buttons in Ant Design's Tabs component might look like the following:

<Tabs
  // ... other props ...
  showScrollButtons={true} // Enable the new feature
  scrollButtonStyle={{
    leftButton: { /* styles for left scroll button */ },
    rightButton: { /* styles for right scroll button */ }
  }}
/>

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: deno
Issue: Deno stalls out after ~9500 concurrent `fetch()` requests in EasyRacer structured concurrency suite scenario 3
Labels: bug,perf,needs investigation

I'm trying to implement a Deno version of [EasyRacer](https://github.com/jamesward/easyracer), and all scenarios are passing except for scenario `3` which makes 10,000 concurrent requests. When monitoring the scenario server, it appears that it climbs up to about ~9500 requests before stalling out.

I recognize that this isn't a normal use case; it's designed to test the capabilities of a system rather than be a guide for optimal usage. However, there are successful implementations for Scala, Java, Kotlin, Swift, Rust, and Go.

Here is a link to my implementation: https://github.com/cowboyd/easyracer/tree/main/javascript-effection
Repository: vscode
Issue: Unexpected tab order in moved code
Labels: polish,diff-editor

Testing #191508

1. Toggle tab moves focus.
2. Focus into the editor above a moved code block
3. Tab. I'm not sure what's getting focus now. If you have a screen reader on it reads "Code moved with changes..."
4. Tab a second time. The element with "Code moved with changes..." is now visibly focused and is read again.