TraceSift drop zone rejects files in browser panels without File.path

未關閉
#110 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
半天
新手友好度
45/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
領域
frontend

研究方向

The payload names no source files. Start by finding the TraceSift drop handler in the browser panel code, the part that requires File.path and shows the 'Cannot be read from a drop here' message. Reproduce by passing a standard File object with a Chrome Performance JSON to that handler. Done means either the dropped file is analyzed locally, or the native file-picker requirement is shown before a drop is attempted, with existing size limits kept.

由索引模型根據 Issue 內容生成。

描述

bug

What happened

The presenter dragged a profile from Finder into the TraceSift upload pane in the T3 Code browser panel. The pane showed Cannot be read from a drop here. Click to choose it from disk. The drop handler requires a host-specific File.path and rejects the file before it checks the profile format. The same condition affects supported JSON files in browser hosts that expose only standard File objects.

Expected behavior

Test dropping a supported Chrome Performance JSON in T3 Code. Where the panel can import a dropped file, accept it and analyze it locally. Where only a native file picker is supported, make that interaction clear before the user attempts a drop. Keep the existing local processing and profile size limits.

主要語言
C++
星號
243
分支
21
平均合併
15 小時 6 分鐘
30 天內合併 PR
57

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

callstackincubator/codex-mobile-dev-plugin 的其他 Issue

查看 callstackincubator/codex-mobile-dev-plugin 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。