You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion hover and tooltips options {mode, axis, intersect} are tightly bound together.
There could be a use case where that is not true, but by default these could be configured using one set of options.
Current Behavior
hover and tooltips options are configured separately. Controllers usually set default for hover.mode, but not for tooltips.mode => weird effects.
Expected Behavior
hover and tooltips options extend from new interactions option.
Possible Solution
Add interactions option that both hover and tooltips extend from.
Move defaults (global and chart type specific) to the new option.
Extend on chart initialization to keep compatibility with external code?
2nd Possible Solution
Update controllers to set defaults for both tooltips and hover
Context
This would ease the configuration of new charts a bit. Also new developers would avoid weird interaction effects when familiarizing with this library for the first time.
Environment
Chart.js version: 2.7.3
The text was updated successfully, but these errors were encountered:
In my opinion
hover
andtooltips
options{mode, axis, intersect}
are tightly bound together.There could be a use case where that is not true, but by default these could be configured using one set of options.
Current Behavior
hover
andtooltips
options are configured separately. Controllers usually set default forhover.mode
, but not fortooltips.mode
=> weird effects.Expected Behavior
hover
andtooltips
options extend from newinteractions
option.Possible Solution
interactions
option that bothhover
andtooltips
extend from.2nd Possible Solution
tooltips
andhover
Context
This would ease the configuration of new charts a bit. Also new developers would avoid weird interaction effects when familiarizing with this library for the first time.
Environment
The text was updated successfully, but these errors were encountered: