Skip to content

[MOO-1836]: fix feedback widget logo issues and make WCAG compliant#490

Open
SrirangK wants to merge 3 commits intomainfrom
moo/MOO-1836-native-feedback-widget-improvement-11.8
Open

[MOO-1836]: fix feedback widget logo issues and make WCAG compliant#490
SrirangK wants to merge 3 commits intomainfrom
moo/MOO-1836-native-feedback-widget-improvement-11.8

Conversation

@SrirangK
Copy link
Copy Markdown
Contributor

@SrirangK SrirangK commented Apr 10, 2026

Checklist

  • Contains unit tests ✅
  • Contains breaking changes ❌
  • Compatible with: MX 8, 9, 10
  • Did you update version and changelog? ✅
  • PR title properly formatted ([XX-000]: description)? ✅
  • Works in Android ✅
  • Works in iOS ✅
  • Works in Tablet ✅

This PR contains

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Other (describe)

Relevant changes

Feedback widget strings were hardcoded, they were updated to enable language translation.
Custom logo issue was fixed.

@SrirangK SrirangK requested a review from a team as a code owner April 10, 2026 08:19
titleSending?: DynamicValue<string>;
titleResult?: DynamicValue<string>;
labelFeedbackInput?: DynamicValue<string>;
placeholderFeedback?: DynamicValue<string>;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we discussed , these props are added to the component to support the language translation . I think we are making component heavy by introducing these props for only the language purpose . Can we avoid these ?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To add to this, I am a bit suspicious of handling localization in this manner, since no other Widget does it like this i.e. 'passing props for individual text fields'.

Maybe it is the responsibility of the User to manage different DataSources dynamically and Studio Pro should only expose the fields for override.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants