Change Details

µ-block Origin and probably others have registered our EventLogging endpoint. Blocking this request causes bad survey behavior: the user is able to complete a survey but their response is thrown away. We don't know how often this happens, yet. Decide how to handle this, and fix. It would be nice to detect blocking when recording the initial impression and never show the survey, but I think there's an ordering problem with that.

µ-block Origin and probably others have registered our EventLogging endpoint. Blocking this request causes bad survey behavior: the user is able to complete a survey but their response is thrown away. We don't know how often this happens, yet. Better would be to detect when the response couldn't be sent, and show an error in place of the thank-you message: > Unfortunately could not submit because of privacy settings. Try turning off your adblocker and refreshing the page. This would not be recorded in local storage as a success, and the survey would display again on the next page load.

µ-block Origin and probably others have registered our EventLogging endpoint. Blocking this request causes bad survey behavior: the user is able to complete a survey but their response is thrown away. We don't know how often this happens, yet. Decide how to handle this,Better would be to detect when the response couldn't be sent, and show an error in place of the thank-you message: > Unfortunately could not submit because of privacy settings. and fix. It would be nice to detect blockTry turning off your adblocker and refreshing when recording the initial impression and never show the surveythe page. This would not be recorded in local storage as a success, but I think there's an ordering problem with thatand the survey would display again on the next page load.