sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [bug] error[E0432]: unresolved import `wry::webview::WebviewExtUnix`
Labels: type: bug,status: needs triage

### Describe the bug

```
error[E0432]: unresolved import `wry::webview::WebviewExtUnix`
    --> core/tauri-runtime-wry/src/lib.rs:2193:23
     |
2193 |                   use wry::webview::WebviewExtUnix;
     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `WebviewExtUnix` in `webview`
     |
note: found an item that was configured out
    --> /usr/ports/devel/tauri/work/tauri-1.0.5/cargo-crates/wry-0.19.0/src/webview/mod.rs:576:11
     |
576  | pub trait WebviewExtUnix {
     |           ^^^^^^^^^^^^^^
     = note: the item is gated behind the `linux` feature

error[E0046]: not all trait items implemented, missing: `skip_taskbar`
   --> core/tauri-runtime-wry/src/lib.rs:730:1
    |
730 | impl WindowBuilder for WindowBuilderWrapper {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing `skip_taskbar` in implementation
    |
    = help: implement the missing item: `fn skip_taskbar(self, _: bool) -> Self { todo!() }`

error[E0599]: no method named `webview` found for struct `Arc<wry::webview::WebView>` in the current scope
    --> core/tauri-runtime-wry/src/lib.rs:2194:23
     |
2194 |                   f(w.webview());
     |                       ^^^^^^^ private field, not a method

error[E0599]: no method named `gtk_window` found for enum `WindowHandle` in the current scope
    --> core/tauri-runtime-wry/src/lib.rs:2286:40
     |
1545 | enum WindowHandle {
     | ----------------- method `gtk_window` not found for this enum
...
2286 |               tx.send(GtkWindow(window.gtk_window().clone())).unwrap()
     |                                        ^^^^^^^^^^ method not found in `WindowHandle`
     |
     = help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope; perhaps add a `use` for it:
     |
7    + use wry::application::platform::unix::WindowExtUnix;
     |

Some errors have detailed explanations: E0046, E0432, E0599.
For more information about an error, try `rustc --explain E0046`.
error: could not compile `tauri-runtime-wry` (lib) due to 4 previous errors
```

### Reproduction

_No response_

### Expected behavior

n/a

### Full `tauri info` output

```text
n/a
```


### Stack trace

_No response_

### Additional context

Version: 1.0.5
rust-1.74.1
FreeBSD 14.0
Repository: rust
Issue: Missed layout optimisation with multiple niches
Labels: T-compiler,A-layout,C-optimization

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
use std::num::NonZeroU8;

struct Test {
    niche_one: NonZeroU8,
    niche_two: NonZeroU8,
}

fn main() {
    assert_eq!(
        std::mem::size_of::<Test>(),
        std::mem::size_of::<Option<Option<Test>>>()
    );
}
```

I expected this program to exit fine, and fit the tag of the second option in the available niche. 
Instead, the program panics, as the second option wastes a byte of memory making it's own tag byte.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.77.0-nightly (e51e98dde 2023-12-31)
binary: rustc
commit-hash: e51e98dde6a60637b6a71b8105245b629ac3fe77
commit-date: 2023-12-31
host: x86_64-unknown-linux-gnu
release: 1.77.0-nightly
LLVM version: 17.0.6
```
Repository: neovim
Issue: TUI: support being used as a "renderer" even when stdio not a PTY
Labels: bug,tui,has:bisected

### Problem

Using neovim as a previewer for FZF is broken, the textfile is not displayed in the preview window - this is a regression.

This problem does not exist in NVIM v0.8.4 (commit b1ae775de618e3e87954a88d533ec17bbef41cdf) but does exist in master and NVIM v0.9.6 (commit 3a80c6ad18804ade71b9c59321592d391645bbd9):






### Steps to reproduce

echo "foobar" | fzf --preview "nvim -R somefile.txt"

### Expected behavior

The text file should be displayed in the preview window

### Neovim version (nvim -v)

master

### Vim (not Nvim) behaves the same?

sort of

### Operating system/version

FreeBSD 14

### Terminal name/version

urxvt

### $TERM environment variable

xterm-256color

### Installation

from source
Repository: go
Issue: cmd/cgo: const in c translate to go const without obey original type. 
Labels: NeedsFix,compiler/runtime

### Go version

go version go1.21.5 darwin/amd64

### What operating system and processor architecture are you using (`go env`)?

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/Users/acorn/Library/Caches/go-build'
GOENV='/Users/acorn/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/acorn/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/acorn/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/acorn/workspace/programming/golang/go1.21.5'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/acorn/workspace/programming/golang/go1.21.5/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='go1.21.5'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/n1/750_y87d4cx826dsgx4rrd9r0000gn/T/go-build1840385617=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

*reg2expand.go*
```go
package main

// size_t var1 = ~(size_t)0;
// const size_t const1 = ~(size_t)0;
import "C"
import "log"


func main() {
	println(C.var1)
	// 18446744073709551615
	println(C.const1)
	// -1
	log.Println(C.var1 == C.const1)
	// (_Ciconst_const1) (untyped int constant -1) overflows uint64
}

```
```bash
❯ go build ./reg2expand.go  
# command-line-arguments
./reg2expand.go:12:20: (_Ciconst_const1) (untyped int constant -1) overflows uint64
```

##### 1. compile error happen when:
a unsigined type c const with a value bigger than go math.MaxInt.
when this translated const compare with same type c variable or const.

##### 2.why
cgo translate a const in this case to a negative value.
*_cgo_gotypes.go*
```go
var _Cvar_var1 *_Ctype_size_t = (*_Ctype_size_t)(unsafe.Pointer(&__cgo_var1))
const _Ciconst_const1 = -0x1
```
##### 3. questiont source
c pcre2 library has a const named PCRE2_UNSET.
```c
#define PCRE2_UNSET           (~(PCRE2_SIZE)0)
```
when check whether a group  is set come with compiler error.

##### 4. temp workaround
define a same type variable whith the const value.
```go
package main

// #cgo pkg-config: libpcre2-8
// #define PCRE2_CODE_UNIT_WIDTH 8
// #include <pcre2.h>
// PCRE2_SIZE GOPCRE2_UNSET = PCRE2_UNSET;
// PCRE2_SIZE mockVectorIndex = PCRE2_UNSET;
import "C"

func main() {
	println(C.mockVectorIndex == C.GOPCRE2_UNSET)
}
```

### What did you expect to see?

>go tool cgo  reg2expand.go 

*_cgo_gotypes.go*
```go
const _Ciconst_const1 = 18446744073709551615
```

### What did you see instead?

>go tool cgo  reg2expand.go 

*_cgo_gotypes.go*
```go
const _Ciconst_const1 = -0x1
```
Repository: next.js
Issue: Static Export HTML content missing in "out" whenever imports "next/image"
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://github.com/alexchu-dev/next-js-image-bug-export

### To Reproduce

To Reproduce
Create a new next.js project using npx create-next-app@latest
Options: Selected Eslint only,  selected "No" on all others.

Add output: "export" to next.config.js.

npm run build
![image](https://github.com/vercel/next.js/assets/61229735/c82c200a-e822-4a2d-899a-18c312812c2c)


The "out" folder contains only a "_next" folder, without html etc.
![image](https://github.com/vercel/next.js/assets/61229735/bd8b1a39-5d58-4113-80e9-c3b7481502ad)




### Current vs. Expected behavior

Current: The"out" folder contains only a "_next" folder, without html etc.
Expected: All files exported.

Figured out when the line of **import Image from 'next/image'** is removed, the HTML files and other contents would be back.


### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 21.5.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.5-canary.34
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

Image optimization (next/image, next/legacy/image), Static HTML Export (output: "export")

### Additional context

_No response_
Repository: ant-design
Issue: 能提供：通过点击其他按钮等行为触发 Mentions 菜单打开么
Labels: 📝 Documentation,Inactive,unconfirmed

### What problem does this feature solve?

页面上点击按钮，自动插入 `prefix` 比如 `@` 到 mentions 输入框中，但是无法触发选择列表，必须得手动再键盘输入内容才可以，不方便

### What does the proposed API look like?

能够有办法唤起下拉输入选择框

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: PowerRename  Black screen not responding
Labels: Issue-Bug,Product-PowerRename,Needs-Triage

### Microsoft PowerToys version

0.76.2

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce

[PowerToysReport_2024-01-02-13-20-21.zip](https://github.com/microsoft/PowerToys/files/13807325/PowerToysReport_2024-01-02-13-20-21.zip)
When renaming a file name ending with"1", it will get stuck

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: transformers
Issue: LLaMA-MoE
Labels: New model

### Model description

LLaMA-MoE is a series of token-choice based Mixture-of-Experts models on LLaMA2. It first partition LLaMA2's FFNs into multiple experts, then apply continual pre-training to recover its language abilities.

We believe LLaMA-MoE is a good start for MoE research under limited computing resources.

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Our repo: https://github.com/pjlab-sys4nlp/llama-moe
HF models (currently set `trust_remote_code=True`): https://huggingface.co/llama-moe
Repository: TypeScript
Issue: In WebView, using Map is not possible.
Labels: Needs Investigation

### 🔎 Search Terms

"iterator", "iterable", "Map", "WebView"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `__values`.


### ⏯ Playground Link

_No response_

### 💻 Code

```ts
// Your code here
```


### 🙁 Actual behavior

I am using RN with a WebView, and the web application uses [class-validator](https://github.com/typestack/class-validator/tree/develop). I encountered an error stating 'Object is not iterable.' Upon investigation, I found that the issue comes from the transformation of `for...of` loops to `__values` in esm5. (the original code is [here](https://github.com/typestack/class-validator/blob/develop/src/metadata/MetadataStorage.ts#L119C52-L119C52))

The class-validator uses `Map` and it does not have the property `length`. And in WebView the `m` is `undefined` in the following compiled `__values`. Hence the error is shown.

```javascript
var __values = (this && this.__values) || function(o) {
    // here, o is from the return value of Map instance's entries.
    var s = typeof Symbol === "function" && Symbol.iterator, m = s && o[s], i = 0;
    if (m) return m.call(o);
    if (o && typeof o.length === "number") return {
        next: function () {
            if (o && i >= o.length) o = void 0;
            return { value: o && o[i++], done: !o };
        }
    };
    throw new TypeError(s ? "Object is not iterable." : "Symbol.iterator is not defined.");
};
```

So, I fix this issue like following temporarily.

```javascript
var __values = (this && this.__values) || function(o) {
    var s = typeof Symbol === "function" && Symbol.iterator, m = s && o[s], i = 0;
    if (m) return m.call(o);
    if (o && typeof o.length === "number") return {
        next: function () {
            if (o && i >= o.length) o = void 0;
            return { value: o && o[i++], done: !o };
        }
    };
    if (o.next) return o; // add this line
    throw new TypeError(s ? "Object is not iterable." : "Symbol.iterator is not defined.");
};
```

This issue occurs not only with `Map` but also when using `Set` in WebView.

### 🙂 Expected behavior

I can use `Map` and `Set` in WebView.

### Additional information about the issue

_No response_
Repository: ollama
Issue: Please add TinyGPT-V model support
Labels: model request

TinyGPT-V: Efficient Multimodal Large Language Model via Small Backbones

Github: https://github.com/DLYuanGod/TinyGPT-V
HuggingFace: https://huggingface.co/Tyrannosaurus/TinyGPT-V

It stands out because it only requires a 24G GPU for training, and just an 8G GPU or CPU for inference. TinyGPT-V is based on Phi-2, combining an effective language backbone with pre-trained visual modules from BLIP-2 or CLIP.
Repository: next.js
Issue: [Next.js] Attribute removal doesn't work on inputProps in TextField (MUI)
Labels: bug

### Link to the code that reproduces this issue

https://github.com/AdamZajler/mui-attribute-removal-ex/tree/main

### To Reproduce

1. Create component like
```<TextField  data-cy="test1" inputProps={{ "data-cy="test2" }} />```
2. Set nextjs config to
```
compiler: {
    reactRemoveProperties: { properties: ['^data-cy'] },
  }
```
3. Build your application
4. Input tag of TextField shouldn't have data-cy attribute, but it has.

### Current vs. Expected behavior

For ex. we have component like this:

`<TextField 
data-cy="test1"
inputProps={{ "data-cy="test2" }}
/>`
. And also we have set compiler options in next.config.js to:

```
compiler: {
    reactRemoveProperties: { properties: ['^data-cy'] },
  }
```
After build, attributes will be removed from wrappers of <input/> element, but not from a <input/> itself :o

This issue dosent exists on other components like vanilla input tag, only on TextField etc.

Expected behavior === Attributes will be removed everywhere.

**MUI marked this issue as from the Next itselft https://github.com/mui/material-ui/issues/40091**

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

_No response_
Repository: vscode
Issue: Add vso.* scopes support for Microsoft authentication provider
Labels: feature-request,upstream,microsoft-authentication

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

I have an extension which needs to access Azure Devops resources, right now we can use the old ADO scope `499b84ac-1321-427f-aa17-267ca6975798/.default` which gets access to all ADO resources. For some time this was the only option available.

ADO recently added support for smaller scopes, described here https://learn.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/oauth?view=azure-devops#scopes, and the release announcement https://devblogs.microsoft.com/devops/new-azure-devops-scopes-now-available-for-microsoft-identity-oauth-delegated-flow-apps/.

We want to switch over to using the smaller scopes as our extension doesn't usually need the full scope https://github.com/microsoft/ado-codespaces-auth/issues/11. 

However it seems the current VSCode client app doesn't support these new scopes 
![image](https://github.com/microsoft/vscode/assets/2021979/2a83f5db-e18a-40ae-a4f6-76ef8a52ad9f)

It would be great if the VSCode team could add support for these new scopes as well, considering we already have the earlier full scope authorized it shouldn't be that much of a stretch to get permissions for the smaller scopes 😊
Repository: PowerToys
Issue: power rename is not showing on cotext menu
Labels: Issue-Bug,Product-PowerRename,Needs-Triage

### Microsoft PowerToys version

0.76.2

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce

![image](https://github.com/microsoft/PowerToys/assets/101933777/3cbfcfd5-cdc9-4fc1-ad36-ebb49bb6acef)
![image](https://github.com/microsoft/PowerToys/assets/101933777/67435413-ea72-4c93-8f90-f995b5d07341)


### ✔️ Expected Behavior

hold shift then hit menu button to show power rename

### ❌ Actual Behavior

i just had normal menu 

### Other Software

_No response_
Repository: PowerToys
Issue: Full Screen Remote Desktop with Key Remap on both server and client causes key to be sent twice.
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.76.2

### Installation method

Chocolatey

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

(I originally found the issue using Vim and multi-cursor mode in VsCode, this is the simplest repro I could come up with)

1. You need two computers with the same key mapping: _e.g._ `Caps Lock` remapped to `ESC` on both.
2. Remote Desktop with Full Screen on the Server.
3. Open a remote browser to https://skill-test.net/keyboard-test
4. Hit `Caps Lock`
5. You'll see that two `ESC` are received by the keyboard tester
6. 
![image](https://github.com/microsoft/PowerToys/assets/467692/616152b2-7fe2-47d9-93ba-022161659df8)

Note: If RDP is in Windowed mode, then only one `ESC` is send / received (as expected)

### ✔️ Expected Behavior

Only one `ESC` should be sent (received) to the Remote Server

### ❌ Actual Behavior

Two `ESC` are sent (or perceived sent).

### Other Software

Windows' Remote Desktop
Local: Windows 10 Pro Version 22H2 (build 19045.3803)
Remote: Windows 11 Pro Version 23H2 (build 22631.2861)
Repository: rust
Issue: TAIT applies type constraints backwards where variable type is already fully constrained
Labels: A-diagnostics,T-compiler,C-bug,F-type_alias_impl_trait

This code works:
```rust
use core::ptr;
fn foo() -> impl Fn() {
    {
        fn bar(_: *const impl Sized) {}
        let p = ptr::null();
        if false {
            // This constrains the type of the pointer p
            return unsafe { ptr::read(p) };
        }
        bar(p);
    }
    || {}
}
```


~~However, the equivalent code using TAIT doesn't work.~~(edit: Yes, I see, this is not equivalent and the issue seems to be more about the incorrect error message and not that it doesn't work) Calling `foo` with argument `p` should constrain the impl Trait, but the constraints are applied backwards instead:

```rust
#![feature(type_alias_impl_trait)]
use core::ptr;
fn foo() -> impl Fn() {
    {
        type ReturnType = impl Sized;
        fn bar(_: *const ReturnType) {}
        let p = ptr::null();
        if false {
            // This constrains the type of the pointer p
            return unsafe { ptr::read(p) };
        }
        bar(p);
    }
    || {}
}
```

```
error[E0277]: expected a `Fn()` closure, found `ReturnType`
 --> src/main.rs:3:13
  |
3 | fn foo() -> impl Fn() {
  |             ^^^^^^^^^ expected an `Fn()` closure, found `ReturnType`
  |
  = help: the trait `Fn<()>` is not implemented for `ReturnType`
  = note: wrap the `ReturnType` in a closure with no arguments: `|| { /* code */ }`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `fooobar` (bin "fooobar") due to 1 previous error
```

`rustc --version --verbose`:
```
rustc 1.77.0-nightly (e51e98dde 2023-12-31)
binary: rustc
commit-hash: e51e98dde6a60637b6a71b8105245b629ac3fe77
commit-date: 2023-12-31
host: x86_64-unknown-linux-gnu
release: 1.77.0-nightly
LLVM version: 17.0.6
```

</p>
</details>
Repository: material-ui
Issue: [material-ui][Text Field] `autoFocus` prop not working consistently with a Next.js App Router project
Labels: external dependency,component: text field,package: material-ui,nextjs

### Search keywords
`TextField`, `autoFocus`, `NextJs`, `App Router`

### Latest version
- [x] I have tested the latest version

### Steps to reproduce

Link to live example: https://codesandbox.io/p/devbox/ecstatic-boyd-js7l82

### Current behavior

When using the `TextField` component with the `autoFocus` prop in a Next.JS App Router project, the autofocus feature does not work as expected.

1. The `TextField` is not focused upon the initial page load or when the page is refreshed.
2. However, the `autoFocus` feature works correctly when there is a tab change in the browser window or when navigating between pages within the app.

### Expected behavior

We expect the `TextField` with the `autoFocus` prop to consistently focus on the input element under the following scenarios:

1. On the initial page load.
2. When the page is refreshed.
3. When navigating between pages within the app.
4. When there is a tab change in the browser window.

This consistency in autofocus behavior is crucial for a smoother user experience in our Next.JS App Router project.

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD 
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD  
  Browsers:
    Chrome: Not Found
    Edge: Chromium (120.0.2210.91)
  npmPackages:
    @emotion/react: latest => 11.11.3
    @emotion/styled: latest => 11.11.0
    @mui/base:  5.0.0-beta.29
    @mui/core-downloads-tracker:  5.15.2
    @mui/icons-material: latest => 5.15.2
    @mui/material: latest => 5.15.2
    @mui/private-theming:  5.15.2
    @mui/styled-engine:  5.15.2
    @mui/system:  5.15.2
    @mui/types:  7.2.11
    @mui/utils:  5.15.2
    @types/react: latest => 18.2.46
    react: latest => 18.2.0
    react-dom: latest => 18.2.0
    typescript: latest => 5.3.3
```
</details>
Repository: PowerToys
Issue: Layout reset for FancyZones
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

A simple keyboard shortcut to reset the order of visibility for windows.

For example, suppose you have multiple windows and they're all 800x800 and offset in height by 100 pixels each, so that they overlap 700 pixels. If the first window is selected, then the second window is completely hidden. It would be helpful to have a shortcut that restores the original order so they could be quickly accessed. Amazing drawing included!

![Illustration](https://github.com/microsoft/PowerToys/assets/83516072/84a29124-b4ef-402b-b750-460f4545b7eb)


### Scenario when this would be used?

When multiple windows overlap and one is completely hidden

### Supporting information

_No response_