You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2014/05/22 18:10:04 UTC
[Issue 124959] New: Table: Selection inconsistence for merged cells
https://issues.apache.org/ooo/show_bug.cgi?id=124959
Issue ID: 124959
Issue Type: DEFECT
Summary: Table: Selection inconsistence for merged cells
Product: Writer
Version: OOo 3.4 Beta
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: editing
Assignee: issues@openoffice.apache.org
Reporter: rainerbielefeld_ooo_qa@bielefeldundbuss.de
Created attachment 83449
--> https://issues.apache.org/ooo/attachment.cgi?id=83449&action=edit
Sample Document with instruction
You will find steps how to reproduce with "AOO 4.0.1 – German UI / German
locale [AOO401m3(Build:9712) - Rev. 1520285 2013-09-05 13:52:01]" on German
WIN7 Home Premium (64bit)", Common 4.0 User Profile
in attachment
Additional Info:
----------------
(a) For selection vertically merged cells are handled as the most top former
cell.
That causes strange unintuitive effects as described in "Issue 118681 -
selecting whole table with merged cells not possible"
(b) For selection of horizontally merged cells are handled as the most distant
from selection start point former cell
(c) Kingsoft Writer makes the same difference between horizontally and
vertically
merged cells.
(d) Softmaker FreeOffice Writer does selection with merged cells always as
I would expect: Maximum selection for area covered by merged cells.
--
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.
[Issue 124959] Table: Selection inconsistence for merged cells
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124959
Rainer Bielefeld <ra...@bielefeldundbuss.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://issues.apache.org/o
| |oo/show_bug.cgi?id=118681
--
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.