Due to an API limitation, total votes are only tallied for active committee members.
However the API call returns last known total votes for both active and backup committee members.
Thus, if a member's last known total (prior to being made inactive) was higher than any of the active members' totals, they will be displayed as active at that position, pushing everyone else one position down and the last actual active member completely out of the active member list.
Current example: harvey-xts (backup) appearing in the active list pushing chris4210 (active) off it.
Due to an API limitation, total votes are only tallied for active committee members.
However the API call returns last known total votes for both active and backup committee members.
Thus, if a member's last known total (prior to being made inactive) was higher than any of the active members' totals, they will be displayed as active at that position, pushing everyone else one position down and the last actual active member completely out of the active member list.
Current example: harvey-xts (backup) appearing in the active list pushing chris4210 (active) off it.