| Summary: | do not focus on the summary field when moving between editors | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Jakub Jurkiewicz <jakub.jurkiewicz> | ||||||||||||||
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> | ||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||||||
| Severity: | minor | ||||||||||||||||
| Priority: | P2 | CC: | mik.kersten | ||||||||||||||
| Version: | unspecified | ||||||||||||||||
| Target Milestone: | 3.2 | ||||||||||||||||
| Hardware: | PC | ||||||||||||||||
| OS: | Windows XP | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Bug Depends on: | 262510 | ||||||||||||||||
| Bug Blocks: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Jakub Jurkiewicz
Created attachment 92094 [details]
possible Fix
I think that can fix this for the following Controls.
estimated, issueReportURL, Summary and Note
What do you think?
Created attachment 92095 [details]
mylyn/context/zip
Thanks Frank. I have implemented it in a similar way as suggested by your patch. Essentially any control that can accept focus gets a focus listener that remembers the last control that had focus for the next activation of the page. Created attachment 97911 [details]
mylyn/context/zip
Created attachment 98118 [details]
mylyn/context/zip
Reopening to address a regression that is causing the task editor to change the scroll position when it gets the focus. Created attachment 104797 [details]
patch to disable focus tracking
Created attachment 104800 [details]
patch
I have committed this patch. The behavior is now the following: - the form toolkit does not track focus, i.e. not "automatic" scrolling - when text is typed into a text field the form scrolls to the that text field - when the form gains focus it will restore the focus to the control that had it last Restoring focus will fail in certain cases, e.g. when controls are lazily constructed. I am deferring further tweaks to the next milestone. Further improvements will be tracked on bug 236084. |