Bug 119456 - Right border of embedded table in webview not properly drawn with sidebar active depending on zoomlevel (and screen resolution)
Summary: Right border of embedded table in webview not properly drawn with sidebar act...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.5.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Table-Borders Writer-Tables-Nested
  Show dependency treegraph
 
Reported: 2018-08-23 16:02 UTC by Telesto
Modified: 2020-04-02 03:35 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot (42.87 KB, image/png)
2018-08-23 16:03 UTC, Telesto
Details
Bibisect log (2.91 KB, text/plain)
2018-08-23 16:06 UTC, Telesto
Details
Example file (8.34 KB, application/vnd.oasis.opendocument.text)
2018-09-18 18:29 UTC, Buovjaga
Details
Screencast (580.11 KB, video/mp4)
2018-09-19 18:05 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2018-08-23 16:02:44 UTC
Description:
Right border of embedded table in webview not properly drawn with sidebar active depending on zoomlevel (and screen resolution)

Steps to Reproduce:
1. Open Writer
2. Open sidebar with properties view
3. Insert a table (2x2)
4. Insert a table in A2 (2x2)
5. Zoomlevel 140%
6. Document screen filling
7. Go to webview

Actual Results:
Missing right border (see screenshot)

Expected Results:
Should be visible


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.2.0.0.alpha0+
Build ID: 414ef6cb187dd3bbcc917dbedf3c0c1cc8668f60
CPU threads: 4; OS: Windows 6.3; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-08-20_22:43:18
Locale: nl-NL (nl_NL); Calc: CL
Comment 1 Telesto 2018-08-23 16:03:10 UTC
Created attachment 144397 [details]
Screenshot
Comment 2 Telesto 2018-08-23 16:06:30 UTC
Created attachment 144398 [details]
Bibisect log

Issue appeared after

author	Caolán McNamara <caolanm@redhat.com>	2017-09-28 11:36:15 +0100
committer	Caolán McNamara <caolanm@redhat.com>	2017-09-28 13:03:59 +0200
commit e302ade40e202d285e2208fb6190850e126b4eae (patch)
tree 7e28dfcd6b1873dda205b1963738e70dd5743230
parent 0f6b9eca2007629e61d3ab9cdf2a616a33cbdefe (diff)
Related: tdf#109385 make default panel width wider

https://cgit.freedesktop.org/libreoffice/core/commit/?id=e302ade40e202d285e2208fb6190850e126b4eae

It's also reproducible with the same sidebar width in older versions (found in in 5.2)

but not in
Version: 4.5.0.0.alpha0+
Build ID: 9b4abcd1c45a646a1ac9120fe1c489ba6bb44e95
Locale: nl_NL
Comment 3 Buovjaga 2018-09-18 18:29:46 UTC
Created attachment 144993 [details]
Example file

No repro.

Version: 6.2.0.0.alpha0+ (x64)
Build ID: 18c5089df091bddeb8c2dc339776671964389040
CPU threads: 4; OS: Windows 10.0; UI render: default; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-09-12_23:24:12
Locale: fi-FI (fi_FI); Calc: threaded

Version: 6.1.0.3 (x64)
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
CPU threads: 4; OS: Windows 10.0; UI render: default; 
Locale: fi-FI (fi_FI); Calc: group threaded
Comment 4 Telesto 2018-09-19 18:05:41 UTC
Created attachment 145042 [details]
Screencast

I can't repro it with the sample file (or after saving & reloading)
Comment 5 Buovjaga 2018-09-19 18:09:23 UTC
(In reply to Telesto from comment #4)
> Created attachment 145042 [details]
> Screencast
> 
> I can't repro it with the sample file (or after saving & reloading)

Not from scratch either anymore?
Comment 6 Telesto 2018-09-19 18:15:40 UTC
Yes, still happening as shown in the screencast. But might be combination of screen resolution/dpi and zoomfactor
Comment 7 Chiang Han 2018-11-29 08:04:45 UTC
Bug not reproducible in version

I follow all the steps,but this problem didn't occur in this Version.

Version: 6.3.0.0.alpha0+ (x64)
Build ID: 0f25a3c36f27fd51453b9a9115f236b83c143684
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-27_20:06:55
Locale: zh-TW (zh_TW); UI-Language: en-US
Comment 8 Xisco Faulí 2019-01-23 13:05:55 UTC
Not reproducible in

Version: 6.3.0.0.alpha0+
Build ID: 8f7c35072a6bbb33f6582c8c9a37a275c8d3cb14
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

@Telesto, still reproducible in master ?
Comment 9 Telesto 2019-01-23 19:21:21 UTC
Still around
Version: 6.3.0.0.alpha0+
Build ID: 6740443311268b7d918bf4f43134d64fb78a0109
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-01-15_23:37:04
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 10 Xisco Faulí 2019-07-31 11:37:06 UTC
Hi Telesto,
No one has been able to reproduce this issue since you reported it. Is this issue still reproducible in master? any chance you can reproduce it with another computer just to double check ?
Comment 11 Xisco Faulí 2019-09-03 08:20:07 UTC
(In reply to Xisco Faulí from comment #10)
> Hi Telesto,
> No one has been able to reproduce this issue since you reported it. Is this
> issue still reproducible in master? any chance you can reproduce it with
> another computer just to double check ?

setting to NEEDINFO
Comment 12 QA Administrators 2020-03-02 02:47:39 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2020-04-02 03:35:11 UTC
Dear Telesto,

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