mirror of
https://github.com/status-im/status-app.git
synced 2026-08-27 15:11:20 +00:00
754276d8533f879c03cdeee7964b8de276cae69f
7
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 Alex Jbanca
|
68eb973c84 |
perf(chat): lazy, async member loading for user list and mention suggstions (#21920)
* perf(chat): lazy, async member loading for user list and mention suggestions The members panel builds on first show only (latched), asynchronously behind MembersListSkeleton — it must never delay a chat switch. Once built, UserListPanel binds its users model only while the right panel is actually visible, and it adopts the shared MembersPanelHeader introduced with the skeletons. The mention suggestions adaptor stays detached from the members model until the first mention entry (short wire delay, loading skeleton in the suggestion box meanwhile; the latch drops on usersModel swap so chat switches never pay for sorting the members model). Together these were ~1.5s of the chat-switch freeze on large communities. * fixup! perf(chat): lazy, async member loading for user list and mention suggestions The members panel is shared across the section's chats, so once built it stayed visible through a chat switch: it showed the previous chat's members while sorting the incoming model on the switch frame. A latch drops it back behind MembersListSkeleton on every active-chat change and re-arms on a short delay, the same shape as the mention suggestions wiring. rightPanelReady now follows the loader it was named after. * fixup! perf(chat): lazy, async member loading for user list and mention suggestions Keying the latch on the active chat id dropped it on every switch, but a community channel without permissions hands the view the *same* members model object — so the panel was torn down and fully re-sorted for nothing, on the dominant path. Key it on the model identity instead: same object, same members, no work; different object, the protection the latch is for. rightPanelReady must fold the latch in, or the chrome retires its members skeleton exactly while the panel is showing one. membersWireDelay moves into `d` (tests reach it through the view's private object), and the panel's own skeleton is released like the others rather than kept alive and hidden. The switch test now targets the permissioned channel, whose model really differs, and a new test pins that the shared-model switch costs nothing. * fixup! perf(chat): lazy, async member loading for user list and mention suggestions Extract the fully-wired CommunityChatLoader test harness (mock stack, loader wiring, type-prefix finders) into a shared helpers component. The members-skeleton suite is the first consumer; the community section suite above adopts it at the next stack rebase, removing ~90 duplicated lines per suite. * chore: update translations * perf: sorted users_model and PR comments * perf: Avoid swapping skeleton for the real view when swipeview animations are running * chore: update translations * chore: update translations |
||
|
Alex JbancaandAnastasiya
|
bd3fccc449 |
perf: load the chat and community sections asynchronously with skeletons (#21917)
* perf: load chat and community sections asynchronously with skeletons The section loaders own the chrome (StatusSectionLayout) and show the matching skeleton — with the real, functional header — while the actual section incubates behind an asynchronous Loader; the section's panels are proxied back into the loader-owned chrome once ready (full-page community views hide it). The communities portal loader turns asynchronous too. The pre-ready startup overlay recomposes from the skeleton panels, replacing the ChatLayoutLoading placeholder view (whose AppMain reference had been left dangling). * fixup! perf: load chat and community sections asynchronously with skeletons Each skeleton slot was gated on the whole section loader reaching Ready, so the header, chat list, message column and member list all swapped in at once, paced by the slowest panel. ChatView now publishes per-panel readiness and ChatLayout forwards it, letting each slot retire on its own. `root.item` is null until the section itself loads, so the old whole-loader behaviour remains the floor. The right panel is not deferred at this point in the stack, so its flag is constant; it becomes meaningful once the members panel moves behind a loader. Also drops `signal ready()` from both section loaders: `mainReady` is fed to AppMain by AppMainLoader and nothing has ever connected to `ready`, so the signal and the comment claiming AppMain owns the spinner toggle are both dead. * fixup! perf: load chat and community sections asynchronously with skeletons The startup overlay predates the loader-owned chrome. ChatLoader and CommunityChatLoader declare their skeleton panels as plain children, which Qt instantiates and paints even while the loader is inactive, so for the chat section the overlay now covers an already-correct skeleton with a duplicate of itself. Scoped to the two cases where nothing else paints yet: the communities portal (CommunitiesPortalLoader is gated on mainReady and owns no skeleton), and a community section during the window where activeSectionType is already `community` but the repeater has not produced any delegate — the same window the currentIndex fallback below already accounts for. * fixup! perf: load chat and community sections asynchronously with skeletons Release the chrome skeletons instead of hiding them: permanent visible:-gated skeletons re-evaluate their tile geometry bindings on every resize for the lifetime of the section (same class as the ChatContentView messages skeleton, caught in a resize profile). Each skeleton now lives behind a Loader gated on its slot's readiness. * fixup! perf: load chat and community sections asynchronously with skeletons The slots fell through to the real panel as soon as `root.item` existed. ChatView's panels are non-null Loader objects from the moment the section loads, so `?? skeleton` never saw the readiness flags: the LayoutItemProxy retargeted to an empty Loader, released the skeleton with setParentItem(null)/setVisible(false), and the slot painted nothing until the panel incubated. Gate each slot on its own flag instead. The skeletons collapse to bare Loaders keyed on `!ready`, dropping the wrapper Item whose `visible` the proxy also writes. tst_SectionLoaderChrome drives both loaders with a stub section whose flags are writable, so the contract is pinned as a binding rather than as a race against incubation. * fixup! perf: load chat and community sections asynchronously with skeletons The startup overlay's only remaining case was a community section with no repeater delegate yet, and it painted the chat-list skeleton there — wrong shape, replaced a frame later by CommunityChannelsSkeleton. Keep the overlay for the communities portal, which has nothing else painting, and let a missing community delegate fall back to the currentIndex loader, which already shows the right shape. * fixup! perf: load chat and community sections asynchronously with skeletons * chore(@e2e): fix tests according to the changes * fixup! perf: load chat and community sections asynchronously with skeletons * fixup! perf: load chat and community sections asynchronously with skeletons --------- Co-authored-by: Anastasiya <anastasija.ig@gmail.com> |
||
|
Jonathan Rainville
|
8b23a3fe3d |
feat(links): show experimental setting to enable linking to message
Part of https://github.com/status-im/status-app/issues/21457 Enables the message link sharing feature, but when enabled, shows a setting in the AdvancedView that let's the user decide if they want to see the feature. If both the setting and the feature flag are enabled, the option to copy messages becomes shown. |
||
|
Jonathan Rainville
|
8053844782 |
feat(link): implement link to message PoC
Fixes #21457 Implemented message link sharing in status-app behind a feature flag, including a new message context-menu action to copy a deep link that targets a specific chat and message. The feature flag was wired from Nim feature configuration through QML stores/loaders into the chat message components so the capability can be safely toggled at runtime. On the app side, deep-link activation now routes message links through shared URL module APIs instead of local parsing, so clicking a message link opens the correct chat and scrolls directly to the referenced message. |
||
|
Noelia
|
9867871563 |
fix(ActivityCenter): Open community member requests tab
Route community membership request notifications to the Members settings subsection and preserve the navigation while the community chat/settings views lazy-load. Also reuses CommunityMembershipSubSections for the members tabs to avoid mismatched enum values. |
||
|
|
d91f29f292 |
chore: cherry-picked commits from 'release/2.38.x' into master (#21035)
* chore: force build * fix(EphemeralNotifications): Suppress message ephemeral toasts Prevent chat message notification types from being added to the ephemeral notifications model shown in AppMain. Message toasts are currently considered too noisy for the in-app experience, so NewMessage, NewMessageWithPersonalMention, and NewMessageWithGlobalMention are skipped until their usefulness is reassessed. Fixes #20877 * fix: Android connectivity issues Fixing multiple deadlocks on instable connectivity and on app restarts. - go-waku deadlocks and peer reconnection storm fixed by https://github.com/logos-messaging/logos-delivery-go/pull/1302. This issue was deadlocking the messenger and any client restart would end-up in the same deadlock. - status-go filters the connection change and propagates only when the state actually changes https://github.com/status-im/status-go/pull/7447. This would trigger a peer reconnection storm with lots tens of changes on app kill/app start. - Handle dns failure at start-up, leaving the clients with no lightpush peer. App should start now with more peers. Send message should work from the start. https://github.com/status-im/status-go/pull/7447 - Make nim's connectionChange no-op on android. The connectionChange is managed by the android service itself since the service is persistent and the client is not. - Add a destruction watchdog for the android activity. If qt's onDestry blocks for more than 3 seconds we'll forcefully kill the app. Otherwise it can deadlock, making app restart impossible. * fix(MessageView): unbreak opening URLs when clicking on a text message - use a StatusTextArea as the internal part (renderer) of the StatusTextMessage and make it always enabled (disabling prevents the URLs from being opened) - by using a (Status)TextArea instead of a TextEdit, we can handle the context menu events correctly w/o disabling the edit control Fixes #20894 * fix(StatusMessage): unbreak opening chat image preview - on touch screens, the `button` is often `Qt.NoButton` - also fixup opening the image context menus; on touch screens, the Menu.popup() needs a point position to open at the exact point the user (long)pressed Fixes #20897 * fix: reopen keyboard (#20947) * ci: skip fdroid for release * fix: handle shutdown process to avoid race conditions - more appropriate - Added a global singleton instance for QGuiApplication to manage application lifecycle. - Replaced direct quit calls with singletonInstance.application.quit() for consistent application termination. * fix(Chat): Adjust chat lists margins and scrollbar spacing 1. Adjust 1:1 chat list margins and scrollbar spacing 2. Align community channel list margins and scrollbar spacing 3. Align member list margins and scrollbar spacing - Sets a thinner scrollbar width matching the Activity Center list pattern - Adds left content padding based on the swipe indicator width plus the standard minimum margin - Reserves right padding for the scrollbar and a small gap so delegates do not overlap it - Keeps the chat list geometry driven by `StatusScrollView` padding instead of manual child offsets - Refines chat list spacing to improve visual balance and consistency. Fixes #20593 * fix: IOS push notifications * fix: back button close the app (#20969) * fix(browser): android connector (#20885) * fix(browser): per-tab ConnectorBridge and webchannel * fix state correctness (connected flag) * fixes OpenSea sign-in failing when another dApp tab (e.g. hub) is open * fix stale listeners when reloading a page Fixes #20602 * chore: tests * fix(browser): route disconnect through connectorController fix(browser): make status user-scripts idempotent on same-URL reload fix(dapps): preserve connectorId for ConnectDAppModal disconnect fix(browser): reload via ensureLoaded + native reload * fix: assets page remains empty for ~15s for new user with 0 balances - Added a `loading` property to the `AssetGroupItem` type to track balance fetching status. - Updated `BalancesModel` to include loading state in data retrieval. - Modified `onAllTokensBuilt` to set loading state based on balance errors. - Loading states for balances introduced to the assets tab. Closes: #20980 * fix[Browser] Update the new tab image - also size-optimize some browser PNGs using `optipng` Fixes #20601 * fix(Browser): fix closing an empty tab using a kdb shortcut - we don't have an active WebView, so the abstract action wouldn't do anything * fix(Browser): opening a webpage for browsing activates the URL input field - make a distinction between opening a new tab for viewing, and an empty one (where we actually do want to start entering the URL) Fixes #20656 * fix(Browser): fix closing the DevTools using its own close button - don't break the settings binding, and update the internal action properly * fix(StatusBaseButton): fix setting explicit icon size from outside - don't take the value from `d.iconSize` which is precomputed, make it possible to set it properly via `icon.width/height` * fix(StatusBaseButton): rely on the pointer hover handler also for tooltips and text color - that way we don't get spurious hover events on touch * fix(StatusDialogHeader): use discrete corner radii - in Qt 6.11, we can set the radius on an individual rectangle corner, no need to create an extra fake Rectangle * fix(Browser): transparent favicon bleeds outside circle container - no need to set the border here at all Fixes #20683 * fix(Browser): minor browser UI fixes - increase font sizes and spacings - use default corner radius - element sizes upped to 44, icon sizes to 28 - use the standard SearchBox component - increase the webpage preview size Fixes #20443 * fix(Browser): try to active OSK when editing the URL Fixes #20891 * fix(Browser): disable IME for FindBar - adjust the flags to make it more privacy oriented * fix(Browser): update the New Tab illustrations - also add a dark variant Fixes #20601 * chore(Browser): always open a new tab with the "+" button * chore: remove `suppressKeyboardResize` for the Browser section - we `freeze` the native WebView when there's an active popup/modal Fixes #20967 * fix: mobile navigation to subsections Fixing broken bindings * fix: persist push notifications settings Was using the wrong persist key * Release 2.38.0 RC2 * chore: tag version 2.38 RC2 * chore: use a real token image that is coming from the token lists instead of locally stored images Using images from the token lists displaying any token is safe, while using locally stored images requires adding new icons for new tokens and delivering new builds, otherwise tokens may appear using incorrect image or be represented by their names (named icon, capital first letter). * fix: Allow navigating to the same chat * StatusChatInput: proper handling of attached images removal Closes: #20928 * StatusChatInput: minor sizing alignments Closes: #20570 Closes: #20495 * Chat view: text wrap for system label Closes: #20976 * StatusModal: StatusModal footer layout improved The sizing via background implicit height was not taking into account potential safe area margin. Now it's all calculated automatically, with proper handling of safe area. Closes: #20946 * fix: SafeArea handling and bottom sheet simplifications It elminates logical circular dependencies and binding loop warnings. * StatusChatInput: no jumps on backspace on ios Closes: #20898 * fix(display-name): fix editing display name is very laggy when in a comm Fixes #20963 The problem was that we called `isDisplayNameDupeOfCommunityMember` for each character on the display name edit. To fix it, I use a debounce on that function. I had to do the rest of the validation manually, since you cannot edit the error message from the outside if there is already a validation happening internally (it gets overwritten). * feat(gif): add count property to gifs model (#21028) refs status-im/status-app#20691 * chore: bump status-go --------- Co-authored-by: Jonathan Rainville <rainville.jonathan@gmail.com> Co-authored-by: Noelia <noelia@status.im> Co-authored-by: Alex Jbanca <alexjb@status.im> Co-authored-by: Lukáš Tinkl <lukast@status.im> Co-authored-by: Anthony Laibe <491074+alaibe@users.noreply.github.com> Co-authored-by: Siddarth Kumar <siddarthkay@gmail.com> Co-authored-by: Andrey Bocharnikov <andrey.bocharnikov@gmail.com> Co-authored-by: Michał Cieślak <michalcieslak@status.im> |
||
|
|
b416cdf22d |
chore: merge branch 'release/2.38.x' into master (#20950)
* Release 2.38.0 * fix(browser): hide sidebar when tapping outside (#20624) * fix: payment modal padding (#20702) fixes #20690 * fix(Browser): open URLs in a new tab from Downloads view Fixes #20685 * fix(RenameAccountModal): responsive layout - fix the overall layout, respecting the modal width - fix the pre-selected color (color vs color-string mismatch) - add the modal to Storybook Fixes #19325 * feat(StatusTextField): provide a standard edit context menu - allows to be styled propely using our Theme - disabled on mobile (iOS/Android provide their own) Fixes #20632 Iterates #20544 * fix(Portal): fix the community promo icon color Fixes #20689 * fix: cannot login via keycard Closes #20633 * chore: remove Polygon zkEVM chain - Deleted constants and UI elements related to Polygon zkEVM from wallet_constants.nim, Constants.qml, and Utils.qml. - Removed SVG icons for Polygon zkEVM from the assets directory. - Updated translation files to eliminate references to Polygon zkEVM Explorer in multiple languages. * chore: display "Unknown token" for tx in History tab if token details are missing For the tokens that are not in any of the list that the app operates with "Unknown token" should be used for the name, and raw value for crypto value instead of the token key. * fix: amount colors of the token breakdown pills make the amounts hard to read Closes #20701 * fix(Settings): fix overflow in Appearance view - add the view to Storybook Fixes #20645 * fix(Desktop) Increasing app height triggers portrait mode - lower the `portraitBreakpoint` to 640x480, and make the portrait/landscape criteria switch depend on `width` only - let the PrimaryNavSidebar follow the same logic - update TS files Fixes #20318 * chore(@e2e): text input * chore(@qml): object name for send button in chat * chore(@e2e): temp exclude password change from PRs * fix: don't try to (re)store window geometry/visiblity on mobile * fix(AppMain): reapply font size and padding when the orientation changes Fixes #20635 * fix(StatusSectionLayout): explicitly state the breakpoint - when switching to portrait mode * fix(main): restore visibility on mobile - similar to setting it to `visible` * fix(browser): android connector fixes (#20623) * fix(browser): stale request when closing connection popup * fix(browser): require webkit 1.12.1 * to enable addDocumentStartJavaScript fixes #20602 * fix(Syncing): Ensure mobile network sync is enabled by default Fixes `syncingOnMobileNetwork` DB value defaulting to false, causing status-go to block store node sync on mobile devices and leaving sent messages stuck in "sending" state. Fixes #20663 * fix(CommunitiesPortal): community cards are cut on the right - simplify the layout, use full width for the ScrollView - remove the internal scaling, causes more issues than it solves - use smaller card delegates when in compact mode - fix some other minor responsive issues - regenerate TS files Fixes #20728 * chore: remove status l2 sepolia (#20748) * ios: upgrade to SDK 26 * fix: avoid sync getAllTokens on every token refresh (#20786) fixes #20784 * fix(StatusChatInfoButton): don't open Profile dialog with pinned message - in 1-1 chats, the TapHandler would leak the click event to the underlying MouseArea, thus invoking both the PinnedMessagesPopup and the ProfileDialog Fixes #20658 * ConfirmationDialog: refactor to derive from StatusDialog * StatusDialog: delayed bindings to ensure proper height in bottom sheet mode * Settings: prevent navigating to settings on sign out request in portrait mode * AdvancdedView: prevent options switching before confirmation * fix(StatusBaseInput): no placeholder with preeditText - also hide the placeholderText when there are suggestions from the native virtual keyboard on mobile Fixes #20774 * fix(browser): android snapshot colors (#20791) * fix(connector): parallel dapp requests race (#20703) * fix(browser): fix crash fixes #20591 * chore: bump status-go * chore: hide data verified by Nimbus (#20811) fixes #20788 * feat(connector): ephemeral dApp records (#20808) * feat(connector): ephemeral dapp records refs status-im/status-app#20676 * fix: copilot comments * chore: bump status-go * ChatColumnView: workaround for QTBUG-146653 It was causing that selecting mention from suggestions list was not possible on mobile. Closes: #20798 * StatusChatInputTextArea: take preedit text into account when filtering mentions It's necessary to handle suggestions correctly (filtering based on the user input). Closes: #20743 * StatusChatInputTextArea: take preedit text into account when filtering emojis * fix: swapped ui in history (#20818) Swapped word is now staying in one row * fix(iOS/FileDialog): Use native pickers for image selection Route iOS file selection through native platform pickers to avoid Qt file dialog sizing issues on mobile. - Use `UIDocumentPickerViewController` for document-based flows such as backups and JSON imports. - Add a photo-library mode to `StatusFileDialog` for image selection flows. - Use the native iOS photo picker for profile picture, community logo/banner, and image selector uploads. - Return selected files/photos through the existing `StatusFileDialog` selected file API. - Added support for multi file selection. Closes #20704 * chore: a huge delay between balance/history update (#20812) Closes #20751 * fix(wc): reconnect broken pipe (#20809) * recreate wc client after Resume() fixes #20767 * fix(Search): focus the user/channel/chat search fields - StatusTextField: theme/style according to Status design - SearchBox: derive from StatusTextField instead of the clunky StatusInput; we only need one-line input here anyway - fix usages of the SearchBox, notably fixup the need to use a native validator if needed; greatly simplifies the code to use this component - regenerate TS files Fixes #20754 * chore(@e2e): fix locators for search boxes * chore(@e2e): fix for seed phrase * fix(ThirdpartyServicesPopup): prevent eliding the instructions - use a simple RowLayout with StatusIcon+StatusBaseText, with wrap mode turned on - don't hardcode the InformationTag pill height - remove the redundant Close button Fixes #20706 Fixes #19981 * chore: don't show unknown token for nft name in history view Fixes: #20817 * fix(Onboarding): Make sync pairing page scrollable Make the sync pairing page scrollable so the instructions button stays reachable when the QR scanner content overflows. Fixes #20638 * fix(StatusSectionLayout): Fix SwipeView panel positioning Ensure the portrait `StatusSectionLayout` visually follows `SwipeView.currentIndex` changes on Android by repositioning the internal view after programmatic panel navigation. This prevents the layout from keeping the previous `contentX` while the logical index has already changed. Fix #20771 * Android: workaround for triggering full-screen mode after screenshot On Android 15, taking a screenshot and invoking sharing dialog was triggering full-screen mode, not restored when sharing is finished. Closes: #20612 * fix: GifPopup and StickersPopup bottom-sheet layout improved Closes: #20571 * StatusStickersPopup: layout improved * emoji/gif/stickers popups sizing ad-hoc patches * Perf/cherry pick v1 (#20802) * perf: Async start messenger The startMessenger backend call is a lengthy process, blocking the main thread for a few seconds. Moving it to async tasks gives the main thread the chance advance on the login work until the messenger starts successfully. Perf improvement on my heavy account: Before: 17 sec warm start-up After: 14 sec warm start-up - Added `onMessengerStarted` method to `AccessInterface` to handle messenger start errors. - Implemented `onMessengerStarted` method in `Module` to emit error notifications. - Introduced `SIGNAL_MESSENGER_STARTED` constant for signaling messenger start events. - Created `asyncStartMessengerTask` to manage asynchronous messenger start operations. - Updated `startMessenger` method in `Service` to utilize the new async task and handle responses. * fix: Trim StartMessenger async task output * fix: review coment - remove dead code * perf(qml): Drop the file selectors * fix(webviewLoader): log on error * perf: seed contacts with community members Iterates: https://github.com/status-im/status-app/issues/20228 Resolving community members creates a high frequency RPC flood at start-up when the app tries to eagerly resolve every community members. On Android Status community adds around 2 sec in CPU time on warm start-up. The solution implements an enriched community member type and contact type returned from status-go. The app will receive this extra data and seed the contacts cache (instead of creating the contacts cache using 4 separate RPCs for each member/contact). * perf: enhance contact seeding with MemberSeed structure and optimize duplicate handling * feat: Migrate android binder from files to shared memory This commit aligns the client-server communication with standard Android solutions - direct binder calls and shared memory. This is done both for perf reasons (has a big impact on high frequency callse) and security concerns (no unencrypted data is touching the disk). There are two main changes in this commit: 1. Direct communication between client and service when the payload is below 64KB. This is for high frequency and ligh calls (like colorId). The file based communication overhead is just too high for such usage. 2. Shared memory - When the payload is bigger than 64KB we'll use the shared memory * perf: Avoid unnecessary community and chat copies The nim profile trace is dominated with community and chat object copies. There are 3 main types of changes: - using `lent` to borrow a community from the service. It can be used as a return type only - using openarray in favor of seq for proc args, where `lent` cannot be used. - use "communityId" instead of full community where openarray or lent migration would cascade into lots of changes * perf: Optimize community role retrieval in getChatItemFromChatDto * perf: Move `getCachedCurrencyFormats` to threadpool * fix: Fixing merge errors * perf: Granular control qml compilation and loading of main layouts This commit aims to split the qml compilation into smaller chunks and schedule the compilation at the appropriate time. Approach: Each main section lives behind a loader component that has 2 purposes - load the component at appropriate times and defer the qml compilation until the loader is created. The same approach was applied to AppMain.qml and on top of this we'll need to make sure we're loading the AppMain at an appropriate time so that we'll avoid many intermediary states if the nim layer isn't ready for it. For this, I've introduced a new component - QmlCompiler. It has a list of main components and can precompile the qml component or make sure to load it all if needed (e.g while the onboarding runs we can use that time to preload everything) This approach is fully compatible with Loader.asynchronous usage and implementing loading states for the components - the community and chat loaders already implement it partially. Can be extended to preload all the sections in the background while the user is working on the current section. - Added MarketLoader.qml to handle market-related UI loading. - Introduced NodeLoader.qml for loading node-related UI components. - Created PopupsLoader.qml to manage various popups within the application. - Developed ProfileLoader.qml for loading user profile sections. - Implemented WalletLoader.qml to manage wallet-related UI components. - Added QmlCompiler.qml to centralize URL management for QML components. - Updated qmldir to include new loaders for better modularity. - Refactored main.qml to utilize the new AppMainLoader and improve loading logic. * fix: Correct spelling, function args and bindings * chore: bump vendors * fix: home selection doesn't open the proper 1x1 chat There are 2 bugs: property binding override from within the component internals and a signal signature mismatch * fix: handle shutdown process to avoid race conditions - Added a custom exit procedure (https://en.cppreference.com/c/program/_Exit) to bypass libc static destructors on mobile devices, preventing potential race conditions during shutdown - Ensured proper teardown of the threadpool in the StatusFoundation delete method Fixes #20855 * fix(nft): disable more chains (#20866) * fix(collectibles): add ink, katana to unsupported list fixes #20717 * fix(dapps): dapp name html injection (#20881) * chore: add dapp fields html injection to storybook * fix(dapps): use the PlainText format for dApp controlled strings fixes #20879 * fix(Portal): do not autofocus the Search field Fixes #20870 * fix: Community members in community settins * fix(android): async webview construction (#20916) fixes #20886 * fix(chat): restore iOS paste menu behavior Use the platform popup for the chat input context menu on iOS so paste and selection actions follow native text editing behavior. Avoid toggling readOnly during iOS paste handling, since that dismisses and restores the virtual keyboard. Keep Android using the existing null context menu path. Closes #20588 * fix(StatusTextField): Use native paste menu for text fields on iOS Use the native iOS context menu for StatusTextField and keep Android on the default behavior. * fix(android): battery usage while the app is in the background This commit bumps status-go to include https://github.com/status-im/status-go/pull/7440. As a result the message sending is paused while in the background to stop the high frequency mvds loops that will prevent Android from going into sleep. To preserve message sending while the app is in the background/killed we'll have to wake messenger briefly on the OS intent. We'll resume messenger for 60 seconds - enough to push the message through and then it will be paused again unless the app goes back to foreground. This results in less battery usage and less events piling up in the qt event loop while the app is in the background. * chore(@e2e): temp disable syncing test in release 2.38 * fix(chat): prevent MessageView from stealing ImageMessage right-clicks (#20889) fixes #20789 * fix: cliping modal input (#20944) * feat(notifications): update notification settings copy Refresh notification settings wording across desktop and mobile, renaming the settings entry to “Notifications” and updating the enable notifications popup copy for iOS and other platforms. Add clearer privacy messaging for APNs, on-device mobile delivery, and desktop OS notifications. Restore the iOS centralized notification options section and reuse the sound/volume controls across general and iOS notification settings, while keeping platform-specific test notification behavior. Part of #20628 * feat(PushNotifications): Update mobile notification banner display logic Adds local display state for the mobile push notification banner so it can respect the “Don’t ask me again” choice and avoid reappearing within the same minor version. The banner is now shown only on mobile when private notifications are disabled, the current app minor version is at least 2.38, the user has not opted out, and the banner has not already been shown for that minor version. Patch updates reuse the same stored minor version, so they do not retrigger the banner. Also wires the current app version into the handler and adds the “Don’t ask me again” switch to the popup. Closes #20902 * fix(NotificationsView): Fix filter exemptions with stable scroll position Move exemption search filtering from delegate visibility toggles to a SortFilterProxyModel, so the list only instantiates matching items instead of hiding non-matching delegates. Keep the exemptions list height stable while filtering, capped to the visible settings page height, to avoid the page scroll jumping when the filtered result count shrinks without leaving a long empty scroll area. * fix: failed e2e test fixed * chore(@e2e): fix after conflicts resolution --------- Co-authored-by: Anthony Laibe <491074+alaibe@users.noreply.github.com> Co-authored-by: Andrey Bocharnikov <andrey.bocharnikov@gmail.com> Co-authored-by: Lukáš Tinkl <lukast@status.im> Co-authored-by: Anastasiya <anastasija.ig@gmail.com> Co-authored-by: Noelia <noelia@status.im> Co-authored-by: Siddarth Kumar <siddarthkay@gmail.com> Co-authored-by: Michał Cieślak <michalcieslak@status.im> Co-authored-by: Alex Jbanca <47811206+alexjba@users.noreply.github.com> Co-authored-by: Alex Jbanca <alexjb@status.im> |