docs: Update platform naming conventions in feature support tables to align with Uno 6.0

[Copilot]

GitHub Issue: closes #21018

PR Type:

📚 Documentation content changes

What is the current behavior? 🤔

Feature support tables use outdated platform naming conventions that predate Uno 6.0's renderer separation and single-project structure:

• Linux (Skia) ambiguously refers to X11-based desktop Linux
• Win 7 (Skia) / WPF (Skia) creates confusion between Windows desktop, Uno Islands, and legacy Windows 7
• macOS lacks consistent "Desktop" prefix used by other platforms
• Column names don't match GitHub issue template platform options, causing friction when filing issues

Users targeting net9.0-desktop or net10.0-desktop on Windows cannot determine if features are supported from tables showing "WPF (Skia)" or "Win 7 (Skia)".

What is the new behavior? 🚀

Platform naming conventions now align with GitHub issue templates and Uno 6.0 architecture:

Updated column headers:

# Before
| Feature | WinUI | Android | iOS | Web (WASM) | macOS | Linux (Skia) | WPF (Skia) |

# After  
| Feature | Windows | Android | iOS | Web (WASM) | Desktop (macOS) | Desktop (X11) | Desktop (Windows) |

Mapping:

• Linux (Skia) → Desktop (X11) - Explicitly targets X11-based systems
• Win 7 (Skia) / WPF (Skia) → Desktop (Windows) - Clarifies Windows desktop with Skia renderer
• macOS → Desktop (macOS) - Consistent desktop platform prefix
• WinUI → Windows - Simplified for native Windows

Files updated:

• 2 feature documentation templates
• 15 feature documentation files (accelerometer, barometer, clipboard, compass, file-management, flashlight, gamepad, gyrometer, magnetometer, orientation-sensor, PasswordVault, settings, step-counter, windows-applicationmodel-calls, windows-networking)

PR Checklist ✅

Please check if your PR fulfills the following requirements:

• 📝 Commits must be following the Conventional Commits specification.
• 🧪 Added Runtime tests, UI tests, or a manual test sample for the changes have been added (for bug fixes / features) (if applicable)
• 📚 Docs have been added/updated which fit documentation template (for bug fixes / features)
• 🖼️ Validated PR Screenshots Compare Test Run results.
• ❗ Contains NO breaking changes

Other information ℹ️

Documentation builds successfully with updated naming conventions. This change improves developer experience by making platform support immediately clear and consistent with the rest of the Uno Platform ecosystem.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• github-production-user-asset-6210df.s3.amazonaws.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Docs][SupportedFeatures-Tables][Enhancement-Request] Please update the Platform specific feature/api support tables with v6.0 target and renderer naming conventions</issue_title>
<issue_description>### What would you like clarification on? 🤔

I was reading the Image Control Page, that links to the StorageFile.ReadStorageFileFromApplicationUrlAsync Docs and with the not longer Multi Head Uno App Solution/Project Strucutre, it's difficult for me to really understand this table on the top region of this page that should tell me as reader about the supported state for our target platforms in Uno.

*(Reference Screenshot of this table)*

The Difficultness in this, to help you understand my point, is the naming of the column headers that should tell me the platform.
Since you added, up from the uno.sdk v6.0, the Differencing between the Renderers SkiaRenderer and Native, the naming convention of Skia as equivalent for Desktop is in my opinion (not longer) a real equivalent we should automatic imply.

I for example do target net9.0-desktop and develop on Windows 11 pro which would then be Desktop (Windows) in my understanding. Assuming you would mean in this table for example Skia == Desktop and the user does maybe make use of SkiaRenderer while targeting Android, which we now can, thanks to Uno's 6.0 release, we have a duplication of targets. And for me searching for the answer for Is this feature supported on Desktop targeting to run on Windows? well, I still don't know the answer!

Maybe you mean:

Skia (Wpf) == Desktop (Windows) -> Yes, we have support for this on your target!

But could also mean:

Skia (Wpf) == Uno Islands embedded in Wpf app, which I tryed and hopelessly failed (following the Uno Islands docs tutorial and sample app) with the error of the Wpf Designer & Compiler in the end was telling me, that WinUI controls are not supported to be embeeded in Wpf apps.

I have at the moment no full list of the Desktop target supported full list, but Skia (Wpf) is defintly nothing that would make me imply Windows, so would be really nice if you could consider to update those in the future!

Concern 📚

Clarification of capabilities 💡

Renderer 🎨

• Skia
• Native

Affected platforms 📱💻🖥️

Desktop (Windows), Desktop (macOS), Desktop (X11), Desktop (Linux Framebuffer), Build tasks

Any feedback? 💬

[!TIP]
Maybe you could change the column header namings to the ones we have here for the docs/Enhancement-Request issue GitHub template, that would fit this need much better 👍

[!NOTE]
While the GitHub unoplatform repo(s) issue template I am currently using is showing this maybe to be targeted Naming, this does not apply, until now, to all other active Uno Repository's

This caused for me already multiple times the same problem and difficultness as mentioned for the tables in the docs when opening a Bug Report or other Report with those in the unoplatform repositories.
So, if you would consider to update those too, it would help me a lot, to provide you better and more useable Feedback/Reports in the future 👍 💯
Requested the issue template part here (maybe wording improvable/could be more clear there, but same goal) in:

• Issue Template Platforms list is outdated for >v6 sdk #21017</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Docs][SupportedFeatures-Tables][Enhancement-Request] Please update the Platform specific feature/api support tables with v6.0 target and renderer naming conventions #21735

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-22332/docs/index.html