treeview of chrome dev tool source panel workspace display incorrectly when creating new file and rename a file
Reported by
liuway...@gmail.com,
Jan 19 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: issue#1 1. open chrome dev tool and switch to source panel 2. add folder to workspace 3. rename a file within the folder just added to the workspace 4. new file with the new name is created and the old file with old name still exists issue#2 1. open chrome dev tool and switch to source panel 2. add folder to workspace and make the folder expanded 3. right click on the folder just added to the workspace and select 'new file' 4. enter a name for the new file and press enter 5. two files showing in the treevew, they are 'NewFile' and the one with the name just entered What is the expected behavior? issue#1 file with old file name should not appear in the treeview. issue#2 the 'NewFile' should not appear in the treevew. What went wrong? However, the actual behaviours correctly when you check on the disk, the file is renamed and new file is created, no duplicated files. It's just the treeview not working properly. Did this work before? N/A Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.12.2 Flash Version: Shockwave Flash 24.0 r0
,
Feb 11 2017
These both are fixed in https://codereview.chromium.org/2651043006 Should work beautifully in Chrome Canary. Thanks for the bugreport though!
,
Feb 13 2017
I tried the canary v58. I notice that when creating new file, the file name is default to `NewFile` and not been focused in editing mode. Now we should click the `NewFile` and manually rename it. Previously this is working. Can we bring it back? I think naming a file immediately after creating it is wanted behavior.
,
Feb 13 2017
@liuwayong: i can't reproduce it on 58.0.3012.0 - could you please file a separate bug and give more details?
,
Feb 14 2017
hi @lushnikov, thanks for replying. never mind, I test it on chromium 58.0.3012.0 and everything's okay. it's the canary 58.0.3011.0 witch is broken.
,
Feb 24 2017
hi @lushnikov, I filed an new bug about the issue mentioned above, it can be reproduced in recent 58.0.3021.0 https://bugs.chromium.org/p/chromium/issues/detail?id=695755 |
||
►
Sign in to add a comment |
||
Comment 1 by kavvaru@chromium.org
, Jan 20 2017Labels: -Type-Bug -Pri-2 M-55 OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)