GitHubTags: #A11yTCS; #A11yAAT; #A11yMAS; #A11y_WindowsTerminal; #WindowsTerminal; #DesktopApp; #C+E-H; #A11ySev1;

Fix and close other bugs before starting accessibility conformance documentation. Any bug that will not be fixed and closed within SLA must be declared in the AAT. The SLA for this bug is also 60 days.
[Guide](https://microsoft.sharepoint.com/teams/ceacc/SitePages/Conformance%20

It would be nice if extraterm could open a new tab when called via it's executable. For example, for a context menu entry.

Hi!

In https://github.com/microsoft/WSL-DistroLauncher#building-project-visual-studio the step states:

You can also easily build and deploy the distro launcher from Visual Studio. To sideload your appx on your machine for testing, all you need to do is right-click on the "Solution (DistroLauncher)" in the Solution Explorer and click "Deploy Solution". This should build the project and side

Somewhere in the guide, when talking about Permissions, I made it clear that there were not any restrictions around permissions, and that users shouldn't have permission issues out of the box (ootb).

But that's incorrect, at least in my case. With a basic guide setup, users cannot navigate to Cookies or other directories on their User/user path. Can someone please try this on their machine with

I've already heard opinions like: "I can not use this on the enterpise." or "This other sudo is just a few lines RunAs script that I can audit myself." (Sure, but building a feature-rich sudo takes far more lines than that.) and the next one probably will be: "I won't run as administrator something from a nobody on the internet."

This is a trust problem. And I cannot create trust by myself.

We should resolve values before showing them.

I just had an issue that I was unable to execute neither wsl-ssh-pageant or wsl-ssh-pageant-gui. Both just exited immediately, without any error message or log file produced. It was quite hard to debug and it took me some time to notice that the SSH_AUTH_SOCK file already existed. Probably some leftover from a previous run. I just deleted the file and it was working again.

It would be goo

gcr.io 国内访问有问题，所以我们开启一个 local server，让 Docker 桌面版从本地拉镜像

• 文档 https://github.com/khs1994-docker/lnmp/blob/master/docs/kubernetes/docker-desktop.md

添加如下 hosts

# 路由器分配给电脑的 IP gcr.io k8s.gcr.io
# 例如

192.168.199.100 gcr.io k8s.gcr.io

启动

首先关闭本地监听 443 端口的程序

$ ./lnmp-docker gcr.io

$ lnmp-docker gcr.io logs

执行完毕之后，Docker 设置中开启 k8s

开启成功之后，删除启动的 lo