[Bug]: Widget custom background color is ignored on macOS (renders default background)

[pochemuto]

Platform

Mac

Versions

Version 26.6 (26601)

Reproduction steps

Reproduction steps:

Set a custom background color for the widget in the script (e.g. green background using background={...}).

Add or view the widget on macOS.

$render(
  <vstack frame="max" background={weight_color} alignment="leading">
    <hstack alignment="top">
      <text font="title" color={color.weight.value} bold="true">
        {data.last_weight.toFixed(1)} кг
      </text>
      <text font="caption" color={weight_diff_color}>
        {weight_diff}
      </text>
    </hstack>
    <hstack alignment="bottom">
      <text font="title3" color={color.workouts.value}>
        {formatWorkouts(data.current_week.workouts_value)}
      </text>
      {workouts_text}
    </hstack>
    <hstack alignment="bottom">
      <text font="title3" color={color.calories.value}>
        {data.current_week.calories}
      </text>
      <text font="caption" color={color.calories.value}>
        {plural(data.current_week.calories, "калория", "калории", "калорий")}
      </text>
    </hstack>
    <hstack alignment="center">{last_week_days}</hstack>
    <hstack alignment="center">{days}</hstack>
  </vstack>
);

Expected and actual behavior

Expected behavior:
The widget background renders with the custom background color (e.g. fully green), matching the iOS behavior.

Actual behavior:
The widget renders with the default system background, and the custom color cannot be applied or customized on macOS.

Diagnostics

No response

[everettjf]

Thank you very much for the detailed report and the clear reproduction example! We confirmed that this issue exists in version 26.6 on macOS. The script background was being applied only to the widget content, while WidgetKit continued to render its default container background.

This has been fixed in the current code by forwarding the background from the root JSX element to the WidgetKit container background on macOS. We also verified that the macOS app and widget extension build successfully with the fix. It will be included in the next update.

We really appreciate you taking the time to report this!