Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
Hi,
How to reproduce:
1. Take for example https://demo.projeqtor.org/view/main.php
2. Go to activities (there are a lot of activities)
3. Go to the last item
4. Change something and save.
5. List area is refreshed, the right item is underlined in list area, the right item is seen in detail area BUT in list area, the underlined item is not in the scope of what you can see, you have to use the scrollbar to find where the item was (in this case, it's easy because it's the last item, but not in a middle of a long list).
(tested in IE and Firefox)
When dealing with a large amount of items, this is really annoying as you lost your progress in a long list of items each time you save an element and you want to move on to next item…
Good luck, I know it won't be easy to fix this bug!
Hi,
Weird indeed.
It seems on long lists, the positionning occurs slightly before expected position.
It also seems that if you don't display photos in list (it's a user parameter) the gap is less important...
Ticlet #1949 recorded
Maybe it's because it's positioning before the browser load all images and stuff.
Some solutions I can think about:
1. Fixed height for row. This seems to me the best solution so if images are not loaded, there is enough space to load them. However, if a cell has multiple lines, it may be cut. And… if you use min-height instead, the positioning might be impacted again.
2. Use an anchor #myid1234 so the browser go by itself at the right anchor. May not work, I don't know how browser would react but I know that sometimes Firefox has a 15-years old bug about this: https://bugzilla.mozilla.org/show_bug.cgi?id=60307
Thnaks for the ideas.
1) fixed lentgh : I thing it's the best way (or at least the less worst !)
2) Anchor : I'll have a look but the Grid uses lazy loading, so the anchor may not be rendered.
I saw that this bug was moved to 5.5.0 target version which delays the fix a lot, was the first solution too difficult to implement?
If not, would you like that I take a look at it?
Did not have time to analyse this issue.
But it id minor and fixing can be a real mess.
Don't hesitate to have a look if you have the opportunity.
We'll be glad to include fixing in next version or patch if you find some.
Thanks