https://bugs.documentfoundation.org/show_bug.cgi?id=138468
--- Comment #11 from R. Bingham <rdbing...@verizon.net> --- (In reply to Roman Kuznetsov from comment #10) > So, your "problem" was in installed extensions? Can we close it as NotABug? Please indicate if the color picker widget is statically configured via a text-editable file and if so its path in the user or host-common profile. I suggest it is unwise to so readily dismiss this case as NotAbug. I happen to be a retired IT systems engineer with experince as both an IT vendor and an IT customer and I have some interest in contributing to LO bug root cause analysis and improving LO. I can tell you from my vendor experience that even if a bad extension or bad extension install process caused this color picker dysfunction, for the average LO user it still has LO's name on it especially if they do not associate the appearance of the dysfunction with an extension management event. For example, does LO provide an API for extensions to use to statically modify the user profile during install/first use/uninstall or conversely does LO call in to enabled extensions via an LO-spec API at startup to dynamically assemble the color picker? If so, why does that API not perform simple QA checks such as for palette namespace collisions across enabled extensions or enforcing LO-reserved names if any? Quality Assurance deficit bug if it does not. Further, if I can identify a particular extension causing the issue, then LO should really want to know about that and remove it from the public extensions repo. Regards. -- You are receiving this mail because: You are the assignee for the bug.
