Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Validity Input Help will have vanished after scroll out of sight and back | ||||||
---|---|---|---|---|---|---|---|
Product: | Calc | Reporter: | Rainer Bielefeld <rainerbielefeld_ooo_qa> | ||||
Component: | viewing | Assignee: | AOO issues mailing list <issues> | ||||
Status: | UNCONFIRMED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P5 (lowest) | CC: | elish, rainerbielefeld_ooo_qa | ||||
Version: | 3.3.0 or older (OOo) | Keywords: | needhelp | ||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | Windows 7 | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
Rainer Bielefeld
2014-04-06 09:00:00 UTC
A tool tip is not supposed to be sticky. Behavior is consistent with comment appearance. (In reply to Edwin Sharp from comment #1) > A tool tip is not supposed to be sticky. > Behavior is consistent with comment appearance. You are wrong. Input help is an aid for the user for filling the specific validity cell. User scrolled from cell -> user doesn't want to fill the cell, why still display input help? If comments are supposed to be always on - why option "show comment" ? Created attachment 83233 [details] Sample Document Reasoning in Comment 1 is wrong. A Tooltip is a mousover effect what disappears "by definition" if the cell with comment becomes moved out of visible area. But Validity input help visibility is related to cell cursor position. Assumption of users' intentions and needs in Comment 3 seems a stretch to me. If user scrolls to cell AF100, does that mean that he is not interested in contents of A1, so that there is no need to show contents of A1 again when he has scrolled back? Attachment shows a real life situation where it is unexpected that Validity help disappears I am not happy with the current Validity Help, my opinion is that it is too persisting and covers cells in the neighborhood even if it no Help is required. So it might be inexpedient to start a fix here before we have a complete overview how an optimal Validity help should work. I have an Enhancement Request in my to-do list. But such a decision should base an knowledge and careful weighing, not on unknowingness and wrong comparison There are workarounds to the given example. The detailed explication can be incorporated into validity input help. The detailed explication can be located in frozen cells not affected by scrolling. A valid bug can be issued against: a. previous versions behavior b. specification defining a different behavior c. help describing a different behavior d. other spreadsheet programs with different behavior A valid bug report can not be issued based on subjective expectation. For me the validity input help is a nuisance the moment I finished reading it. Keywords=needhelp for more thoughts |