Created attachment 122581 [details] Invalid category names 1) Create new table, e g with data: 1 4 2 2 3 1 3 2 2 4 1 1 2) select this range 3) add column chart 4) Right-click on X-Axis -> select "Data Ranges..." 5) Change categories to: "Caaaa1","C2","C3" 6) Click OK 7) It's still "1 2 3" in categories names. Moreover, if you try to load proper XLSX with manually set category names - the resut will be the same - "1 2 3 ..."
Yes, it doesn't change the X axis labels. The correct form least for me is: "Caaaa1";"C2";"C3" so semicolons instead of commas. Otherwise the background of the input field was red. But it doesn't work.. I tried in 3.5, but there the background of the input field was red with commas or semicolons and it would not accept the categories. Serg: set the version to the earliest you saw the problem in. Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: a6f876d45bd4e41a7143594a6cb11b6893a0f620 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-02-11_00:07:38 Locale: fi-FI (fi_FI)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear Serg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Serg, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
With a master build from today, custom categories: - Are accepted but not shown when separated by commas (e.g. "Caaaa1","C2","C3","kk") - Are not accepted at all when separated by semicolons (e.g. "Caaaa1";"C2";"C3";"kk") Adding UX to the conversation, as I am not sure if custom labels entered by hand should even be accepted. The documentation makes it sound like only ranges should be accepted: https://help.libreoffice.org/7.5/en-US/text/schart/01/wiz_data_series.html Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 1fd42472e2b1a2169d56e62ef11aa7ee1f7815e7 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
Created attachment 183852 [details] ODS file to test To test: 1. Open ODS file 2. Double-click on chart to enter edit mode 3. Right click on X axis > Data ranges... 4. Data series tab 5. Change Categories value do a custom vector of strings
When I try to type some vector the application crashes with the second item (A;B). But if I enter the labels into cells like E1:E4 and select this range everything works as expected. One could now argue to block direct editing. But that would be awkward in many other cases. For example I collect continuous data and add it on top of the sheet (don't want to scroll). Inserting a row on top moves the chart content/range and I have to update manually. Given the chart is a bit more complex it's much easier to update per direct editing than doing the range selection. My take: fix the bugs and block crashes. If users enter inappropriate values to fields it should be shown and not accepted. Version: 7.4.3.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (en_US.UTF-8); UI: en-US 7.4.3-1 Calc: threaded
This is a hairy mess.. The range selector was supposed to not support anything but cell range references, where the list separator used is the function parameter separator, so whether it's ',' or ';' depends on configuration. Later in 2012 an import of static literal category labels from .xlsx was added, but only half i.e. it does not work through the UI nor in any of the data sequences obtaining code. Additionally, that check whether content/input is valid accepts any badly formed string, not only string literals. Even worse, the check is valid in any of the reference input fields, not just categories. Worse yet, the interface used by Chart is part of the public API so simply changing it for just the categories case isn't possible but probably would need an optional additional API.
Complex one indeed. Thanks for the history, Eike! Changing blocked meta to "OOXML charts" as this is first and foremost an interoperability / filter issue. Also, related to complex axis label categories + custom strings *for the Name field*, there's this regression: Bug 142346 I couldn't reproduce the crash Heiko describes though: (In reply to Heiko Tietze from comment #7) > When I try to type some vector the application crashes with the second item > (A;B). Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 01a3cc1e55034f7703219d4bbb209de7c37bf07b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (en_AU.UTF-8); UI: en-US Calc: threaded
It gets even worse.. the xlsx compatibility thing needs to accept an unquoted word (that is not a named range) as "Range for Names" which will be displayed as label, I stumbled over that sc/qa/uitest/chart/tdf98690.py test when trying to narrow things down to accept only properly quoted string. That appears to have been (unintendedly?) implemented with the commit https://bugs.documentfoundation.org/show_bug.cgi?id=142346#c4 points to. For the crash Heiko mentioned, I experienced an occasional crash but could not reproduce it yet.
The more I think about it the more I am convinced that the tdf98690.py test tests a broken document (https://bugs.documentfoundation.org/attachment.cgi?id=123610 of bug 98690 saved already broken by LibreOffice) and so far only worked by accident. Those names can not be unquoted whatever strings, probably not even in Excel as there they'd have to fulfil the expression constraints as well.
(In reply to Eike Rathke from comment #10) > For the crash Heiko mentioned, I experienced an occasional crash but could > not reproduce it yet. Cannot make master crash, and 7.4 is has no debug info. Neither it crashes when started from the command line! Very elusive bug.
Stumbled over the need to edit the data range field: if a chart is defined as $Sheet1.$A$1:$A$10 it's not possible to ctrl+click select/unselect individual cells via the range definition. One has to enter manually $Sheet1.$A$1;$Sheet1.$A$3;$Sheet1.$A$7:$A$10.