text:
Updated post 1903 log location

These logs moved in 1903.

@greg-lindsay The PR that expands the description on Windows Autopilot log location is available for review. Thanks.

@greg-lindsay Following up for updates.

And if Greg is busy with lots of other work assignments, maybe @lizap could help out with final review and merge the PR if all is well?

The only other change I can think of (although far from required), is to add separate bullet points both for the 1903 and the 1803 location description within this PR content. Then again, looking at the rest of the affected page, it could result in an overuse of bullet points, making it look like almost all the descriptive text uses bullet points.

@greg-lindsay @martyav Would you be able to review this PR as the time permits? Thanks.

@greg-lindsay @martyav Following up for updates.

@jeffgilb : Are you able to resolve the conflict between your PR file content and the master branch file troubleshooting.md ? Or would you like some help with that?

@jeffgilb Would you be able to resolve merge conflicts with the file troubleshooting.md ? We would like to merge your contributions. Thanks.

It looks like the entire article is a conflict now somehow?!

Yes, this is because someone else updated the same page while you were waiting for your PR to be reviewed. These things happen some times, so we need to deal with this type of change too.

@jeffgilb Please let us know whenever the conflicts are resolved. Thanks.

Feel free to ask for help, in case you find the conflict difficult or too hard to resolve.

I’m in training all week until around 8pm everyday. If there’s a way to easily resolve this, please do. I only changed one small section so not sure why the entire thing is conflicting now and don’t really have the bandwidth to figure out completely what is going on.
Thanks
~Jeff
From: Trond B. Krokli notifications@github.com
Sent: Thursday, August 15, 2019 12:41 PM
To: MicrosoftDocs/windows-itpro-docs windows-itpro-docs@noreply.github.com
Cc: Jeff Gilbert Jeff.Gilbert@microsoft.com; Mention mention@noreply.github.com
Subject: Re: [MicrosoftDocs/windows-itpro-docs] Updated post 1903 log location (#4581)
Feel free to ask for help, in case you find the conflict difficult or too hard to resolve.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fpull%2F4581%3Femail_source%3Dnotifications%26email_token%3DADB5ARCGTFELHYX5NJZX2LLQEWILRA5CNFSM4IHW7PVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4MPSMQ%23issuecomment-521730354&data=02|01|Jeff.Gilbert%40microsoft.com|e261f1c831ab425e99c408d721a7c3f5|72f988bf86f141af91ab2d7cd011db47|1|0|637014876772058698&sdata=vB6oqGSFGexjv3c9hojsGumigC4xXvn5OibAYKMSfHM%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADB5ARDRFJZRPMSTJ3AHG3LQEWILRANCNFSM4IHW7PVA&data=02|01|Jeff.Gilbert%40microsoft.com|e261f1c831ab425e99c408d721a7c3f5|72f988bf86f141af91ab2d7cd011db47|1|0|637014876772068687&sdata=u3p%2BiDH09nBKGI7v9HkCpxRvdlHblQDdsN9iWLaFY5Y%3D&reserved=0.

The reason PR files get conflicts is because there will always be someone else will find it necessary to change some other part of the file, and that change can be merged into the source code before your suggested change makes it there. That happens a lot, because of the hundreds, maybe thousands of people working on the very same source tree as you do. Some times, housekeeping of a long list of files is done by admins, or the PR content file you are working on may simply be on hold for another index change while you are still waiting for your change to become accepted by the admins. Meanwhile, conflicts occur, because you have not kept your personal fork of the repository up to date with the Microsoft source (your fork, jeffgilb/windows-itpro-docs is currently 447 commits behind MicrosoftDocs:master).

The simple explanation is that 1 line got inserted between line 11 and 12 (addition of a New line 12) in the target file (https://github.com/MicrosoftDocs/windows-itpro-docs/blob/master/windows/deployment/windows-autopilot/troubleshooting.md):
 ---
 title: Troubleshooting Windows Autopilot
 description: Windows Autopilot deployment
 keywords: mdm, setup, windows, windows 10, oobe, manage, deploy, autopilot, ztd, zero-touch, partner, msfb, intune
 ms.reviewer: mniehaus
 manager: laurawi
 ms.prod: w10
 ms.mktglfcycl: deploy
 ms.localizationpriority: medium
 ms.sitesec: library
 ms.pagetype: deploy
+audience: itpro
 author: greg-lindsay
 ms.author: greglin
 ms.collection: M365-modern-desktop
 ms.topic: article
 ---

Also worth noticing: Besides the PR author (you), it will only be possible for the Microsoft Docs team administrators (authors and managers) to merge, edit and make changes to the PR content. All the rest of us can only comment here in the dialogue page or in the code, suggest changes via code comments or open pull requests ourselves. (Although, if you think it will be any easier to accept a pull request into your own repository than to edit your file to add a new line number 12 with my highlighted text above, feel free to tell me and I will clone your repository to my computer to create the PR for this change.

Ok, if you can’t make the merge happen, just close the PR.
If you need to do that then I’ll just make a new one when I get time in the private repo.
From: Trond B. Krokli notifications@github.com
Sent: Thursday, August 15, 2019 2:04 PM
To: MicrosoftDocs/windows-itpro-docs windows-itpro-docs@noreply.github.com
Cc: Jeff Gilbert Jeff.Gilbert@microsoft.com; Mention mention@noreply.github.com
Subject: Re: [MicrosoftDocs/windows-itpro-docs] Updated post 1903 log location (#4581)
Also worth noticing: Besides the PR author (you), it will only be possible for the Microsoft Docs team administrators (authors and managers) to merge, edit and make changes to the PR content. All the rest of us can only comment here in the dialogue page or in the code, suggest changes via code comments or open pull requests ourselves. (Although, if you think it will be any easier to accept a pull request into your own repository than to edit your file to add a new line number 12 with my highlighted text above, feel free to tell me and I will clone your repository to my computer to create the PR for this change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-itpro-docs%2Fpull%2F4581%3Femail_source%3Dnotifications%26email_token%3DADB5ARBRZFCXHB6WX5SX733QEWSBZA5CNFSM4IHW7PVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4MWOFA%23issuecomment-521758484&data=02|01|Jeff.Gilbert%40microsoft.com|96ea051fe7304b2922e908d721b352c9|72f988bf86f141af91ab2d7cd011db47|1|0|637014926391367053&sdata=ywQWcDlhymkQYv6m31J8Gbfrn%2FzLhFrdUvK4QILgKHw%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADB5ARABVFTBV3R5MUKSWK3QEWSBZANCNFSM4IHW7PVA&data=02|01|Jeff.Gilbert%40microsoft.com|96ea051fe7304b2922e908d721b352c9|72f988bf86f141af91ab2d7cd011db47|1|0|637014926391367053&sdata=8eDTePFALbZ8LuLU8%2FQpFtaZt6vZ0wTSURMZD915VA4%3D&reserved=0.

Ok, if you can’t make the merge happen, just close the PR. If you need to do that then I’ll just make a new one when I get time in the private repo.

Closing as suggested. Thank you for taking the time to contribute to the repository.

@officedocsbot close

authors: e0i illfated jeffgilb


text:
Resolves #2581

Fix example title
https://github.com/MicrosoftDocs/windows-powershell-docs/issues/2581

Docs Build status updates of commit 68ba9be:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 85a7aa8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e8f94ea:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (winserver2012r2-ps)

docset/winserver2016-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/activedirectory/Get-ADFineGrainedPasswordPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

source: gharchive/pull-request

repo: MicrosoftDocs/windows-powershell-docs

license_type: permissive

license_source: github-api


text:
Clarify that DN syntax can be used to set permissions on AD domain root

PR Summary
Adds comments to all LAPS permission-setting cmdlets to clarify that DN syntax may be used to target the AD domain root.
PR Checklist

[X ] Descriptive Title: This PR's title is a synopsis of the changes it proposes.
[X ] Summary: This PR's summary describes the scope and intent of the change.
[X] Contributor's Guide: I have read the [contributors guide][contrib].
[X] Style: This PR adheres to the [style guide][style].

#sign-off

#sign-off

#sign-off

@sdwheeler - can you please help me get this PR completed?   Apparently #sign-off is not the right magic incantation.


text:
Can you clarify the contrained delegation section?

>When you install Windows Admin Center on Windows 10, it's ready to use single sign-on. If you're going to use Windows Admin Center on Windows Server, however, you need to set up some form of Kerberos delegation in your environment before you can use single sign-on. The delegation configures the gateway computer as trusted to delegate to the target node.
Does this mean I'd need to run this cmdlet for every host that I want to manage with Windows Admin Center? So if I have 500 hosts, I have to set this property on each one of their AD computer objects?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d6273f49-fe06-5a18-80e3-863bd3a0cf4e
Version Independent ID: 4ed5bf3d-0c2a-a80e-5bd9-0e858dd8749b
Content: Configuring user access control and permissions
Content Source: WindowsServerDocs/manage/windows-admin-center/configure/user-access-control.md
Product: windows-server-threshold
GitHub Login: @Haley-Rowland
Microsoft Alias: harowl

Yes, if you choose to use this form of delegation, you would need to run that for every host. You could use an array of computer names and a loop like this:
$gatewayObject = Get-ADComputer -Identity "<hostname of gateway here>"
foreach ($node in $nodeList) {
    $nodeObject = Get-ADComputer -Identity $node
    Set-ADComputer -Identity $nodeObject -PrincipalsAllowedToDelegateToAccount $gatewayObject
}

I include the instructions Resource-based constrained delegation because it's the easiest to set up with a few lines of PowerShell. There are other forms of Kerberos delegation that may be more suitable for scale.

source: gharchive/issue

authors: Geogboe jwwool

repo: MicrosoftDocs/windowsserverdocs


text:
OpenSSHUtils is deprecated

Trying to install OpenSSHUtils as per the "Host key generation" instructions gives the following error;
PackageManagement\Install-Package : The module 'OpenSSHUtils' cannot be installed or updated because the authenticode signature of the file 'OpenSSHUtils.psd1' is not valid.
The first result for that points at the Win32-OpenSSH repository and indicates that OpenSSHUtils is deprecated;
https://github.com/PowerShell/Win32-OpenSSH/issues/1313
It also links to the up-to-date method of correcting file permissions.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4c89b7b3-c05f-b517-6109-04e6a97195c3
Version Independent ID: 1e4b742e-d999-2c1e-a396-dc149f7ac76b
Content: OpenSSH Server Configuration for Windows
Content Source: WindowsServerDocs/administration/OpenSSH/OpenSSH_KeyManagement.md
GitHub Login: @maertendMSFT

Hi,
Is anyone helping maintain docs on these topics?

See Pull Request #4788 for a suggested improvement to this issue.
(The PR will close this issue ticket when it gets merged.)

List of related issue tickets:

#2747 A better explanation can be found here (Open)
#3400 Can't install the "OpenSSHUtils" (Closed)
#3456 Misleading title/summary causing search confusion (Open)
#3970 OpenSSH installation (Closed)
#4345 OpenSSHUtils Not Needed (Open)
#4518 Unable to configure OpenSSH for public key auth following docs (Open)
#4598 Instructions provided ends with an error (Open)
#4622 Out-of-date - OpenSSHUtils no longer available. (Open)
#4634 More documentation required (Open)
#4690 OpenSSHUtils install reference no longer valid (Open)
#4702 OpenSSHUtils got unlisted from the PowerShell gallery (Open)
#4743 Nope. First example errors out. (Open)
#4770 Error when following instructions to install OpenSSHUtils (Open)
#4787 OpenSSHUtils module does not exist (Open)
#5000 Clarification needed (Open)
#5138 These instructions do not work on Windows 10 20h2 (Open)

Thanks for submitting this issue. I have reworked this document to remove or replace parts that are no longer relevant or correct based on this and several other issues raised for this page.
The changes should be visible in around 6-12 hours.
#please-close

authors: FizzBuzz791 dknappettmsft illfated jeffwilcox


text:
Update to include W2k12R2 EOL

This is incorrect: "With the end of life of Windows Server 2003, 2008, and 2008 R2, these domain controllers (DCs) need to be updated to Windows Server 2012, 2012 R2, 2016, 2019, or 2022. "
Windows Server 2012, 2012 R2 are also EOL.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 418dc0a0-0312-9d6f-b2dc-2eb4841285ba
Version Independent ID: 600b0469-3c96-5737-c39b-2ce9021b0f5a
Content: Active Directory Domain Services Functional Levels in Windows Server
Content Source: WindowsServerDocs/identity/ad-ds/active-directory-functional-levels.md
Service: windows-server
Sub-service: ad-ds
GitHub Login: @dknappettmsft
Microsoft Alias: daveba

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


text:
Error in instructions?

I found this line in the style.css file in the default theme:
/* Logo image recommended dimension: 60x60 (square) or 350X35 (elongated), 4 kB average, 10 kB maximum. Transparent PNG strongly recommended. */

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 26b30a8b-731c-a11f-a666-83e25eef75ad
Version Independent ID: 2f45486d-f1d0-bf45-3790-fedc30f5a658
Content: Changing the company logo on the AD FS sign-in page
Content Source: WindowsServerDocs/identity/ad-fs/operations/Change-the-company-logo-on-the-AD-FS-sign-in-page.md
Product: windows-server-threshold
GitHub Login: @billmath
Microsoft Alias: billmath

@mdedmon : I know, this comment is pretty late compared to when you posted this ticket, but do you recommend taking the text you quoted from the CSS and enter that in the "important" note instead of the current text, which is as follows:

We recommend the dimensions for the logo to be 260x35 @ 96 dpi with a file size of no greater than 10 KB.

#please-close

#assign:IngridAtMicrosoft

authors: IngridAtMicrosoft illfated mdedmon


text:
Update pktmon.md

-removed the mention of release codenames
-added the best practices section
-edited the limitations section

@george-guirguis : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@george-guirguis : Would you be able to add my suggested change, to make that bullet point list work as intended?

@george-guirguis : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@george-guirguis : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@illfated: I'm sorry - only the author of this article, @khdownie, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Yes, I know. I just added the comment (as agreed) to get more attention to this PR.

#sign-off


text:
Bug in LockScreen.SetImageFileAsync(IStorageFile) Method when using Desktop Bridge

There is a bug in the desktop bridge that causes the SetImageFileAsync method not to work. It only seems to works on X64 architectures (where both the app and the system are X64).
See:
https://github.com/MicrosoftDocs/winrt-api/issues/2148
https://stackoverflow.com/questions/56935486/cached-image-not-being-updated-with-lockscreen-setimagefileasyncfile
This bug is still not fixed after YEARS! Unbelievable.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 68bece6b-32da-533b-6963-b9d92ebf34c2
Version Independent ID: 987d9f45-d64c-4d8d-2b84-8ea7bac608d6
Content: LockScreen.SetImageFileAsync(IStorageFile) Method (Windows.System.UserProfile) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.System.UserProfile/LockScreen.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @alvinashcraft
Microsoft Alias: aashcraft

Thanks for taking the time to let us know about this and we sincerely apologize for the delayed response. Have you reported this bug over at Microsoft Q&A? That's the best place to raise concerns about bugs like this in the APIs.
If you do create (or have already created) a thread over at Microsoft Q&A, we would appreciate if you could share that link here so we can track the progress and incorporate any technical details into our documentation. I'd like to call out the issue in the documentation if there is an official response provided about the problem. Though I'm marking this Issue as closed now, please treat this thread as an open thread for follow-ups. I'll be continuing to monitor it. Thanks!

repo: MicrosoftDocs/winrt-api


text:
Content very long, could use an abbreviated list

This is a very long list of properties and methods.  I think a simple filter switch, such as "common" / "complete" could make this and similar pages much more useful?  Or perhaps a checkbox to hide inherited, ubiquitous members?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 01539533-ca9f-5851-b5a8-05a95c3f4f8c
Version Independent ID: fa2040e4-5404-a85e-1a76-021b258ec38e
Content: DropDownButton Class (Microsoft.UI.Xaml.Controls) - WinUI
Content Source: winui-api-build/xml/Microsoft.UI.Xaml.Controls/DropDownButton.xml
Product: reunion
Technology: winui-reference
GitHub Login: @jwmsft
Microsoft Alias: jimwalk

Thanks for the feedback. We're always looking to improve the end-user experience with the API docs and the member lists on the Class topics is always in the discussion. At this time, our engineering process for building API topics require that all members (including inherited) be listed on those pages.
The primary TOC only shows direct members.

authors: Karl-Bridge-Microsoft mstasak

repo: MicrosoftDocs/winui-api


text:
Section on linking static libraries is not clear

"If your native library contains C++ code you must also pass the -cxx flag in your "Extra Arguments" so that Xamarin.iOS knows to use the correct compiler."
The above sentence is in the section about linking static libraries.  Why is it talking about the compiler when the static libraries are already compiled?
Also, what if the static libraries are a mixture of C++ and Objective C++ that is called from the C++ (NOT from the C#)?  What do you do about the -cxx flag in this case?

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dd6324b2-d690-3265-39e2-d5a57fcc1083
Version Independent ID: b7553f1b-1ed1-27fb-5e11-b91f609d32b1
Content: Referencing Native Libraries in Xamarin.iOS - Xamarin
Content Source: docs/ios/platform/native-interop.md
Product: xamarin
Technology: xamarin-ios
GitHub Login: @davidortinau
Microsoft Alias: daortin

Actually this whole section is hard to understand.  Why not mark Build Action as Embedded Resource, and set "Copy Always"?

Thanks for submitting an issue and we apologize for the delayed response. The requested updates haven't been made since the creation of the issue, and the timeline for resolution may vary based on resourcing, so the issue is being moved to an internal repo to better track it.

authors: S-List davidbritch

repo: MicrosoftDocs/xamarin-docs


text:
Setup guide leads to application crashing with you_should_not_call_base_in_this_method exception.

[Enter feedback here]
Hello,
I've experienced several crashes on my Xamarin Application, due to this code snippet
public override bool OpenUrl(UIApplication app, NSUrl url, NSDictionary options)
{
    if (Xamarin.Essentials.Platform.OpenUrl(app, url, options))
        return true;

    return base.OpenUrl(app, url, options);
}

Indeed, UIApplicationDelegate.OpenUrl(app, url, options) throws a you_should_not_call_base_in_this_method exception.
I'm on Xamarin Essentials 1.6 and SDK 13.4
I think the docs need to be updated to adress this issue
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1231a1e1-3734-9021-2cc7-eaf99478afca
Version Independent ID: 01e5fdbe-0b15-4dbe-f8a0-ed40f8593302
Content: Xamarin.Essentials: Web Authenticator - Xamarin
Content Source: docs/essentials/web-authenticator.md
Product: xamarin
Technology: xamarin-essentials
GitHub Login: @Redth
Microsoft Alias: jodick

Microsoft support for Xamarin will end on May 1, 2024 for all Xamarin SDKs including Xamarin.Forms. In preparation for this, all issues and PRs in this repository are being closed.
.NET MAUI is the replacement for Xamarin.Forms, and it's documentation can be found here.

authors: davidbritch ghasszak


text:
Update geocoder.md

Adding a note pointing to the Xamarin Essentials API for reference.

@Nerves82 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@davidbritch : Thanks for your contribution! The author(s) have been notified to review your proposed change.


text:
[Variable fonts] Animate the headings as they scroll into view

Here's the intended behavior:
Each major section of the guide has a class l-section--timeline. Each of these has an h2 heading, and a ::before pseudo element, currently rendered as a long, vertical line. By default, these lines should actually have height: 0, as we're going to animate them.
When the user scrolls and the h2 element is within the top-most third of the viewport, or the user has reached the end of the doc:

Transition the height of l-section--timeline::before to 14em.
At the end of this transition, transition one axis on the font of the heading. Final font is unknown, let's use Bahnschrift for now. We can animate the weight from a lighter weight to the boldest available. (This can be updated later).

Not sure of timings on the transitions, after the functionality is in, we can pair program to tweak the timings.

Closing because it's completed!

repo: MicrosoftEdge/Demos

license: MIT


text:
Clarify accessibility perspective of VK policy

While discussing about virtul keyboards from an accessibility perspective, @kevers-google raised the important point that this proposed policy should be clear the users who need VKs to be locked to screen "permanently".  Perhaps this is more like an OS-forced "show keyboard" option?  Or any corner cases I missed?

@mustaqahmed and @kevers-google Currently on Windows, I can't seem to find a way to lock the keyboard to the screen. We have asked our OS input team to confirm if there is a way to do that on Windows touch devices. Do you have any scenarios on other platforms where its possible to lock the VK to the screen? Could you please elaborate the use cases a bit more so we can get a good understanding of the accessibility implications here?

The accessibility settings on Chrome OS include an "enable on-screen keyboard" that works independently of having a touch screen device.  When active, a keyboard icon appears in toolbar next to the notifications indicator. Tapping on this button toggles show/hide of the VK. Focusing on a text-editable region will likewise show the VK.
This feature is used by uses with mobility impairments that impede typing on a physical keyboard.
On Windows 10, there is an on-screen keyboard app with similar functionality, which may be pinned to the taskbar. It does not auto-show/hide on focus change events, instead requiring manual toggle.

@kevers-google and @mustaqahmed  Thank you for all the details! We discussed this with the OS input team and currently they are making a change to not dismiss the VK on hide() call if the on-screen keyboard is "locked" to the screen or manually raised by the user using the taskbar button. Without this change though, hide() call will dismiss the VK, so my concern here is this - This is not something we can control in the browser platform unless the OS gives us some kind of notification that the user has decided to "lock" the VK to the screen. I couldn't find anything that would do that on Windows and I'm not sure if other platforms have this notification. But, this might be something that would be easier to handle in the OS layer where the show()/hide() calls can just be ignored by the OS if user "locked" the VK to the screen. Thoughts?

I agree with @snianu that the browser is subject to the policies enforced by the OS and there is no guarantee that hide or show will do anything.  That leaves the OS room to implement locking heuristics or explicit locking controls that browser will not override.  I'll close this issue for now.  Feel free to reopen if you think it needs further discussion.

authors: BoCupp-Microsoft kevers-google mustaqahmed snianu

repo: MicrosoftEdge/MSEdgeExplainers


text:
Lab 5.1 / task 2.3 / step 26 - unclear of lab intentions as i dont see the mention of "data"

Lab 5.1 power pages
Exercise 2
Task: 2.3
Step: 26
Description of issue
I am seeking clarification of this step please - as i dont see the mention of "data".
To be honest, i think Practice lab 5.1 needs a little update to clarify some steps as we go, as the wording the pages isn;t always clear. could someone please retest this start to finish?
Repro steps:

Under Set up there used to be a tab called Data
It was renamed to Actions  - see https://learn.microsoft.com/en-us/power-pages/getting-started/add-list
But the Actions tab has now disappeared - I have verified this today - this looks like a product issue not a lab steps issue

Please see updated labs merged today! Thanks.

authors: chaast chandlersyal julians1966


text:
Update 03-configure-data-model-in-power-bi-desktop.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by AnthonyOakley on behalf of MOC Labs Review