noushadali / openhab

Automatically exported from code.google.com/p/openhab
GNU General Public License v3.0
0 stars 0 forks source link

HABDroid: Page jump when values are changed #193

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
1. Description
When values change, eg. lamp changes from OFF to ON, thermostat reports new 
value etc., and user navigates on web app or android app the current page jumps 
to top and user has to scroll back to original view.

2. Example Use Case
 - Define page in setup with enough items to fill the screen vertically
 - open page in web app
 - change single item state via console
 - page on client jumps to top

Original issue reported on code.google.com by hlw31...@gmail.com on 27 Jan 2013 at 10:52

GoogleCodeExporter commented 9 years ago
I originally created this as a bug. May someone please fix this and the error 
itself?
Thanks :)

Original comment by hlw31...@gmail.com on 30 Jan 2013 at 7:32

GoogleCodeExporter commented 9 years ago
Changing it to a bug was easy - fixing it won't be... The point is that the 
page is reloaded on item updates, and the browsers behave differently - mobile 
Safari on the iPhone actually works fine, while PC browers show the problem you 
describe. I don't see a way how to fix this - so I would opt to close this 
issue as "won't fix", if you agree.

Original comment by kai.openhab on 30 Jan 2013 at 11:21

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I'm fine with this. However, fixing this in the specific apps (WP8, Android, 
iPhone) should be possible and would be a great step for UX.

So the current work around is to keep pages from filling more than the screen.

You may of course close this as "won't fix".

Original comment by hlw31...@gmail.com on 31 Jan 2013 at 11:41

GoogleCodeExporter commented 9 years ago
Hm, I assumed, you were only talking about the Classic UI. Can you confirm that 
the same problem exists for the native apps? If yes, we could check if it can 
be adressed in them.

Original comment by kai.openhab on 31 Jan 2013 at 9:15

GoogleCodeExporter commented 9 years ago
I can confirm that this problem exists for HABDroid for the current release. I 
have an older Version of HABDroid on my Tablet, where the problem does not 
exist.

Original comment by TBraeuti...@gmail.com on 1 Feb 2013 at 9:11

GoogleCodeExporter commented 9 years ago
Victor, can you look into that? If it once worked, it should hopefully possible 
to fix it for HABDroid.

Original comment by kai.openhab on 1 Feb 2013 at 9:17

GoogleCodeExporter commented 9 years ago
I can't reproduce this with current build :-/

Original comment by belovic...@gmail.com on 9 Feb 2013 at 7:32

GoogleCodeExporter commented 9 years ago
Thanks to Victor, I just tested his current build and it's perfectly fine.

Original comment by hlw31...@gmail.com on 9 Feb 2013 at 8:47

GoogleCodeExporter commented 9 years ago
Great, so I will close the issue as it is fixed for HABDroid and won't be 
possible to change on the Classic UI.
If you feel that it should be addressed in any other UI, you might want to open 
another dedicated issue.

Original comment by kai.openhab on 9 Feb 2013 at 8:49

GoogleCodeExporter commented 9 years ago

Original comment by kai.openhab on 9 Feb 2013 at 8:50