[BUG]: go.Funnel textinfo="percent initial+value" shows value before percent.

[yachika-yashu]

Description

go.Funnel with textinfo="percent initial+value" displays value before percent (e.g., "700 70.0%"), but should show percent first per docs (e.g., "70.0% 700").

Screenshots/Video

![Bug screenshot]

Steps to reproduce

Using Plotly 5.24.1

import plotly.graph_objects as go
import pandas as pd
platform_funnel = pd.DataFrame({
    'platform': ['Android']*3, 
    'stage': ['Awareness', 'Interest', 'Action'], 
    'users': 
})
fig = go.Figure()
subset = platform_funnel
fig.add_trace(go.Funnel(
    y=subset["stage"], 
    x=subset["users"], 
    textinfo="percent initial+value"
))
fig.show()

Actual: "1000 100.0%", "700 70.0%", "400 40.0%" (value first)
Expected: "100.0% 1000", "70.0% 700", "40.0% 400" (percent first,).

Notes

• Environment: Jupyter, Colab, VSCode
• Confirmed no duplicates via search "funnel textinfo order".
• Workaround: texttemplate="%{percentInitial:.1f}<br>%{value}", textinfo="text".
• Happy to investigate/fix if confirmed!

[Abineshabee]

I’ve investigated this and it appears the issue originates in plotly.js (likely in src/traces/bar/plot.js), where the funnel text rendering logic pushes value before percentage fields unconditionally, rather than respecting the order specified in the textinfo string.

From what I can see, the current implementation does not preserve token order when constructing the display text.

Proposed approach:

• Parse textinfo into tokens
• Render text strictly following the user-specified order

Before working on a fix, I wanted to confirm the intended behavior:
Should the display order strictly follow the order of tokens in textinfo, or is there a preferred canonical ordering?

I can work on a fix once the expected behavior is confirmed.

[emilykl]

@yachika-yashu Thanks for the report, and thanks @Abineshabee for looking into it. I agree this issue will need to be resolved in plotly.js, so I'll move the issue there.

@Abineshabee I'm not sure what the original intention was for textinfo, but it seems reasonable to me that the values should appear in the same order they are specified in the textinfo string. We would be happy to review a PR. Ideally the fix should include every trace type which has a textinfo property.

[Abineshabee]

I've opened a PR for this: #7752