Skip to content

Dev Docs, Clickable Avatars, & Node Status Icon Parity

Pre-release
Pre-release

Choose a tag to compare

View all tags
@QuickMythril QuickMythril released this 17 Nov 03:36
· 11 commits to community since this release
features/docs-avatars-nodeicon
d73109a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Community Testing Pre-release: Chrome Extension

Dev Docs, Clickable Avatars, & Node Status Icon Parity

This is a Qortal-Community test build of the Qortal Chrome Extension based
on the current upstream code, plus three focused changes:

  • Clickable chat avatars & hover – user and group avatars in chat are now
    clickable to open profile/group info, with a clearer hover/interaction
    state so you can see they’re interactive (parallel to Qortal Hub).
  • Node status icon update – the node status indicator has been added/
    moved to a more visible location in the sidebar/header, improving parity
    with Hub.
  • Developer docs – initial DEVELOPMENT documentation explains how to
    build and load the extension in Chrome/Chromium for contributors.

⚠️ This is NOT an official Qortal release.
It is a community test build to gather feedback before proposing changes
upstream.

Downloads

After downloading:

  1. Unzip the archive.
  2. In Chrome/Chromium, go to chrome://extensions.
  3. Enable Developer mode.
  4. Click Load unpacked and select the unzipped folder.

What to test

Focus on chat avatars, hover behavior, node status icon, and
(optionally) the dev docs.

1. Clickable chat avatars & hover states

In Q-Chat within the Extension popup or full view:

  • Open a group or direct chat with active messages.
  • Hover your mouse over user avatars in the message list.
    • ✅ Expect: some hover affordance (cursor change, highlight, etc.) making
      it clear they are clickable.
  • Click on a user avatar.
    • ✅ Expect: a user info view/popup opens (matching Hub’s behavior as
      closely as possible).
  • Click on a group avatar where applicable.
    • ✅ Expect: group info view/popup opens.

Check for:

  • ❌ No weird double-click requirements or dead clicks.
  • ❌ No broken scroll or layout glitches when hovering/clicking avatars.

2. Node status icon

With the extension loaded and connected to your node:

  • Look for the node status icon in the sidebar/header area.
    • ✅ Expect: it’s clearly visible in a consistent place.
  • With your node connected and synced:
    • ✅ Expect: icon shows the "good/connected" state.
  • With your node stopped/offline:
    • ✅ Expect: icon switches to a warning/offline state.
  • If tapping/clicking the icon shows details:
    • Note what you see and whether it matches your expectations.

3. Developer docs (optional, for contributors)

If you’re testing dev flow:

  • Follow the dev docs (DEVELOPMENT.md or dev section of README.md) from a
    clean clone:
    • Install prereqs (Node/npm, etc.).
    • Build the extension.
    • Load it via "Load unpacked".
  • ✅ Expect: the steps are complete enough to get a working dev build without
    guessing.

How to report feedback

Please report results here, or in the corresponding Q-Community issue:

  • Extension parity issue: #4

When reporting:

  • Include:
    • Browser and version (Chrome, Brave, etc.).
    • OS (Windows / Linux / macOS + version).
    • Whether you used the pre-built ZIP or built from source.
    • Steps to reproduce and what you expected vs what happened.

If you mention findings in Qortal chats, please also copy a short summary
into the GitHub issue so we don’t lose track of it.

Thank you for helping test this Trifecta parity slice in the Chrome Extension!

Assets 3
Loading