Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Comment hides Index Entry Field | ||
---|---|---|---|
Product: | Writer | Reporter: | Rainer Bielefeld <rainerbielefeld_ooo_qa> |
Component: | viewing | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Minor | ||
Priority: | P4 | CC: | elish, rainerbielefeld_ooo_qa |
Version: | 3.3.0 or older (OOo) | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | 4.1.0-dev |
Developer Difficulty: | --- |
Description
Rainer Bielefeld
2014-04-22 05:22:20 UTC
(e) Cross References are not affected (f) I did not check similar fields systematically. Confirmed with AOO420m1(Build:9800) - Rev. 1586681 2014-04-15_04:11:11 - Rev. 1587398 Debian This isn't a real bug. Problem: You inserted an entry for an index and a comment at the same position. What should appear? Both are nonprinting fields that must not consume any space. So the grey field for the index entry is overlayed by the colourless "field" for the comment. Try the following: 1. place the cursor in the empty paragraph before 2. press key cursor right → the cursor stands in the comment (line changed) 3. press key cursor right → the cursor stands between the comment (line changed) and the index entry 4. press key cursor right → the cursor stands behind the index entry but it is not visible 5. press key cursor right → the cursor stands after the first character You can change it: 1. delete the comment 2. select the grey index entry 3. insert a comment. Now the index entry stays visible. (In reply to Rainer Bielefeld from comment #0) > (b) With current AOO I can't find any reason to hide the Index Entry I agree, because the Tooltip for the entry is also not available. (But I don't know what should appear, if more fields are laying at the same position about each other?) (In reply to mroe from comment #3) You are right, it's a matter of workflow whether the index entry will become invisible or not, workaround is easy. e): wrong observation, with particular order of inserting and/or particular caret position for input of comment cross reference field will become invisible. But like mroe I still think that is an unnecessary complication for users, it should be possible to create some more clever code. But a really unimportant enhancement. |