1027279: Fixed legend toggle series dimming issue in charts.

[Yokesh-SF4393]

Bug description

Fixed testing portal tickets on charts including sample navigation issue, mobile mode detection.

• 83251 - Legend not visible in mobile mode.
• 83088 - When navigation series points with keyboard, incorrect tooltip values are shown.
• 83069 - The tooltip template is not properly positioned and partially clipped.
• 83061 - The tooltip appears for series when focus on trendlines incorrectly.
• 83034 - The Data labels in some points are not visible.
• 83009 - The Samples are not navigated properly.
• 82983 - The Keyboard navigation on empty points resulting in console error.
• 82969 - Incorrect series are dimmed after toggled.

Root cause

Fixed and implemented testing portal issue and sample navigation issue, mobile mode detection.

• 83251 - Mobile mode detection logic is not available.
• 83088 - The method getData() gives incorrect data for tooltip, is same point values available in different series.
• 83069 - When multiple charts are rendered, the tooltip template is not associated with the correct chart ID. As a result, it accesses the first chart on the page, causing the tooltip to be positioned incorrectly.
• 83061 - In keyboard navigation, the tooltip appears incorrectly on series with same x point on focusing the trendlines.
• 83034 - The Data labels are actually rendered, but the background color is not updated properly and resulting in rendering same color text as background.
• 83009 - The Chart samples div size was not given proper, after selecting the sample, the chart starts to render and aligned improper.
• 82983 - The arrow right and arrow down for navigation to series are not handled proper.
• 82969 - After the legend toggle without mouse move, the series highlight is not removed properly.

Solution description

Fixed testing portal tickets on charts including sample navigation issue, mobile mode detection.

Code Studio usage(Mandatory)

• Code Studio used in this PR/MR?

  • Yes
  • No

• If Yes: Primary use (choose one)

  • Generate new code
  • Refactor/improve existing code
  • Tests
  • Bug fix / debugging help
  • Docs / comments
  • Review assistance (explanations/summaries)
  • Other:

• Outcome

  • Saved time
  • Neutral
  • Cost time

• If “Cost time” explain in short (1 or 2 lines):

Impact assessment

• Low - Affects a single feature with minimal user impact
• Medium - Affects multiple features or has moderate user impact
• High - Critical functionality or significant user impact

Reason for not identifying earlier

This is recently added code, now identified and fixed the issue.

Areas tested against this fix

• Tested using standard test cases
• Tested against feature matrix. Centralized location
• NA

Breaking changes

• Yes (Tag breaking-issue)
• No

If yes, provide breaking commit details link and migration guidance.

Regression testing

• Verified fix doesn't reintroduce previous bugs
• Checked edge cases and error scenarios

Action taken to prevent recurrence

• Added/updated unit tests
• Other (specify): _________________
• NA

Automation status

• BUnit (provide PR link: _________________)
• Playwight (provide PR link: _________________)
• NA

Cross-platform verification

• Blazor Server
• Blazor WASM
• NA

Related issues

Is this issue present in EJ2 or other components?

• Resolved in EJ2 (PR link: _________________)
• Created task for EJ2 (Task link: _________________)
• Needs attention in other components (tag needs-attention-coreteam)
• NA

Output screenshots

Before:

After:

API changes

• New API added (API Review task link: _________________)
• Existing API renamed/modified (API Review task link: _________________)
• No API changes

Performance verification

• Verified no memory leaks introduced
• Verified no performance degradation
• Not applicable

Reviewer Checklist

• Reviewed the provided Code Studio usages related information.
• Code changes follow component guidelines
• All provided information reviewed and verified
• Solution addresses the root cause effectively