This could be a caching issue. Whenever I encounter this problem in Chrome, I switch over to Safari and I do see my solution there.