New XKit 7.6.4
This update prevents XKit from running directly on blogs and increases the amount of location context provided to extensions. This fixes the issues with Themes, Themes Plus, and Timestamps.
This update prevents XKit from running directly on blogs and increases the amount of location context provided to extensions. This fixes the issues with Themes, Themes Plus, and Timestamps.
demijaxon-deactivated20151209 asked:
If you’re able to recreate the Aw Snap! error that is probably a bug that the Chrome developers would be interested in knowing more about. Their bug tracker is https://code.google.com/p/chromium/issues/list, although given they probably already know about the crashes with all the telemetry they have.
kingdom-noise asked:
Thanks for the information! This is a Chrome-specific permissions bug. It will be fixed by an update later today.
Anonymous asked:
It’s there now. The link is under the blog description. We’re also on the Firefox addon store.
operakitten asked:
Thanks for this. It’s beginning to look like Firefox users will keep their settings, and Chrome users won’t. Unfortunately, this isn’t fixable because it depends on the old XKit, not our new version.
Anonymous asked:
We forked this from XKit which has some incredibly broad permissions. While restricting the permissions is a goal, doing so would require a large amount of testing. If you want to contribute to restricting permissions, send an ask off anon and I can walk you through how to test with limited permissions.
Anonymous asked:
It should be under “New XKit”. You can also follow the link in our announcement post.
This will fix all the various disabling problems, and is overall easier. Please spread the word—we’re getting a lot of asks about the .crx method.