Fix/fix tooltip theme not work

[xuefei1313]

[中文版模板 / Chinese template]

🤔 This is a ...

• New feature
• Bug fix
• TypeScript definition update
• Bundle size optimization
• Performance optimization
• Enhancement feature
• Refactoring
• Update dependency
• Code style optimization
• Test Case
• Branch merge
• Release
• Site / documentation update
• Demo update
• Workflow
• Other (about what?)

🔗 Related issue link

close #4550 #4562

🔗 Related PR link

🐞 Bugserver case id

💡 Background and solution

📝 Changelog

Language	Changelog
🇺🇸 English
🇨🇳 Chinese

☑️ Self-Check before Merge

⚠️ Please check all items below before requesting a reviewing. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• TypeScript definition is updated/provided or not needed
• Changelog is provided or not needed

---

🚀 Summary

copilot:summary

🔍 Walkthrough

copilot:walkthrough

[xuefei1313]

Summary

This PR fixes a couple of related theme/interaction edge cases:

1. Interaction trigger merging in common charts: triggers were previously merged only by regionId + trigger.type, which could accidentally merge different trigger configurations (e.g. element-active with click vs pointerover). This can lead to unexpected active-state / interaction behavior (and indirectly affect tooltip-related interactions).
2. Radar area theme default: radar series area.visible was hardcoded to false as a default, which could override theme defaults when the chart spec only provides area.style.

Overall the direction looks correct and the added tests are helpful.

Notes on the implementation

• BaseChart._initInteractions: grouping triggers by isEqual(trigger) (per region) makes sense and should prevent cross-series config pollution. Keeping a separate config snapshot is also a nice touch to avoid later marks mutation affecting comparisons.
• ElementActive: the statedGraphics?.includes(g) change prevents a potential runtime crash when getStatedGraphics() returns undefined.

Suggestions

• In _initInteractions, consider comparing only semantic trigger fields (e.g. type, trigger, state, etc.) instead of the whole object, in case the trigger object ever contains ephemeral properties. A stable key (or a pick(...) + isEqual) would reduce the risk of missing merges unintentionally.
• The .vscode/launch.json changes look unrelated to the bug fix; I’d recommend dropping them or moving them into a separate PR to keep the change focused.
• The new test getActiveTriggerCount reaches into private _interaction internals. It’s OK for a regression test, but if there’s a small public/testing helper we can use instead, it would make the test less brittle across refactors.

Verification

• The new unit tests cover both the trigger isolation case and the radar theme behavior well. If the original reported issue was specifically about tooltip theme, it might be worth adding a minimal regression around tooltip styling/config too (so we don’t rely on indirect coverage).