weifangsun@ - Currently even between Chrome apps, we cannot drop data to the minimized apps. So I'd like to prioritize the other issue like introducing tests and drag and drop Android -> Chrome. Please let me know if we need to increase the priority of this issue. Thanks!

hirono@ - Definitely agree this should be lower priority... in fact, before we work on this, I'd like to better understand the use case for enabling this feature.

It's actually possible by entering overview mode (f5), activate (using key nav), then drop.

It's not hard to just activate the window when you drag & hold on the minimized window's icon on the shelf, but I'll leave it to waifangsun@ for triage.

Hi,
if it's not that difficult, I'd like to pick up this as one of my Noogler-starter tasks. oshima@-san, would you be able to share some code pointers for this?

I think this behavior (un-minimizing the app when the user drags something onto a minimized app) is very common in modern OS UI.

Here is the callback called when you click the item on the shelf.

https://cs.chromium.org/chromium/src/ash/shelf/shelf_view.cc?rcl=85353fb37af561530c775af46f9a8a4b679b9487&l=471

I THINK the following is the code called for app

https://cs.chromium.org/chromium/src/chrome/browser/ui/ash/launcher/app_shortcut_launcher_item_controller.cc?rcl=329b2777374694078f22fd12cd804954e72b1566&l=73

<files-triage>

Looks like this one is pending on weifangsun@'s triage/decision (see comment #5.) Temporarily reassigning to her.

Sounds like this is a good starter bug, but not a priority to implement at this time.

I was thinking of picking this up as a starter task back in January, but I picked up other tasks and didn't start working on it.

I think this is still a good starter task for future Nooglers.

please triage for prioritization