https://bugs.documentfoundation.org/show_bug.cgi?id=148979
--- Comment #5 from Miklos Vajna <vmik...@collabora.com> --- Not updating all fields automatically has a few benefits: 1) updating all these fields can take a bit of time for large documents, so doing it on every keypress would be seen as a problem by some users (Writer could be too slow to be usable) 2) we could also have code to track the dependencies of all fields (similar to e.g. what Calc does), not having that code makes the codebase simpler 3) there is not much pressure on us to do such auto-updates in all cases, e.g. Word doesn't update fields even on file load So given that users learned to live with not auto-updating fields, this allows a bit simpler and faster code. That being said, we do auto-update a few fields, e.g. moving a page number field to a next page auto-updates it. On the other hand, users learned that hand-editing a generated ToC is possible, and if we take that away, they can see that as a regression. With these in mind, completely eliminating the explicit field update doesn't sound good. Adding a possibly to explicitly update an individual field makes sense to me. -- You are receiving this mail because: You are on the CC list for the bug.
