Button Ignores Scale

[deckar01]

Describe the bug

The Button component is ignoring the scale argument. This was regressed somewhere in v6.

Side note: It is not clear why buttons break out of the form container. There is no way to make a form container and the variants for row/col do not have a border. It kind of made sense in v4, when the button expanded vertically, but that was regressed somewhere in v5.

Have you searched existing issues? 🔎

• I have searched and found no existing issues

Reproduction

import gradio as gr

with gr.Blocks() as demo:
    with gr.Row():
        gr.Textbox("foo", scale=1)
        gr.Textbox("bar", scale=0)
    
    with gr.Row():
        gr.Textbox("foo", scale=1)
        gr.Button("bar", scale=0)

demo.launch()

Screenshot

v6.5.1

v5.50.0

v4.44.1

Logs

System Info

Gradio Environment Information:
------------------------------
Operating System: Darwin
gradio version: 6.5.1
gradio_client version: 2.0.3

------------------------------------------------
gradio dependencies in your environment:

aiofiles: 24.1.0
anyio: 4.12.1
audioop-lts: 0.2.2
brotli: 1.1.0
fastapi: 0.119.0
ffmpy: 1.0.0
gradio-client: 2.0.3
groovy: 0.1.2
httpx: 0.28.1
huggingface-hub: 0.35.3
jinja2: 3.1.6
markupsafe: 3.0.3
numpy: 2.3.3
orjson: 3.11.4
packaging: 25.0
pandas: 2.3.3
pillow: 12.1.1
pydantic: 2.12.3
pydub: 0.25.1
python-multipart: 0.0.22
pytz: 2025.2
pyyaml: 6.0.3
safehttpx: 0.1.7
semantic-version: 2.10.0
starlette: 0.52.1
tomlkit: 0.12.0
typer: 0.20.0
typing-extensions: 4.15.0
uvicorn: 0.38.0
mcp is not installed.
pydantic: 2.12.3
authlib is not installed.
itsdangerous: 2.2.0


gradio_client dependencies in your environment:

fsspec: 2026.2.0
httpx: 0.28.1
huggingface-hub: 0.35.3
packaging: 25.0
typing-extensions: 4.15.0

Severity

I can work around it

[deckar01]

The scale prop is set correctly in window.gradio_config block sent from the backend, but button/Index is reading undefined for scale from gradio.props.scale. It looks like the value is actually in gradio.shared.scale (and should get it from there like Textarea). There are some other shared props duplicated in ButtonProps, but they are correctly being read from shared.

---

I found 15 prop interfaces that duplicate shared props by searching for

interface (?!Shared)\w+Props\s*\{(\n|[^}])*\b(elem_id|elem_classes|visible|interactive|server_fns|server|id|target|theme_mode|version|root|autoscroll|max_file_size|formatter|client|load_component|scale|min_width|theme|padding|loading_status|label|show_label|validation_error|show_progress|api_prefix|container|attached_events|components)\b

gradio/js/button/Index.svelte
  11,2: 	interface ButtonProps {

gradio/js/chatbot/types.ts
  116,8: export interface ChatbotProps {

gradio/js/dataset/types.ts
  3,8: export interface DatasetProps {

gradio/js/draggable/types.ts
  3,8: export interface DraggableProps {

gradio/js/fileexplorer/types.ts
  5,8: export interface FileExplorerProps {

gradio/js/gallery/types.ts
  16,8: export interface GalleryProps {

gradio/js/html/types.ts
  3,8: export interface HTMLProps {

gradio/js/imageeditor/types.ts
  28,8: export interface ImageEditorProps {

gradio/js/json/types.ts
  4,8: export interface JSONProps {

gradio/js/label/types.ts
  3,8: export interface LabelProps {

gradio/js/nativeplot/types.ts
  11,8: export interface NativePlotProps {

gradio/js/plot/types.ts
  6,8: export interface PlotProps {

gradio/js/tabitem/types.ts
  3,8: export interface TabItemProps {

gradio/js/tabs/types.ts
  4,8: export interface TabsProps {

gradio/js/textbox/types.ts
  21,8: export interface TextboxProps {

I found 11 shared props that are being read from the wrong place by searching for

gradio\.props\.(elem_id|elem_classes|visible|interactive|server_fns|server|id|target|theme_mode|version|root|autoscroll|max_file_size|formatter|client|load_component|scale|min_width|theme|padding|loading_status|label|show_label|validation_error|show_progress|api_prefix|container|attached_events|components)\b

gradio/js/button/Index.svelte
  37,9: 	scale={gradio.props.scale}

gradio/js/chatbot/Index.svelte
  128,16: 			autoscroll={gradio.props.autoscroll}

gradio/js/draggable/Index.svelte
  273,39: 	{#if gradio.shared.loading_status && gradio.props.show_progress}

gradio/js/html/Index.svelte
  39,11: 	padding={gradio.props.padding !== false}

gradio/js/json/Index.svelte
  67,15: 		theme_mode={gradio.props.theme_mode}

gradio/js/markdown/Index.svelte
  64,18: 		class:padding={gradio.props.padding}

gradio/js/plot/Index.svelte
  68,15: 		theme_mode={gradio.props.theme_mode}

gradio/js/tabitem/Index.svelte
  21,6: 	id={gradio.props.id}
  23,9: 	scale={gradio.props.scale}

gradio/js/textbox/Index.svelte
  35,3: 		gradio.props.validation_error = null;
  47,3: 		gradio.props.validation_error = null;

[deckar01]

@pngwn I tracked the regression down to 5ff20a7, where shared props was added. Are component arguments supposed to be getting loaded into the shared props? It seems like that was supposed to be for globals, but maybe this is an unintended side effect of letting components override shared props?

[Mr-Neutr0n]

Opened a fix in #12889 — covers the 7 clear-cut cases where shared props are read from gradio.props instead of gradio.shared:

• button/Index.svelte — scale
• html/Index.svelte — padding
• json/Index.svelte — theme_mode
• markdown/Index.svelte — padding
• plot/Index.svelte — theme_mode
• tabitem/Index.svelte — scale
• textbox/Index.svelte — validation_error

Left chatbot/autoscroll, tabitem/id, and draggable/show_progress alone since those are either special-cased in create_props_shared_props or intentionally component-specific props.

Thanks @deckar01 for the detailed analysis — made tracking this down straightforward.