fresh install on chrome complains of "possible conflict" about xkit

[nightpool]

I had a similar experience testing the new extension on chrome.

[nightpool]

the offending line seems to be xkit.js:758

    if ($("#dashboard_controls_open_blog").length === 0)

which was from the old blog stats bar. Not sure which plugin hides these, but we add them back in. Maybe do the opposite and a check for > 0 would be useful?

[nightpool]

also this line is also true:

$(".likes").length === 0 || $(".following").length === 0 || $(".spotlight").length === 0

in fact, none of these classes are present at this time

[dlmarquis]

@nightpool Tumblr removed that entire div, so that bit of code should be removed. I'll deal with it, but I'm on a roadtrip right now and my internet could cut out at any time, so it might be a couple hours before you see the changes.

[dlmarquis]

Just submitted the changes. They'll be incorporated into the next release of XKit.

[nightpool]

@dlmarquis I can deal with it, I'm just wondering if there's anything we should put in its place. (we should probably try to detect for old-xkit, for example)

do we have any known conflicts with other tumblr plugins?

[dlmarquis]

@nightpool It should be detecting old versions of Xkit already, but that appears to be broken at the moment. It's probably just a matter of bumping the version number.

We know there's a conflict with Stylish that makes XKit unusable, but we don't know why, since Stylish plays nice with the old version. That probably deserves its own issue.

[nightpool]

@dlmarquis sounds good.

[nightpool]

fixed by #95