excluded folers come back to the chrome devtool workspace after re-generated
Reported by
liuway...@gmail.com,
Feb 10 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3005.2 Safari/537.36 Steps to reproduce the problem: 1. add local folder to workspace 2. right click on a sub-folder and exclude it, say the sub-folder name is `build` 3. run command `mkdir build && touch build/foo.txt` in terminal and the build folder comes back in the treeview of workspace 4. or manually creating the `build` folder from mac finder and coping a file into it also can reproduce the issue What is the expected behavior? the excluded folder should keep been excluded What went wrong? the excluded folder comes back Did this work before? N/A Chrome version: 58.0.3005.2 Channel: canary OS Version: OS X 10.12.2 Flash Version: Shockwave Flash 24.0 r0 both stable v56 and canary v58 are broken
,
Feb 10 2017
,
Feb 18 2017
Yes, the same happens for me with .git folders and node_modules/.
,
Feb 18 2017
and also they excluded files come back to the search results
,
Apr 6 2017
M58 stable is approaching soon, can we have a fix before M59 hits stable.
,
Apr 10 2017
That's not a regression, removing the release-block label.
,
Dec 6 2017
This was supposed to be fixed by https://chromium-review.googlesource.com/c/chromium/src/+/798735, but it's buggy.
,
Mar 19 2018
This is still a bug in Chrome 63 Linux. Every time I rebuild by meteor app the /.meteor/local folder reappears in the workspace and pollutes search results. |
||||
►
Sign in to add a comment |
||||
Comment 1 by nyerramilli@chromium.org
, Feb 10 2017