The javascript change did not solve the problem.
I just confirmed what I had thought though. The problem is that every
web client enters the status.html args;
p0=playlist&p1=jump%p2=%2b1%player=... when you hit next.
Then they refresh to; start=0&refresh=1&player=... just like
status.html tells it to.
Except IE on Windows Mobile refreshes to the first URL.
I can confirm this was not broken in 5.6. I don't remember if it was
in 6.0 or not, but it was in 6.1.1.
So.. whatever the change in refreshing that occurred somewhere in
there is what is causing the problem.
I imagine the code at fault is in Internet Explorer, but it's easier
to code around it than get them to fix it ;-).
Let me know if I can test anything else.
-- Mike
Michael Herger wrote:
Mike
This is running on an HP iPAQ with Windows Mobile 2003 Second Edition
using Internet Explorer.
I still don't have a PocketPC to test with :-/.
When on the status screen I click the next button and the song
advances, but when it refreshes the next time I get a 403 Forbidden.
Changing the CSRF Protection Level to None solves this but introduces
another problem.
The next time it refreshes it works fine, but the following time and
every time after that it automatically hits next.
I can't reproduce this. Neither the CSRF problem nor the automatic
skip. But there was some redundant code in the HTML which might have
caused problems (redirect using both the meta tag and javascript). I
checked in a change for this to subversion. It should be in the 20/10
nightly. Please report back if this fixes your problem.
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
