Bugzilla

Thanks for the report! I believe this can be fixed by adding `workplace.com` to the Facebook entity on [Disconnect's entitylist](https://github.com/disconnectme/disconnect-tracking-protection/blob/16214b4ca390236194e609e970f67999f1e6d2c3/entities.json#L4546). I've filed https://github.com/disconnectme/disconnect-tracking-protection/issues/104 for that and will update this bug with status on that.

Based on the screenshots in Comment 0, the completely broken site experience (CSS/JS) is due to the STP list pulling in `fbcdn.net` from the `Content` category of the Disconnect list. This is fine when the STP list is used for cookie blocking, since we want to block cookies from the `Content` category by default anyway. However, it seems like a bad idea when the STP list is used for tracker blocking. That's the case for "Strict" mode of Firefox desktop and the default mode of Fenix.

Tanvi, what do you think about excluding domains from the STP list that are in the `Content` category? We know that blocking content from origins in those categories typically causes a ton of breakage, like we're seeing here.

Thanks for the report! I believe this can be fixed by adding `workplace.com` to the Facebook entity on [Disconnect's entitylist](https://github.com/disconnectme/disconnect-tracking-protection/blob/16214b4ca390236194e609e970f67999f1e6d2c3/entities.json#L4546). I've filed https://github.com/disconnectme/disconnect-tracking-protection/issues/104 for that and will update this bug with status on that.

Based on the screenshots in Comment 0 and Comment 2, the completely broken site experience (CSS/JS) is due to the STP list pulling in `fbcdn.net` from the `Content` category of the Disconnect list. This is fine when the STP list is used for cookie blocking, since we want to block cookies from the `Content` category by default anyway. However, it seems like a bad idea when the STP list is used for tracker blocking. That's the case for "Strict" mode of Firefox desktop and the default mode of Fenix.

Tanvi, what do you think about excluding domains from the STP list that are in the `Content` category? We know that blocking content from origins in those categories typically causes a ton of breakage, like we're seeing here.