ZK7 / Window Scroll Position Lost when update a record

Description

Use case: user wants to update product - group field which is on the bottom of the window. open the product scroll down to group field - update it, then save. user wants to continue update another field at the bottom or just review - group field was saved. then user must scroll down again.

IMHO: this behaviour is annoying

remark: i discover it when test ZK7 but same behaviour in idempiere 2.0 with zk6x. also true for other windows like sale order.

see attached screens.

i suggest it fix for version 2.1 and 3.0 both zk6, zk7

Environment

None

Attachments

3
  • 09 May 2020, 03:56 PM
  • 02 Nov 2014, 10:20 AM
  • 02 Nov 2014, 10:20 AM

Activity

Show:

Carlos Ruiz March 8, 2022 at 3:14 PM

This is a potential improvement - what I see is normal behavior,

In some cases is possible that the user want to navigate to the focus field, in other cases (f.e. massive changes) is possible that the user wants the cursor to stay in the last field edited.

As it can be different per-case, I would suggest to implement it as a user preference.

Murilo Habermann Torquato May 9, 2020 at 3:56 PM

Triaged by

This is still happening in current version.

Looking into the source code, i think that this is an (annoying)
expected behaviour in due to the focus policies that are being applied after triggering toolbar events:

 

Maybe a possible solution is apply the focus policies just on some actions:

  • On window/tab open

  • On New, Save & New, Requerey and when returning from Find window

To make this more flexible and don affect users maybe this can be defined as a User Preference (like auto commit)

Hiep Lq January 21, 2015 at 6:23 AM

not only save action. it's in navigate action, active tab action.
will proceduce at clear zk project to detect root cause.

Norbert Bede January 21, 2015 at 6:16 AM

tested in 3.0.0.v20150114-2331
still pending.

Incomplete

Details

Assignee

Reporter

Components

Priority

Created November 2, 2014 at 10:20 AM
Updated May 1, 2022 at 1:50 PM
Resolved March 8, 2022 at 3:14 PM