Bug 121071 - FORMATTING - Double Table Borders When Copied from Calc and Pasted in Gmail
Summary: FORMATTING - Double Table Borders When Copied from Calc and Pasted in Gmail
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.2.1 release
Hardware: x86-64 (AMD64) All
: lowest trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Cell-Border
  Show dependency treegraph
 
Reported: 2018-10-31 02:59 UTC by James A
Modified: 2025-01-15 05:31 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Visual of a problem (5.76 KB, image/png)
2018-10-31 03:03 UTC, James A
Details

Note You need to log in before you can comment on or make changes to this bug.
Description James A 2018-10-31 02:59:27 UTC
Description:
Copying and pasting cells in gmail corrupts table border formatting. Problem didn't exist in Excel.

Steps to Reproduce:
1.Format a cells with both outer and inner borders
2.Copy formatted cells
3.Paste in gmail

Actual Results:
Inner lines of a table appear thicker compared to outside. Looks like double cell borders

Expected Results:
All tables borders should be the same thickness


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Comment 1 James A 2018-10-31 03:03:08 UTC
Created attachment 146183 [details]
Visual of a problem
Comment 2 Joel Madero 2018-11-20 11:54:28 UTC
Linux Mint 19
Version: 6.2.0.0.alpha1+
Build ID: 1647bc1309dcd313dff2614f4844b71b1c558dee
CPU threads: 2; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); Calc: threaded

Confirmed but super minor issue.

James:
You can do additional work to help resolve this problem. First and foremost, you could check against LibreOffice 3.3 to see if this is a regression or if it was inherited from OOo. If it's a regression, there are additional steps we can do to help triage the problem for a developer.

https://downloadarchive.documentfoundation.org/libreoffice/old/
Comment 3 QA Administrators 2020-12-27 03:37:23 UTC Comment hidden (obsolete)
Comment 4 Roman Kuznetsov 2021-01-14 07:42:08 UTC
still repro in

Version: 7.2.0.0.alpha0+ (x64)
Build ID: 94f6765d6ecc3145fa2d266231124003cf953118
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded

but I don't think it's a bug. Excel creates cell borders by different logic. It has only one border for two adjacent cells. 

And my opinion here it will never "fix" in LibreOffice.

Mike, do you have any thoughts?
Comment 5 James A 2021-01-14 23:13:10 UTC
(In reply to Roman Kuznetsov from comment #4)
> still repro in
> 
> Version: 7.2.0.0.alpha0+ (x64)
> Build ID: 94f6765d6ecc3145fa2d266231124003cf953118
> CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL:
> win
> Locale: ru-RU (ru_RU); UI: en-US
> Calc: threaded
> 
> but I don't think it's a bug. Excel creates cell borders by different logic.
> It has only one border for two adjacent cells. 
> 
> And my opinion here it will never "fix" in LibreOffice.
> 
> Mike, do you have any thoughts?

I agree that it's a minor bug for most. But, it is critical for some. Our company's entire sales process is based on copying price quotes from spreadsheets and sending over email. So, this issue basically prevents us from using the software and forces us to stick with MS products for time being.
Comment 6 QA Administrators 2023-01-15 03:23:15 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2025-01-15 03:12:19 UTC Comment hidden (obsolete)
Comment 8 Mike Kaganski 2025-01-15 05:31:26 UTC
(In reply to James A from comment #5)
> Our company's entire sales process is based on copying price quotes from
> spreadsheets and sending over email. So, this issue basically prevents us
> from using the software and forces us to stick with MS products for time
> being.

Any entity that intends to benefit from using the free and open source software, is welcome to contribute and improve it, for benefit of themselves and everyone - e.g.:

* by hiring a developer to fix problems, and sending the patches to the project;
* by contracting a certified professional [1] for that;
* by using one of the commercial ecosystem partners' product, which are paid (for much less cost than in non-open-source competition), and which cost allows to pay developers who improve the product.

The things like "this is an issue preventing us from using this product" is off-topic here in the bug tracker.

[1] https://www.libreoffice.org/get-help/professional-support/