fix: prevent search field interaction during drag operations

[wjyrich]

Fixed an issue where the search field in fullscreen mode remained interactive during drag-and-drop operations, causing potential conflicts between text input and drag gestures. The search field now properly disables interaction when any item is being dragged by checking the currentlyDraggedId state.

The change adds a condition to the search field's interactive property to ensure it only becomes interactive when no drag operation is active (dndItem.currentlyDraggedId === ""). This prevents accidental text input while users are dragging items and improves the overall drag-and-drop user experience.

Log: Fixed search field remaining interactive during drag operations in fullscreen mode

Influence:

1. Test drag-and-drop operations in fullscreen mode while search field is visible
2. Verify search field becomes non-interactive when dragging starts
3. Confirm search field returns to interactive state after drag operation completes
4. Test search functionality when no drag operations are active
5. Verify the fix doesn't affect search field behavior in normal usage scenarios

fix: 修复拖拽操作期间搜索字段保持交互状态的问题

修复了全屏模式下搜索字段在拖放操作期间保持交互状态的问题，该问题可能
导致文本输入和拖拽手势之间的冲突。现在搜索字段在检查到有项目被拖拽时
（currentlyDraggedId状态）会正确禁用交互。

此更改为搜索字段的interactive属性添加了一个条件，确保只有在没有拖拽操作
活动时（dndItem.currentlyDraggedId === ""）才变为交互状态。这防止了用户 在拖拽项目时意外输入文本，并改善了整体拖放用户体验。

Log: 修复了全屏模式下拖拽操作期间搜索字段保持交互状态的问题

Influence:

1. 测试全屏模式下搜索字段可见时的拖放操作
2. 验证拖拽开始时搜索字段变为非交互状态
3. 确认拖拽操作完成后搜索字段恢复交互状态
4. 测试没有拖拽操作活动时的搜索功能
5. 验证修复不影响正常使用场景下的搜索字段行为

PMS: BUG-315733 BUG-315729

Summary by Sourcery

Bug Fixes:

• Disable the fullscreen search field while an item is being dragged to avoid interaction conflicts between text input and drag gestures.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Ensures the fullscreen search field becomes non-interactive while any drag-and-drop operation is active by gating its interactivity on the drag state in addition to popup visibility.

Sequence diagram for search field interactivity during drag-and-drop

sequenceDiagram
    actor User
    participant FullscreenFrame
    participant DndItem
    participant SearchField
    participant FolderGridViewPopup

    User->>FullscreenFrame: Enter fullscreen mode
    FullscreenFrame->>SearchField: Initialize interactive = !FolderGridViewPopup.visible && DndItem.currentlyDraggedId == ""

    User->>DndItem: Start drag on item
    DndItem->>DndItem: Set currentlyDraggedId = draggedItemId
    FullscreenFrame->>SearchField: Reevaluate interactive
    SearchField-->>FullscreenFrame: interactive = false (because currentlyDraggedId != "")

    User->>DndItem: Complete drag operation
    DndItem->>DndItem: Set currentlyDraggedId = ""
    FullscreenFrame->>SearchField: Reevaluate interactive
    alt FolderGridViewPopup not visible
        SearchField-->>FullscreenFrame: interactive = true
    else FolderGridViewPopup visible
        SearchField-->>FullscreenFrame: interactive = false
    end

Loading

File-Level Changes

Change	Details	Files
Gate fullscreen search field interactivity on drag state to avoid conflicts between text input and drag-and-drop gestures.	Updated the search field's interactive condition to also require that no item is currently being dragged (dndItem.currentlyDraggedId === "") Preserved existing behavior that disables interaction when the folder grid view popup is visible	qml/FullscreenFrame.qml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Instead of directly comparing dndItem.currentlyDraggedId === "", consider exposing a boolean like dndItem.isDragging so the binding expresses the intent more clearly and is less coupled to the internal representation of the drag state.
• If dndItem or currentlyDraggedId can be undefined during initialization or teardown, it may be safer to guard this binding (e.g., via a default value or null-check) to avoid runtime binding errors.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Instead of directly comparing `dndItem.currentlyDraggedId === ""`, consider exposing a boolean like `dndItem.isDragging` so the binding expresses the intent more clearly and is less coupled to the internal representation of the drag state.
- If `dndItem` or `currentlyDraggedId` can be undefined during initialization or teardown, it may be safer to guard this binding (e.g., via a default value or null-check) to avoid runtime binding errors.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BLumia, wjyrich

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wjyrich]

/forcemerge

[deepin-bot]

This pr force merged! (status: blocked)