I've been noticing a few odd glitches on the battle tab lately. One of them is if i tap a player to get them off my tab they don't get removed they stay on the BT.
Also me and alot of my legion mates have been running into a annoying little thing lately where you disable someone and if you fail on the first raid when the timer for the next one cools down it makes the web page reset making it so you cant try to raid them if you've failed the first time.
Anyone know how to fix this or is it something dan has to do?

after you click attack once, do you close the window IMPROPERLY by clicking off to the side? or do you close the window PROPERLY by clicking the red X? if you click the red X it should refresh the BT and they'll disappear.... assuming it wasn't a NAP'd person.... NAPs you have to manually force a refresh after the cancelled attack by clicking BATTLE on the nav bar again

as for the page refresh issue.... keep your raids and hacks at least 15 minutes before the top of the hour.... when your system clock hits XX:00, the page will refresh... this is to prevent people from keeping someone on their screen all day long, constantly attacking/raiding/hacking them without an alert

I normally do hit the proper way to close it next time.
But as for the raiding issue it doesn't matter what the time is i can disable one person fail a raid the 5 min timer resets making the whole browser page refresh i can move on to another person right after and the same thing happens. I fail the first raid i wait for the timer to cool down and when it does the page refreshes.

the entire page shouldn't be refreshing, unless dan made a change in the last few days

what browser are you using? (brand and version number)

I use the improper way then click on the battle tab again and they disappear. For me using the proper method takes longer.

I'm using google chrome...

So do I and never had a problem.

same here... if you're getting a full page refresh when the raid or hack timer hits 0, all i can think is you have something running in the background actively eating your browser cookies... there's one browser cookie that controls the hourly refresh and without it you'll get a refresh the very next time you do anything