bug with the postback commands?

I've noticed a peculiar bug lately... Obviously I'm using Opera (7.23).

When I surf the NOOL-forums I open several threads (shift+ctrl+click) in the background. Then I read them one by one and close the pages as I read them.

Well, when I want to go to the second page in a thread I click on the "2" (and a doPostBack-function is executed). Mysteriously, I end up on the (closed) page I read previously (different thread). I'm wondering if the doPostBack-function gets confused with the thread IDs. Perhaps some ID has changed since I loaded the page?

If you want I can try to recreate the problem. Let me know what I should look for.

/TLV

You haven't seen the light yet, eh? Not using Opera? Don't worry, I'll keep on bugging you until you have 110% support for the browser...

Anyway, it seems like a reproduceable problem, and it has some "interesting" consequences. In Opera, I'm opening threads as tabs in the background. When I've read a page in a thread and want to go to another page in the same thread, I end up on the last opened thread (no matter if it's read or not).

Example: I opened page 2 of thread 14432 ("Which version of RIAD is this?"), and whenever I click on the "1" to get to the first page, I end up on the last opened thread. I've tried this by opening different threads while keeping thread 14432 open.

The command embedded under the hyperlink for the "1" is:

javascript:__doPostBack('dgList$_ctl1$_ctl0',')

No reference to the thread ID there, unless the command read the current URL.

Anyway, I don't know if this is fixable or not. If it is, great. If not, well, then my disgust for the Exploder browser and MS web-technology is increased (I actually like XP as an OS, it's just their browser that bugs me...)

/TLV

Coincidentally, the same thing is happening when I open threads in new windows with Exploder 6.0.

/TLV