When default platform is not detected correctly, platform-specific sections are not shown.

[sirocyl]

What is the current behavior?

When visiting a docs page with multiple platform selections separated by tabs, is not detected as either of the platforms given (MacOS, Windows, Linux) and parts of documentation are missing as a result.
Issue spotted from ChromeOS Chrome browser, latest release, Pixelbook.

This may be replicated by using any user-agent in your browser which does not match the existing detection regexes in user_agent.js or the platforms listed in display-platform-specific-content.js.

What changes are you suggesting?

1. For "weird" platforms like ChromeOS, Haiku, BSDs/UNIXes, and so on - a sane default to fall back on, would be Linux, in almost every case.
2. For documents with multiple platforms, the document should make sense with no platform selected. (An example can be seen in the page on adding a new SSH key to your account.)
3. Finally, ChromeOS should be detected, and aliased over to the "linux" platform. This is being solved in Add ChromeOS support in defaultPlatform frontmatter #4102.

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[janiceilene]

Thanks for opening an issue @sirocyl! I'll triage this for the team to take a look 👀

[heiskr]

I've opened #4735 to resolve (1), (3) we resolved in #4102. I suspect we'll need some github/docs-content help for (2).

[janiceilene]

For documents with multiple platforms, the document should make sense with no platform selected. (An example can be seen in the page on adding a new SSH key to your account.)

@sirocyl Can you clarify what you'd like to see change in the SSH key article? I'm not sure I'm understanding. Thank you!

[heiskr]

I believe we've covered the main concerns raised. It may be difficult to support some articles without having examples available to a specific OS, and a non-trivial amount of work for our writers to support. I'm closing this issue, feel free to open new issues :)

[sirocyl]

For documents with multiple platforms, the document should make sense with no platform selected. (An example can be seen in the page on adding a new SSH key to your account.)

@sirocyl Can you clarify what you'd like to see change in the SSH key article? I'm not sure I'm understanding. Thank you!

Sorry, I was away from the computer for a while. If you're on a platform which isn't detected, the article ends abruptly, with no guidance shown on adding SSH keys. Example is attached in screenshot below.

The ideal behavior, would be to fall back on displaying a common set of steps (get your SSH public key; go to github user settings, etc; paste it in) rather than to show nothing at all.

I believe we've covered the main concerns raised. It may be difficult to support some articles without having examples available to a specific OS, and a non-trivial amount of work for our writers to support. I'm closing this issue, feel free to open new issues :)

I agree; if I encounter anything like this, I'll post another issue! It probably affects an extremely small segment of fairly technical users on hobbyist or non-mainstream OS - or, people using GitHub/reading docs on oddball platforms like smart TVs, e-paper readers or game consoles, given that it would only show on particularly uncommon systems.
Combing the whole docs tree for platform-specific information is probably a little more complicated than a simple grep :)

[janiceilene]

Thanks so much for that clarification and screenshot! Please do let us know if you see this again 💖