-
Notifications
You must be signed in to change notification settings - Fork 0
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
to @riverar #7
Comments
They render here on Android hmm. They're standard Unicode characters as far as I know. What browser are you using? |
Strangely here in the office with Chromium v89.0.4389.90 they now show just fine, but they didn't when I last checked in Friday (I think it was then), on Android 8 with Chrome v62.0.3202.84 (stock, not updated on purpose, the oldest I have in the moment) they don't still show up in mobile view, but they do with Desktop user agent ("Request desktop site" enabled), which is strange and it looks like the software (including OS) is with own opinion... |
@riverar Do you think that WSA can be made to also work on W10 ?, because I edited its manifest (.xml) to lower the minimum required build to the latest I have on W10 and replaced only that file with WinRAR (other archive managers refused to manipulate it), but since the archive structure wasn't kept, but set as a simple zip, it probably needs to be properly repacked & resigned or whatever and IDK if there are any specific unknown dependencies, but I think someone experienced can probably manage to make it happen.... |
Won't work, underlying OS changes were made to support WSA. |
@riverar
https://github.com/riverar/wsa-app-compatibility
On windows 7 Chrome/Chromium all I see for what should be the\a status ("legend") colors are empty square symbols for unknown or unsupported characters, IDK what you are using - ASCII, Emoji or whatever, but they are not visible on other OSes (Android), devices and browsers, so please try to use something universal if possible (I don't see why wouldn't it be...). Thanks in advance ;)
The text was updated successfully, but these errors were encountered: