I have the small Ajax thingy always closed... But it shows a minus sign at the first page loading...
If I open the ajax and close it back again, it fixes it into a + sign.

Look at the screenshot:


-Avi

btw, IE7-32bits on Vista x64.

good catch.. happens to me also.. ff3 on vista64
not a pressing issue, but definitely a (small) bug!

Works fine for me

Firefox 2.0.0.12, XP home.

Maybe it only shows on IE7? Can you check it?

Works fine for me using the latest WebKit nightly.

Well, can anyone w/ IE7 verify this? It's really not a complicated bug to check, lol. Just close the ajax thingy, restart browser, enter "neowin.net" in the address bar, and check if you see a minus sign when the ajax box is closed (at the first page loading, of course).

yeh mines a minus on restart of IE7pro

It's a minus here on my pc. Maxthon Classic/IE7


Edit : Thats because it was open. I click it and the recents disappear, and it becomes a +
Working fine here.

Well, after you close it it DOES show a plus. But then, keep it closed. Restart browser. Navigate to Neowin.net. On the first time the page loads, it will be automatically closed (as it should be, cuz you closed it last time)... but will show a minus sign instead of a +.

Yep, just double checked - that's right.

BUT!!!!!
When I closed it and reopened, INITIALLY it was a plus, THEN it changed to a minus. (But the recents were still "closed" - they didn't change at all)
Clicking on the minus at that stage opened the recents - and of course, the symbol didn't change (still a minus!)

Weird!

Yeah, same here. While the page is loading, there is a plus sign (which is correct, cuz the ajax box is closed). But when it finishes loading, it turns into a minus.

It should be noted that this problem does NOT occur in the Forums (neowin.net/forum/)!

No Neowin coders wanna look at this? I'm sure you'll fix it in 5 minutes.

And so they will. It's not impeding your browsing, is it?

Believe it or not, I had to look up the word "impeding"... (English is not my native language)

No, it's not "impeding" my browsing, of course. But it's one of those bugs I know they can fix in a manner of minutes... And so, I reported it.

Thanks for the quick (well, this time...) answer,
Avi