A Closer Look At Dmtzagbov Fmsghh Plotly_chart Kwargs

When using st.plotly_chart with width='content', many users face a strange deprecation warning - even though they’re only passing standard params like width or height. This echoes past frustrations: a feature once straightforward now triggers a warning about unused kwargs. The real issue? Streamlit’s updated API quietly flags these inherited keyword args, but ignores clean, new config usage. Think of it like ordering coffee with extra syrups - yet the barista yells ‘no sugar!’ - pointless, yet persistent. Here is the deal: the warning persists even when kwargs is empty, just because width='content' is used. Current behavior shows the deprecation notice fires when kwargs is present - exactly when it shouldn’t. This isn’t a bug; it’s a legacy echo. Streamlit’s docs promise a cleaner path: use config instead. But until that shift fully rolls out, users get mixed signals. Hidden behind the warning: many still assume width overrides config, or kwargs are optional side notes. But they’re not - kwargs are now flagged redundant, even when harmless. Is this a regression? Not just a bug: it’s outdated feedback clinging to a still-functional system. Practical tip: avoid `width=