Hoversubplots=axis not working with make_subplots

[Coding-with-Adam]

Initially reported on the Plotly forum.

Using make_subplots means that the hoversubplots=“axis” will not work correctly.

Sample code that produces the error:
Codepen.

import plotly.graph_objects as go
from plotly import data
from plotly.subplots import make_subplots

df = data.stocks()


fig = make_subplots(rows=3, cols=1, shared_xaxes=True, vertical_spacing=0.03)
layout = dict(
    hoversubplots="axis",
    title="Stock Price Changes",
    hovermode="x",
    grid=dict(rows=3, columns=1),
)

fig.add_trace(go.Scatter(x=df["date"], y=df["AAPL"], name="Apple"), row=1, col=1)
fig.add_trace(go.Scatter(x=df["date"], y=df["GOOG"], name="Google"), row=2, col=1)
fig.add_trace(go.Scatter(x=df["date"], y=df["AMZN"], name="Amazon"), row=3, col=1)
fig.update_layout(layout)
fig.show()

Expected behavior should be the same as when using the Plotly docs hover on subplots example, where hover labels appear for all charts:
Codepen.

[Episkiliski]

When will this be addressed?

[luweiming]

I have the same issues even with the latest Plotly 5.23.0

[n-splv]

+1
Many folks prefer not to work with the 'go' API because it's less intuitive. A fix for make_subplots would be appreciated 🙏

[verdverm]

+1
hitting the same issue, one cannot add multiple traces to a subplot and have the hoversubplots work at the same time

[matthiasschuurmans]

+1, though I found https://community.plotly.com/t/hover-question-how-to-info-in-all-trace/84893/2 as well, which seems to indicate it's not a bug because (if I understand correctly) make_subplots(shared_xaxes=True) doesn't actually create a single x-axis?

"REMEMBER that setting shared_xaxes=True does not assign the same name to xaxis in all subplots."

[shifenhutu]

I have the same issues even with the latest Plotly 5.24.1

[alsonpr]

Facing the same issue, hope this will get resolved soon

[joel23888]

I am facing the same issue.

[1SoSi1]

having the same issue here, hoping this will get resolved soon

[ShootingStarD]

Same issue

[paoloalba]

+1

[eetulauri]

Any timeline when this would be addressed?

[gvwilson]

Not at present unfortunately - our major release should be out soon, and then we will start looking at backlog again. If someone is able to put together a PR for us to review, that will certainly accelerate things. Thanks - @gvwilson