Bug 35588 - User-facing Style 'names' used to identify Styles internally
Summary: User-facing Style 'names' used to identify Styles internally
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 3.3.1 release
Hardware: All Linux (All)
: lowest minor
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-23 03:33 UTC by doubiman
Modified: 2015-01-21 08:44 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description doubiman 2011-03-23 03:33:46 UTC
This leads to the following problem:

1. Assign a Style to a (unused/non-default) key combination, e.g. Alt+Shift+L
2. Test
  -> Can apply Style fine
2. Change name of Style in Styles dialogue.
3. Try to apply Style with shortcut.
  -> Nothing happens.

I can see in the Customize Keyboard dialogue that the Style 'name' that the user sees is used in the Uno code to identify the Style.

This leads to a similar problem when linking Numbering Styles to Paragraph Styles:

1. Define Numbering Style.
2. Assign Numbering Style to a Paragraph Style.
3. Test
  -> Should apply Paragraph Style with appropriate numbering.
4. Change name of Numbering Style.
5. Test applying Paragraph Style from before
  -> Numbering doesn't work.

However, I have noticed that if one applies a Character Style within a Numbering Style, and then changes the name of the Character Style, it /is/ updated and still works in the Number Style.

This suggests that there is some internal unique identifier by which Styles can be referenced and which would solve the problem of 'broken links' to Styles when the user changes their visible name.

If I'm wrong on this last point, I would submit that there should be such an internal, immutable identifier.
Comment 1 Björn Michaelsen 2011-12-23 11:43:18 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 Florian Reisinger 2012-08-14 13:57:31 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 3 Florian Reisinger 2012-08-14 13:58:51 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 4 Florian Reisinger 2012-08-14 14:03:24 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:05:39 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 sasha.libreoffice 2012-08-30 09:23:21 UTC
reproduced in 3.6.1 on Fedora 64 bit
after renaming style shortcut becomes not working
I do not know if it is a bug or so should be
Comment 7 Joel Madero 2012-10-19 20:41:16 UTC
This is definitely a bug, although a minor one. Marking as such.

Confirmed: 3.6.1.2 
Distro: Bodhi

Minor -- makes creating professional quality work under very specific situations slightly more difficult

Lowest -- Easy work around (reassign key), and only happens if someone renames the style (not too common at all)
Comment 8 QA Administrators 2015-01-05 17:51:06 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

Thank you for your help!

-- The LibreOffice QA Team
Comment 9 Beluga 2015-01-21 08:44:32 UTC
Still reproduced.

Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+
Build ID: 07e84cae983c08afdba03018413a19d01abb3006
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-19_06:15:38


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.