Issue 28351

Summary:	Accept or Reject Changes: Formats cannot be rejected
Product:	General	Reporter:	auberger <r.auberger>
Component:	ui	Assignee:	AOO issues mailing list <issues>
Status:	CONFIRMED ---	QA Contact:
Severity:	Trivial
Priority:	P3	CC:	cmoulin, issues, mhillat, robert.funnell
Version:	OOo 1.1.1
Target Milestone:	---
Hardware:	All
OS:	Linux, all
Issue Type:	ENHANCEMENT	Latest Confirmation in:	---
Developer Difficulty:	---

Description auberger 2004-04-25 15:13:45 UTC

When working with recorded changes (menu Edit - Changes - Accept or Reject) you
cannot reject "Formats" changes. Selecting a Formats-change  (e.g making some
text bold) together with other changes (e.g. Insertion) you can click "Reject"
-> the Formats change is removed from the list and the colored highlighting is
removed also but the change is still present (=text is still bold). The same
happens when clicking "Reject all": the list is cleared, all colored highlights
in the text are removed but the formatting isn't changed back.

Tracking changes of formats doesn't make sense if you can only accept them and
if they aren't reverted when rejected.

Comment 1 thorsten.martens 2004-04-27 08:39:37 UTC

TM->HI: Not a framework issue. Please have a look.

Comment 2 joeclarkia 2004-07-29 05:16:24 UTC

I've seen the same problem in 1.9.m47.  I can change a format parameter (font
size, text color, etc), and it shows up as a change, but if I select that change
in the dialog box, the "Reject" button is grayed out.  I agree with the
originator that tracking format changes is not very useful if they can't be
rejected.

Comment 3 michael.ruess 2004-08-19 14:19:35 UTC

A good thing for the next redlining changes in OO 3.0. As long as the big
competitor does allow this, we should also do...

Comment 4 joeclarkia 2005-04-27 05:44:46 UTC

still broke in 1.9.84

Comment 5 robertf 2010-02-21 14:58:17 UTC

This problem is still present in version 3.2.0.

auberger and joeclarkia said that tracking format changes is not very useful if
they can't be rejected. I hope that nobody takes this to mean that it would be
better not to track format changes. It is good to be able to see what format
changes have been made, although of course it would be _very_ good to also be
able to undo them.

Shortly after this issue was first reported, tm said that it was not a framework
issue, but it is still labelled that way. I don't understand the system enough
to know what component it should be, nor whether it matters.

Does anyone know whether this would actually be a difficult thing to fix?

Comment 6 bettina.haberer 2010-05-21 14:59:14 UTC

To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".

Comment 7 eric.savary 2010-10-28 04:45:53 UTC

*** Issue 115277 has been marked as a duplicate of this issue. ***

Comment 8 camillem 2011-06-27 15:50:29 UTC