Skip to content
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

Armory website roadmap + known bugs #34

Open
rpaladin opened this issue Dec 8, 2022 · 0 comments
Open

Armory website roadmap + known bugs #34

rpaladin opened this issue Dec 8, 2022 · 0 comments

Comments

@rpaladin
Copy link
Collaborator

rpaladin commented Dec 8, 2022

📣 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

⁉️ 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant