Skip to content

Social UI polish leftovers from #173: Sharing depth, own bubble colour, tab order / focus ring / duplicate Manage #406

Closed

Description

@Birfy

Leftovers from #173 (Social UI polish round 3) that were not tracked in any other issue. Last status on main ab723ac (2026-10-18); not re-checked since, so verify before fixing.

  • Sharing is deep in Bot settings. Edit Bot > Sharing sits at the bottom of a long page (about 3 clicks plus a scroll), with no section header like Profile and Model have.
  • Own bubbles are light grey, received bubbles are dark. Make the contrast and styling consistent.
  • Not re-checked: tab order (approval buttons come before the sidebar; one extra Tab stop focuses nothing), the faint composer focus ring, and whether two different controls are still both labelled Manage.

Related: #173 (closed), #384, #343, #182.

Activity

  1. added
    enhancementNew feature or request
    area:socialFriends, invites, grants, Bot Social
    area:uiWeb/desktop UI and copy
    needs-infoWaiting for the reporter or a maintainer decision
    on Oct 19, 2026
  2. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Triage on main 7b9e90b, 2026-10-19 ~12:10 Asia/Shanghai: needs-info. Not re-checked since ab723ac. Blocking: (1) bubble colours: which way should own vs received bubbles go (own darker/accent, received light, or both neutral)? (2) Sharing: only add a section header, or also move Sharing up in Edit Bot? (3) tab order / focus ring / duplicate Manage need a re-check on current main. A self-test or a short owner note can settle these.

  3. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Triage on main 0852b3f, 2026-10-19 16:59 Asia/Shanghai. Checked against the code; I decided the minor points:

    Owner-delegated decisions

    • Bubble colours: no change. Own bubbles use --bt-user (near-black with light text in light theme, near-white in dark theme). Received bubbles use the neutral --bt-bubble (light grey / dark grey). This is one rule in both themes: own = ink colour, received = neutral. The "own light grey, received dark" note was the dark theme.
    • Sharing: the plugin details slot (FlyBotDetails in bot-settings.js) is drawn as a titled Sharing card, using the same Card as Profile and Model. It moves up to sit right after Instructions (before Capabilities / Connectors / Memory). Social's BotSocialDetails drops its own fs-label "Sharing", so the title does not show twice.
    • Duplicate Manage: the two Memory rows (Manage → memory, in Bot settings and in details) are the same action and stay. Group settings' danger card is titled Manage, but Bot settings calls the same card More. Rename the group card to More for consistency.
    • Composer focus ring: make [data-composer-card]:focus-within clearly visible (e.g. the border at about 55% ink instead of 30%). Hover stays as it is.
    • Tab order: the implementer checks it in a browser with the keyboard. Tab from the page start should go sidebar → main → composer, with no stop that focuses nothing. Fix what differs and say what was found.

    Expected / scope: core/src/client/bot-settings.js, core/src/client/group-settings.js, core/src/client/styles.js, plugins/social/client.js (BotSocialDetails), plus zh strings in i18n.js and generated core/client.js / patches. Tests: a source test for the card order, card title and focus style.

    Waiting on the owner: confirm this scope so the issue can be marked agent-ready. Label changed from needs-info to needs-human.

  4. added
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    and removed
    needs-infoWaiting for the reporter or a maintainer decision
    on Oct 19, 2026
  5. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Owner decision (2026-10-19 17:21 Asia/Shanghai): approved the proposed scope. Bubble colours unchanged; Sharing becomes a titled card right after Instructions; group-settings "Manage" card renamed "More" to match Bot settings; stronger composer focus ring; keyboard tab order checked in a browser and fixed where it differs. Ready to develop.

  6. added
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    and removed
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    on Oct 19, 2026
  7. self-assigned this
    on Oct 19, 2026
  8. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Claimed by Birfy at 2026-10-19 17:22 Asia/Shanghai. Branch: Birfy:issue-406-ui-polish off upstream main d65e09d. Scope per the Owner decision: Sharing card after Instructions, group "Manage" card → "More", stronger composer focus ring, tab order check/fix. Bubble colours unchanged.

  9. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    PR #436 (2026-10-19 17:33 Asia/Shanghai). Minor details I decided:

    • The Sharing card holds social's two parts (Invite, People with access) as one card split by a line, like the other settings cards (no card inside a card). The friend's-Bot sheet and details drawer are unchanged (the frame is only in an own Bot's settings).
    • zh title: 分享.
    • Composer: focus border 55% ink, hover stays 30%.
    • Tab order, checked in headless Chrome on a mock bench: sidebar (Search, New…, Bots, Connect apps, Account) → chat header pill → message box → Add / Dictate / voice → turn stats, then the page wraps. The approval overlay layer (shell.overlay) is after the main column in the DOM, so approval buttons no longer come before the sidebar; no stop focuses an invisible element. No change needed. The message box comes before + because DSH's DOM has the input first (FlyBot CSS only moves + to the left visually); kept, since typing is the main action and changing it means changing DSH's DOM.
  10. added a commit that references this issue on Oct 19, 2026
    0e69063
  11. removed
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:socialFriends, invites, grants, Bot Socialarea:uiWeb/desktop UI and copyenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions