Skip to content

Conversation

@TheMasterOfMike
Copy link
Contributor

I noticed while checking the base MSET9 page that platforms like iOS aren't listed, but that the warning about "not having access to any of these devices" only appears after you select the platform on the base MSET9 page, which doesn't necessarily seem ideal (since what platform would you select if you're using iOS on the base MSET9 page? (which doesn't currently have this warning)).

This PR attempts to fix this by simply adding a variant of the same wording to the base MSET9 page.

(Note: It might be better to just say "If your platform isn't listed here" at the start, but as that could potentially be more confusing depending on how somebody looks at that, I'll defer to the other people looking at this PR as to whether or not that wording would make more sense.)

Might be better to just say "If your platform isn't listed here" at the start, but that could potentially be more confusing depending on how you look at that so I'll defer to the other people looking at this PR.
@ManiacOfGitHub
Copy link
Contributor

In my opinion, it should be a footnote rather than a header because after the iOS PR gets merged, there will be basically no modern desktop/mobile OS that isn't supported by MSET9.

@TheMasterOfMike
Copy link
Contributor Author

In my opinion, it should be a footnote rather than a header because after the iOS PR gets merged, there will be basically no modern desktop/mobile OS that isn't supported by MSET9.

Late reply, but imo this PR/change is largely irrelevant if/when the iOS PR gets merged (what relevant platforms don’t fall under the platforms listed at that point?).

That being said, until that PR gets merged, it makes more sense as a header in large part to make sure that the average reader doesn’t miss that section (and also to better align with the other current MSET9 pages)

@lilyuwuu
Copy link
Member

Redundant now that #2554 is merged. Thanks for the motivation to finally do so :p

@lilyuwuu lilyuwuu closed this Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants