Bug 40587 - UI Tabs stops do not line up in ruler
Summary: UI Tabs stops do not line up in ruler
Status: RESOLVED DUPLICATE of bug 38341
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: x86 (IA32) macOS (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-02 11:34 UTC by digital ant
Modified: 2012-03-02 05:26 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description digital ant 2011-09-02 11:34:44 UTC
This should be an easy hack - functionality does not seem to be effected.

Steps:

Clean install of 3.4.3 on OSX
Open Writer
Look at visible tab stops across the top
Tab across page - where the cursor stops is not actually where the tab stops are

I Opened Preferences/LibO Writer/General and saw the tab stops were set to 0.49" - changed to 0.5"

Closed and re-opened writer - first tab stop is at 0.5, but all after that are off - BUT when tabbing across page, cursor stops every 0.5"

If I create a new tab stop, it is created in the correct position and cursor matches - only default stops in new docs seem to be off.
Comment 1 Björn Michaelsen 2011-12-23 12:41:37 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 2 sasha.libreoffice 2012-03-02 05:26:19 UTC

*** This bug has been marked as a duplicate of bug 38341 ***