If you call a method in a notebook snipped, and expand that method and then use cmd-r on the expanded method, after the rename the notebook method retains the old name and when collapsed its now pointing to something that doesn't exist anymore and so doesn't expand.
While it would be cool for all notebook snippets to be renamed globally (like calling methods do) - I would at least expect the locally expanded version to participate in the rename.
In the above you can see a rename about to happen to contentsDecoded - on completion, the originial snippet call will remain contentsDecoded and thus point to nothing
Refactorings in code are not (yet) applied to pages. If you refactor the same method in the code from the page, the page code will be renamed properly. So, it's not a bug. It's not yet done.
If you call a method in a notebook snipped, and expand that method and then use cmd-r on the expanded method, after the rename the notebook method retains the old name and when collapsed its now pointing to something that doesn't exist anymore and so doesn't expand.
While it would be cool for all notebook snippets to be renamed globally (like calling methods do) - I would at least expect the locally expanded version to participate in the rename.
In the above you can see a rename about to happen to contentsDecoded - on completion, the originial snippet call will remain contentsDecoded and thus point to nothing