zusorio/GoodTwitter

Tweets no longer opening in window when clicked, switches to new page instead

Closed this issue ยท 15 comments

Whenever I click a tweet, it takes me to a new page altogether instead of opening in a new window on the page I clicked it like it previously did, resembling the new Twitter UI in functionality. I remember this issue eventually arose when I tried to use User Agent Switcher to bypass the new UI, before GoodTwitter was released.

I'm getting this problem too. Since GoodTwitter hasn't been updated overnight (last update was several days ago), I guess that means it's probably not a problem with the extension itself?

Looks like a server side change on their end to me. :(

UserScript workaround:

// ==UserScript==
// @name         Fix Twitter old UI
// @namespace    http://tampermonkey.net/
// @version      0.1
// @description  restore ability to open overlay without switching the page
// @author       You
// @match        https://twitter.com/*
// @grant        none
// ==/UserScript==

(function() {
    'use strict';

    let json = JSON.parse(window["init-data"].value);
    json.pushState = true;
    window["init-data"].value = JSON.stringify(json);
})();

Where would I input this exactly? Admittedly not familiar with modifying scripts like this. Do you plan on issuing an update to deal with this recent issue?
โ€ฆ
On Wed, Jul 31, 2019 at 9:40 AM vyv03354 @.***> wrote: UserScript workaround: // ==UserScript==// @name Fix Twitter old UI// @namespace http://tampermonkey.net/// @Version 0.1// @description restore ability to open overlay without switching the page// @author You// @match https://twitter.com/*// @grant none// ==/UserScript== (function() { 'use strict'; let json = JSON.parse(window["init-data"].value); json.pushState = true; window["init-data"].value = JSON.stringify(json); })(); โ€” You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12?email_source=notifications&email_token=AL23IHR3JWGBYMUIA4MW3ZLQCGI5DA5CNFSM4IIATN4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3HI6YI#issuecomment-516853601>, or mute the thread https://github.com/notifications/unsubscribe-auth/AL23IHRZRU7L545Z27M7WI3QCGI5DANCNFSM4IIATN4A .

You don't modify the extension. You crate a new userscript in your choice of script extension (tampermonkey, greasemonkey etc.) and copy what he wrote into it.

It worked here.

You don't modify the extension. You crate a new userscript in your choice of script extension (tampermonkey, greasemonkey etc.) and copy what he wrote into it.

It worked here.

Hahaha, sorry- I got emails from this thread and I thought they were all from the developer, I didn't realize they were actually thread replies. And I didn't realize replying via email also posts your message in this thread. Very sparse emails and a format I've never encountered before.

Alternatively, people on the Chrome-version repository of this extension said logging out and in solves it. Worked for me on Firefox as well.

Would it be possible to integrate the above pattern replacement functionality directly into this extension? There are extensions to change user agent, there are pattern replacement extensions, but this small one would be preferred. Thanks.

Sorry for not responding. It would be a good idea to integrate that into the add-on. Can anyone make a pull request?

Alternatively, people on the Chrome-version repository of this extension said logging out and in solves it. Worked for me on Firefox as well.

Thanks! This worked for me on Firefox as well...Phew, was driving me nuts.

I can safely say, that for now -- signing out of Twitter (Good Twitter) and then signing back in, for some reason, solved the issue of other windows (or tabs) opening when responding to someone's tweet. Yay! Thanks all.

Alternatively, people on the Chrome-version repository of this extension said logging out and in solves it. Worked for me on Firefox as well.

Thanks. That totally worked.

Logging out and in worked for me too.

Yes, logging out and in worked for me too. https://twitter.com/logout

Logging out and back in fixes this