Skip to content

[codex] Support localized trigger buttons - #1541

Draft
devashishmamgain wants to merge 1 commit into
masterfrom
codex/tdh-3904-localized-trigger-buttons
Draft

[codex] Support localized trigger buttons#1541
devashishmamgain wants to merge 1 commit into
masterfrom
codex/tdh-3904-localized-trigger-buttons

Conversation

@devashishmamgain

Copy link
Copy Markdown
Collaborator

Jira

Summary

  • Extend startup trigger buttons (kommunicateSettings.quickReplies) to support rich quick-reply-style objects in addition to the existing string array.
  • Render localized button text from title/name, send the configured message, preserve optional replyMetadata, and apply updateLanguage/languageCode when the visitor clicks the trigger button.
  • Keep existing string trigger buttons on the same text-box submit path for backward compatibility.

Root Cause

Trigger buttons are configured through the same quickReplies setting documented for the web widget, but the startup renderer treated every item as a plain string and sent innerText through the text box. That meant trigger buttons could not use the localized display text, reply metadata, or language update fields already supported by rich-message quick replies.

Validation

  • git diff --check
  • Not run: node --check webplugin/js/app/kommunicate-ui.js because Node is not installed in this environment (zsh: command not found: node).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant