Issue 126705 - Chart corruption with logarithmic scale and incorrect error bar data
Summary: Chart corruption with logarithmic scale and incorrect error bar data
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 4.1.2
Hardware: All All
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-28 11:58 UTC by islepnev
Modified: 2017-05-20 10:03 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Chart corruption with logscale, Undo leaves corrupted chart (39.24 KB, image/png)
2015-11-28 11:58 UTC, islepnev
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description islepnev 2015-11-28 11:58:40 UTC
Created attachment 85174 [details]
Chart corruption with logscale, Undo leaves corrupted chart

Chart disappears from spreadsheet when axis scale set to logarithmic and negative error indicator is below zero. This happens when DATA_VALUE > ERROR_BAR_VALUE. 

Expected behaviour is ignore invalid input data and not draw error indicator at all, but not corrupt the whole chart. If either of error indicator bounds become NaN, ignore such indicator.

Undo operation does not work as expected, chart remains corrupted after Undo.
Comment 1 oooforum (fr) 2015-12-07 09:53:10 UTC
Your bug report is being closed as NOT_AN_ISSUE due to a lack of information which is needed in order to accurately reproduce and confirm the problem. We need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of AOO that you have confirmed the bug to be present

b) Provide a step-by-step procedure to reproduce (the simpler will be the better)

c) Provide any test case(s) which will help us confirm the problem (like a sample document)

d) Provide screenshots of the problem if you think it might help


Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.