https://bugs.documentfoundation.org/show_bug.cgi?id=153506
--- Comment #24 from ady <[email protected]> --- (In reply to Mike Kaganski from comment #23) > I disagree that this is a bug. Yes, this is a behavior change. However, both > behaviors have their benefits and logic, and merging the multiple CFs was > done to avoid much worse problems. > > OTOH, if there is a way to only merge ranges on copy of cells, not on sheet > copy, that would be a possible improvement. IDK about pros and cons, because I have no idea which issues prompted such behavior's change. BTW and FWIW, I don't recall seeing anything about such thing in any Release Notes – maybe I just missed it. Any links to any kind of info about this, anywhere? What I do know is that, as a simple common user, I would expect that a copy of a worksheet would behave the "same" as the original. If a formula is using an absolute reference for a worksheet, I would expect to be kept in the newly-pasted copy with the same absolute reference. The same goes for a CF that depends on an absolute reference. I have to admit that, even if I would had known about such behavior's change, I'm not sure I would had realized I was about to make a mistake in some common "duplicate sheet" action. Of course this is speculation ATM. IOW, I could understand the frustration of users finding out that what was supposed to be a copy, it is not really an exact copy. That is, if they happen to find out about it. -- You are receiving this mail because: You are the assignee for the bug.
