Thread by @jpluimers

Trying to figure out why @googlecalendar `<iframe>` elements won't load in Chrome.

The URLs like calendar.google.com/calendar/embed… both 302 redirect to URLs like accounts.google.com/ServiceLogin?s…

The latter give `(blocked:other)`.

I have seen this happen for a while. Not sure why yet.

@googlecalendar The journey:

None of the extensions were visible on the @googlechrome toolbar.

This made the icons of @PrivacyBadger and @ublockorigin invisible.

Clicking on the extensions icon made them visible:

@googlecalendar @googlechrome @PrivacyBadger @ublockorigin By default @PrivacyBadger disables bout accounts.google.com and calendar.google.com, hence the `(blocked:other)` in the first tweet.

@googlecalendar @googlechrome @PrivacyBadger @ublockorigin Enabling just calendar.google.com in @privacybadger is not enough: it will show the calendar `<iframes>`, but with empty content:

@googlecalendar @googlechrome @PrivacyBadger @ublockorigin The reason is that calendar.google.com asynchronously updates the information from the domain clients6.google.com which is also by default blocked by @privacybadger:

@googlecalendar @googlechrome @PrivacyBadger @ublockorigin After enabling clients6.google.com in @privacybadger and refreshing both calendar `<iframe>` instances (or the page), both show data.

(I only show the first row of Week on the left and Month on the right because of privacy reasons)

There was no need to unblock anything in @ublockorigin as the blocked URL gadgets.buienradar.nl/akam/13/pixel_* was outside the google.com domain:

You need to open the logger (second icon from the right on the bottom row) to show this.

I wish clicking on "blocked" showed that.

@ublockorigin Lessons learned:

1. when things do not work on a page, verify the number badges on the @googlechrome extensions
2. @privacybadger is very strict (for good reason)
3. @ublockorigin logger is in a separate panel and not intuitive to find

/end