Bug 89595 - TOC: Rulers go full width of view area when cursor in Table of Contents
Summary: TOC: Rulers go full width of view area when cursor in Table of Contents
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: TableofContents-Indexes Rulers
  Show dependency treegraph
 
Reported: 2015-02-23 19:18 UTC by Yousuf Philips (jay) (retired)
Modified: 2022-11-14 03:32 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
screenshot (79.92 KB, image/png)
2015-02-23 19:18 UTC, Yousuf Philips (jay) (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2015-02-23 19:18:01 UTC
Created attachment 113628 [details]
screenshot

If you open a document with a table of contents and you click within its area while the TOC is in protected mode, the rulers will stretch the full width of the view area. This doesnt happen if the TOC is in non protected mode.

Version: 4.5.0.0.alpha0+
Build ID: 4cf69df2f543b023f4ec3d4279c5ac11a2a819d9
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2015-02-21_03:46:34
Comment 1 A (Andy) 2015-02-24 19:14:10 UTC
Reproducible with LO 4.4.0.3, Win 8.1
Comment 2 tommy27 2016-04-16 07:28:40 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2017-05-22 13:26:52 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2019-12-03 14:33:04 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2020-11-13 16:58:38 UTC
Still repro

Arch Linux 64-bit
Version: 7.1.0.0.alpha1+
Build ID: c54e1c22f30c23d00e2fe7521217569fcec59cc4
CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 13 November 2020
Comment 6 QA Administrators 2022-11-14 03:32:47 UTC
Dear Yousuf Philips (jay) (retired),

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug