Semnatic bug: Error bars

Semnatic bug: Error bars

Posted by: storm.binary on 22 November 2019, 5:52 pm EST

• 

  storm.binary

  • Post Options:
  • Link
    Copy

  Posted 22 November 2019, 5:52 pm EST

  Hello,
  
  In the SpreadJS web designer:

  1. Add chart elements → Error bars.
     
     An opportunity must be given to the user to choose a column from the sheet for errors. You can not decide what the error boundaries might be from the y values. What you have is scientifically WRONG.
     
     A typical example of just learning to program nothing else. If don’t understand it ask someone who does.

  b) Add chart elements → Error bars → More Error bar options,
  
  or
  
  Add chart elements → … → More … options. What is it suppose to do? Load another bit of div section. Well it doesn’t. The RHS panel is blank.

  Regards,

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 24 November 2019, 10:27 pm EST - Updated 3 October 2022, 1:33 am EST

  Hi,

  1). If we understand correctly, you need to have an option to adjust the error boundaries. In this case, you may double click on the Error bar and a panel on the right side will open up with the required settings. Please refer to the following snapshot:
  
  

  

  1277×949 63.4 KB

  
  
  We have picked this behavior from MS Excel. Please let us know if our understanding is incorrect or if you have some other expectations

  2). More error bar option is supposed to open a dialog to select the series for which we need to open the error bar. Please refer to the following gif demonstrating the expected behavior and let us know if you are observing any different behavior:
  
  
  
  I’ve tested the functionality in Chrome, Firefox, Edge and IE11 and it is working fine in all the browsers on my machine. If you are observing any issues could you please let us know about your machine configuration(OS, browser) so that we could test on a similar environment too.

  Regards
  
  Sharad

• 

  storm.binary

  • Post Options:
  • Link
    Copy

  Posted 25 November 2019, 5:29 pm EST

  Hello Sharad,
  
  I think part of the problem is because of the fact that I have no properties panel on the rhs. Furthermore, I suggest for the user to be able to indicate column as the source of error bars.
  
  Thank you.
  
  Mehran

  Edit: not sure if my screen capture was attached.

• 

  storm.binary

  • Post Options:
  • Link
    Copy

  Posted 25 November 2019, 5:31 pm EST - Updated 3 October 2022, 1:33 am EST

  Here it is:
  
  [url=https://ibb.co/MV3P22f]

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 26 November 2019, 7:27 pm EST

  Hi Mehran,

  We are sorry but we are unable to replicate the issue at our end. I have tested it on the Firebox(71.0.1) on Windows 10(version 1809) and macOS(10.10.6). Could you please share your machine configuration so that we could test on a similar environment
  
  Also please let us know if you are able to replicate the issue in other browsers too?

  Furthermore, I suggest for the user to be able to indicate column as the source of error bars.
  
  Could you please elaborate some more about the requirement so that we could have a better understanding of the requirement and forward it to the dev team.

  Regards

• 

  storm.binary

  • Post Options:
  • Link
    Copy

  Posted 27 November 2019, 12:24 am EST

  Hi,
  
  Firefox 70.0.0.1,
  
  Win 10 x64, Pro version 1903, build 18362.418
  
  16GB RAM

  Able to load the rhs panel in Microsoft Edge and Chrome v78.0 but not FF v70.
  
  Regards,
  
  Mehran

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 27 November 2019, 5:41 pm EST

  Hi Mehren,

  I tried the sample on Windows 10 Pro version 1903, build 18362.476 using Firefox 70.0.1 but is still unable to replicate the issue.
  
  Could you please provide us with the following info:
  
  • Are there any error messages on the console?
  
  • Are you able to replicate the issue on other machines too? If yes, could you please share a gif of the steps involved so that we try exactly the same steps

  Regards

• 

  storm.binary

  • Post Options:
  • Link
    Copy

  Posted 23 December 2019, 5:42 pm EST - Updated 3 October 2022, 1:34 am EST

  Hi Sharad,
  
  Sorry for the delay in getting back to you.
  
  FF v71.0, win 10 x64, RAM 16GB, Core i7

  Thank you.

  PS. no idea if the gif got attached?
  
  So here it is uploaded:
  
  [url=https://ibb.co/crkx3tV]

  http://www.mediafire.com/view/v2bpyokbdfb2an2/SpreadJs_properties_page.gif

• 

  storm.binary

  • Post Options:
  • Link
    Copy

  Posted 11 January 2020, 5:06 pm EST

  Hello
  
  Any thoughts?

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 12 January 2020, 6:12 pm EST

  Hi,

  Sorry for the delayed response and thank you for providing the gif. However, I am still unable to replicate the issue even after following the same steps shown in the gif, further I have forwarded(SJS-2687) the issue to the dev team and shared the gif with the team too. I will let you about any updates I get from the dev team.
  
  In the meantime, could you please try the same on another machine and let us know if the issue is observed on any other machine too?

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 12 January 2020, 7:01 pm EST

  Hi Mehren,

  After multiple attempts, dev team is also unable to replicate the issue at their end. Could you please the dev console to see if any errors are thrown?

• 

  storm.binary

  • Post Options:
  • Link
    Copy

  Posted 16 January 2020, 4:19 am EST

  Hi Sharad,
  
  I suggest you look into the difference between loading div with class “slider-panel” in Chrome with that of Firefox (v.72.0). The slider panel is visible in the Chrome but not so in the FF. No console info in FF, the usual missing Jquery Map file, but in the Chrome, you get this:
  
  [Violation] ‘setTimeout’ handler took ms
  
  [Violation] ‘setTimeout’ handler took ms
  
  [Violation] ‘setTimeout’ handler took ms
  
  [Violation] ‘setTimeout’ handler took ms
  
  [Violation] ‘setTimeout’ handler took ms
  
  [Violation] ‘setTimeout’ handler took ms
  
  gc.spread.sheets.designer.min.js:334 [Violation] ‘setTimeout’ handler took 130ms
  
  gc.spread.sheets.designer.min.js:243 [Violation] ‘setTimeout’ handler took 91ms
  
  gc.spread.sheets.designer.min.js:243 [Violation] ‘setTimeout’ handler took 81ms
  
  gc.spread.sheets.designer.min.js:334 [Violation] ‘setTimeout’ handler took 105ms
  
  gc.spread.sheets.designer.min.js:243 [Violation] ‘setTimeout’ handler took 68ms
  
  gc.spread.sheets.designer.min.js:243 [Violation] ‘setTimeout’ handler took 60ms
  
  [Violation] Forced reflow while executing JavaScript took 77ms
  
  [Violation] Forced reflow while executing JavaScript took 63ms

  It all likely to be because of the way the side panel is loaded and displayed.
  
  Hoping this helps.
  
  M.

• 

  sharad.tomer

  

  • Post Options:
  • Link
    Copy

  Posted 16 January 2020, 7:32 pm EST

  Thank you for the additional info. I have shared the same with the dev team. I will let you know about any further updates.

  Regards