Achievement selector currently requires you to refresh the page to request new data from the API. This mostly affects dailies, as it will work with cached data.
The achievement selector currently doesn't really work well with updating data, so it will need some re-mangling probably.
We should consider moving all caching into the GW2API class, and have the achievement selector always "request" the data each time, and then have the GW2API class determine if it should respond with the cache data, or actually retrieve new data.
Achievement selector currently requires you to refresh the page to request new data from the API. This mostly affects dailies, as it will work with cached data.
The achievement selector currently doesn't really work well with updating data, so it will need some re-mangling probably.
We should consider moving all caching into the GW2API class, and have the achievement selector always "request" the data each time, and then have the GW2API class determine if it should respond with the cache data, or actually retrieve new data.