You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create this report so that newcomers or veterans are aware of planned new content or unsolved bugs. Relating to planned content, this was discussed with the developer/contributor team both publicly and privately. Most of the planned content I can do myself, but as for the bugs, they've been flummoxing me for a while and I can't seem to figure out fixes or workarounds for them.
[MANUAL]: Port the Github wiki to work with the website - whether in the old Armory API repository or in the Armory website repository.
Build script(s) will also need to be created for this - similar to the Python script used for build wiki script (used for updating/porting monthly changes to the wiki).
[TUTORIALS/RESOURCES] Implement better tutorials and resources page(s).
[MARKETPLACE]:Implement a new, free and community-based marketplace; perhaps. Will need confirmation with @ Lubos. There's also the practical question of would a static store even be good enough? Github Pages only support static hosting, not server-side hosting, which disallows possible store accounts, which also disallows direct user uploading w/ verified account.
⁉️Known Issues
[NOTES]: URL anchors do not work in Edge (possibly Chromium related issue?) - possibly due to the dynamic content selection process (i.e. anchors don't exist until content set and shown).
Possible workarounds: I've already tried using setTimeout() and also manual setting of saved mouse coordinates, but no luck - quite possibly because I'm doing something wrong, of course. This by no means that those two processes are invalid, they could be possibly valid - I just don't know how to make them work properly, if so.
[NOTES]:Viewport selection isn't remembered on page refresh.
Possible workaround:I've observed when removing or commenting all code from footer.html, the issue is fixed, but unfortunately, I can't figure out what is causing the issue from that webpage's code snippets.
[GLOBAL]: MP4s don't always play on load (until page refresh) - this is due to some browsers having an autoplay setting disabled. I'm not sure if this is a "global" MP4 thing, as I've only noticed this issue at the release notes (I could be well mistaken).
Possible workaround: Dynamically stream video via JavaScript to ensure active playing.
[FOOTER]: Back to top button doesn't work in Edge (and possibility Chrome) if preferred reduced motion is enabled in OS settings. (Independent of browser settings).
Possible workaround: N/A. There's not really anything we can do, as it's on the OS side, not browser.
The text was updated successfully, but these errors were encountered:
📣
TL;TR
I create this report so that newcomers or veterans are aware of planned new content or unsolved bugs. Relating to planned content, this was discussed with the developer/contributor team both publicly and privately. Most of the planned content I can do myself, but as for the bugs, they've been flummoxing me for a while and I can't seem to figure out fixes or workarounds for them.
🚀
Planned New Content
Implement a new, free and community-based marketplace; perhaps. Will need confirmation with @ Lubos. There's also the practical question of would a static store even be good enough? Github Pages only support static hosting, not server-side hosting, which disallows possible store accounts, which also disallows direct user uploading w/ verified account.Known Issues
setTimeout()
and also manual setting of saved mouse coordinates, but no luck - quite possibly because I'm doing something wrong, of course. This by no means that those two processes are invalid, they could be possibly valid - I just don't know how to make them work properly, if so.Viewport selection isn't remembered on page refresh.I've observed when removing or commenting all code from footer.html, the issue is fixed, but unfortunately, I can't figure out what is causing the issue from that webpage's code snippets.autoplay
setting disabled. I'm not sure if this is a "global" MP4 thing, as I've only noticed this issue at the release notes (I could be well mistaken).The text was updated successfully, but these errors were encountered: