From bbcd27d3c275aa64efa4ab67d8e056492fecec58 Mon Sep 17 00:00:00 2001 From: John Preston Date: Fri, 9 May 2025 10:00:18 +0400 Subject: [PATCH] Fix possible crash in restrictions. --- .../history/view/controls/history_view_compose_controls.cpp | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Telegram/SourceFiles/history/view/controls/history_view_compose_controls.cpp b/Telegram/SourceFiles/history/view/controls/history_view_compose_controls.cpp index 404691263a..50a49a7371 100644 --- a/Telegram/SourceFiles/history/view/controls/history_view_compose_controls.cpp +++ b/Telegram/SourceFiles/history/view/controls/history_view_compose_controls.cpp @@ -2325,11 +2325,17 @@ void SetupRestrictionView( ) | rpl::start_with_next([=](Controls::WriteRestriction value) { using Type = Controls::WriteRestriction::Type; if (value.type == Type::Frozen) { + state->icon = nullptr; + state->unlock = nullptr; + state->label = nullptr; state->button = FrozenWriteRestriction( widget, show, FrozenWriteRestrictionType::MessageField); } else if (const auto lifting = value.boostsToLift) { + state->icon = nullptr; + state->unlock = nullptr; + state->label = nullptr; state->button = BoostsToLiftWriteRestriction( widget, show,