Skip to content

[3.0] Name the icons in the message icon picker - #9479

Merged
live627 merged 1 commit into
SimpleMachines:release-3.0from
albertlast:3.0/message-icon-alt
Aug 10, 2026
Merged

[3.0] Name the icons in the message icon picker#9479
live627 merged 1 commit into
SimpleMachines:release-3.0from
albertlast:3.0/message-icon-alt

Conversation

@albertlast

Copy link
Copy Markdown
Collaborator

Description

Clicking a post's message icon opens the icon picker, and every icon in it has alt="null".

IconList.onIconsReceived() reads icon.getAttribute('name'), but the XML that ?action=xmlhttp;sa=messageicons produces has no name attribute - the name is the element's text:

<icon value="lamp" url="…/post/lamp.png"><![CDATA[Lamp]]></icon>

getAttribute() returns null, and assigning that to .alt stringifies it. Measured on a topic: 13 icons, 13 alts reading null, while title - which reads the text - is correct throughout. Inherited from 2.1, where script.js builds the same markup the same way.

How to test

Open a topic as someone who can modify a post, click the icon next to the subject, and inspect the picker. Before: alt="null" on all of them. After: alt="Standard", "Thumb Up", "Lamp", … matching the titles.

Issues References (Fixes|Related|Closes)

Found while sweeping the topic display for the #7933 split.

The XML for these has value and url attributes and carries the icon's name
as its text, so getAttribute('name') is null and every one of the 13 icons
in the picker announced itself as "null". Read the same text the title
already uses.

Signed-off-by: Mathias Papenbrock <mathiaspapealbert@hotmail.com>
Signed-off-by: albertlast <mathiaspapealbert@hotmail.com>
@albertlast albertlast mentioned this pull request Aug 9, 2026
@live627
live627 merged commit f0e598e into SimpleMachines:release-3.0 Aug 10, 2026
4 checks passed
@jdarwood007 jdarwood007 added this to the 3.0 Alpha 5 milestone Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants