This bug has been noticed by some users, but I've never been able to reproduce it.
I'm looking for someone to give me hints !

1) Do you reproduce this issue if you try same case on Demo ( http://projectorria.toolware.fr/demo ) ?

2) Do you reproduce this issue on another screen than WorkFlow ?

3) Could you try and "close" all status but one => how about workflow screen then ?
If it's OK, could you "re-open" (unclose) status one by one and test workflow each time => when doesn it get "wrong" ? (what status ? how many active status ?)

Thanks for your help.

How do i log on the demo ?

guest/guest or invité/invité

1)
2)
3) Doesn't change a thing

Tested on :

Google Chrome 17.0.963.66 m (W7)
Firefox 9.01 (W7)
Firefox 10.0.2 (W7)
Internet Explorer 8.0.6001 (WXP)

What OS ?

W7 => Windows7
WXP => WinXp

Could you send a print screen showing behaving with one only active status ?

Thanks.

I don't understand. I have only one status active in the print screens.

Or if you mean not having recording...qualifying etc... that's meaningless (i think) because i won't have the problem with one status because it will fit in one screen. So no scrollbar.

Yes,
My purpose is to test with 1 only status : there will be no scroll bar.
Then add status one by one and test.
I'd like to check wether the issue appears rights just when scroll bar is needed or depends on request size...

I don't understand how that works. I tried to create a new workflow and i can't delete objectifs from the workflow diagram. So how can i do it to have just one status ? How do you delete it ? I can't click them.

Just go to the Status screen (Parameters/Lists of values/Status).
Select each status but one, check the closed checkbox and save.

Thanks.

Ok i did that and have no scrollbar. I'm gonna try to "re-open" the status one by one now.

Whith Two statuts. No scrollbar.

OK.
Many thanks for all these tests.

This eliminates my fist intuition about request size.
What is really weird is that I could never reproduce the issue on same platforms (OS / Browser...)
I'll investigated about unclosed tags or specific request transformation (headers, additional data, ...) due to specific network.

Maybe I'll come back to you next for additional testing.

Thanks.

If you're using iframes (i didn't look into the code) with the scrolling attributes you may want to look if you don't have any "overflow" from the css that are colliding with it. I had a similar issue not so long ago but can't quite remember what caused it.

Oh and i don't think navigators change with x86 or x64 but both my computer are 64bits.

No, there is no iFrame involded here.

As you reproduce the issue and I don't using :
- Same OS
- Same browsers (and several tested)
- Same instance : http://projectorria.toolware.fr/demo
I guess some network influence is in cause.

Do you reproduce the issue on an enterprise network, on a private network or anywhere ?
Do you use a proxy ?

I use proxy. Enterprise network. I have acces to another computer outside the network. Want me to try it ?

YES PLEASE !

Tested on W7 Google Chrome at my house. Same thing

Could you pease execute this test :

Modifiy /view/js/projector.js and add after lines 412 and 493 the line :

if (page.substr(0,16)=='objectDetail.php') {console.log(data);}

These lines should then look like

      load: function(data,args){
if (page.substr(0,16)=='objectDetail.php') {console.log(data);}
        // update the destination when ajax request is received

Then open a brower with console (Chrome or Firefox with firebug), be sure to refresh the cache (F5) and run the test (display workflow detail).

A large message should appear in the console.
Copy it and paste it here or send it to me.

Many thanks in advance.

An issue has been fixed for V2.1 or bad tag closure.
It could slve this kind of issue.
(not sure as I never could reproduced the issue, and so cannot test the fixing )

Thank you i could not test the code (cause too much work elsewhere).

I finaly could reproduce the issue.
I found the reproduction case.
It will be fixed in V2.1.1

A workaround is simple :
- go to "User parameters"
- in Display History, select 'Yes"
- save parameters
- test again : it's magic !