Description: I exported a table sheet with Libreoffice Calc in HTML using the File->export menu. In the HTML file, I found not valid style value : .ce2 { font-family:Liberation Sans; border-width:NaNcm; border-style:solid; border-color:#000000; } There is a NaN here. The with of the cell border is the default one in Calc (so 0,05 pt) My config : Debian testing Version: 6.1.5.2 Build ID: 1:6.1.5-1 Threads CPU : 4; OS : Linux 4.19; UI Render : par défaut; VCL: gtk3; Locale : fr-BE (fr_BE.utf8); Calc: group threaded Steps to Reproduce: 1. Open calc 2. Add cell borders using the icon tool (black border on all cells selected) 3. Export to HTML 4. look at the HTML code and search for "NaN" Actual Results: I found this in the HTML file: .ce2 { font-family:Liberation Sans; border-width:NaNcm; border-style:solid; border-color:#000000; } Expected Results: I should have get : .ce2 { font-family:Liberation Sans; border-width:0.05pt; border-style:solid; border-color:#000000; } Reproducible: Always User Profile Reset: No Additional Info: My config : Debian testing Version: 6.1.5.2 Build ID: 1:6.1.5-1 Threads CPU : 4; OS : Linux 4.19; UI Render : par défaut; VCL: gtk3; Locale : fr-BE (fr_BE.utf8); Calc: group threaded
Created attachment 150272 [details] test case
--- Comment #2 from mulla.tasanim at gmail.com --- Thank you for reporting the bug. I can not reproduce the bug in Version: 6.2.1.2 (x64) Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL Version: 6.3.0.0.alpha0+ (x64) Build ID: 91cdf22b88a4f7bec243c8fb187627e766d3294c CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86_64 at 42, Branch:master, Time: 2019-03-08_00:38:10 Locale: en-US (en_US); UI-Language: en-US Calc: CL Here is what I am finding when I am opening HTML file in both versions- .ce2 { font-family:Liberation Sans; border-width:0.0133cm; border-style:solid; border-color:#000000; } Comment lost during the BZ outage -> https://lists.freedesktop.org/archives/libreoffice-bugs/2019-March/176601.html
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Tuxicoman, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Tuxicoman, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, 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 LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp