New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OnIdiom doesn't respect Desktop setting on Windows #22093
Comments
We have verified that this problem, does not recur on 5 machines. We are not sure why it still reoccurs. Does it occur in a specific environment setting? In order for us to investigate this further, could you provide the Msbuild Log and binLog? |
Just tried this myself and same here, with your exact code, no changes, I see the text as red so I wonder what the difference is. Also tried a release build and same there. Can you run |
Please find attached build output and also the dotnet info. FYI I did a dotnet workload update but it's still the same. |
Very strange and I don't have a good explanation for it for now unfortunately. This one seems to might be related? #21799 So maybe when that gets merged, that might fix this too |
Ok, I've subscribed to that issue.. however it's a draft and no activity on it for 3 weeks. What's blocking that being merged do we know? |
Description
When using this for example:
TextColor="{OnIdiom Desktop='Red', Default='Black'}"
Running a solution on Windows the text is Black when I would expect it to be Red.
It works as expected when running on MacCatalyst, the text is Red.
It works as expected when running on iOS, the text is Black.
It works as expected when running on Android, the text is Black.
It does not work as expected when running on Windows, the text is Black.
Steps to Reproduce
Link to public reproduction project repository
https://bitbucket.org/KeithBoynton/on-idiom-desktop-issue/src/master/
Version with bug
8.0.21 SR4.1
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
No response
Did you find any workaround?
No
Relevant log output
No response
The text was updated successfully, but these errors were encountered: