Checking another approach

[jrmgx]

That's funny I have the same problem as you – need a link for a given email – and I found you on stackoverflow then, your chrome extension here.

Anyway I wanted to improve a little bit this extension and while doing it I found another working approach, let me explain:

• I use the content script too
• I hijack the "Show original" button in inbox email menu
• When that page open the script kicks-in and get the message id from that email
• It builds a valid inbox search url and copy it to the clipboard
• Finally auto close the "show original" page

Advantages:

• This gives you a google inbox link to that email
• It seems to be quite resilient to inbox markup changes

Inconvenients:

• Open/close a page
• Not so well integrated into inbox

Evolution:

• Instead of opening the page, the extension could intercept it and do the job without messing up tabs
• It could be nice to change the "Show original" entry to reflect the new action or add an entry to that menu

I join the code here as a fork does not have sense (code 100% new)

/* content.js */
function parseParams() {
    var query = location.search.substr(1);
    var result = {};
    query.split("&").forEach(function(part) {
        var item = part.split("=");
        result[item[0]] = decodeURIComponent(item[1]);
    });
    return result;
}

function copyTextToClipboard(text) {
    var copyFrom = document.createElement("textarea");
    copyFrom.textContent = text;
    document.body.appendChild(copyFrom);
    copyFrom.select();
    document.execCommand('copy');
    copyFrom.blur();
    document.body.removeChild(copyFrom);
}

var params = parseParams();
if (params.view && params.view == "om" && params.ik && params.permmsgid) {
    var d = document.querySelectorAll('td.message_id');
    if (d && d.length >= 1) {
        var id = d[0].innerText;
        copyTextToClipboard("https://inbox.google.com/search/rfc822msgid%3A" + id);
        window.close();
    }
}

manifest need a new permission: clipboardWrite

[adrienjoly]

Hello Jérôme ! ^^

Your approach is interesting.

Once you extracted the email-id, how do you build the "valid inbox search url"?

E.g. the message id I found in the notification email triggered by this issue that you posted was <adrienjoly/chrome-inbox-permalinks/issues/[email protected]>, but the URL https://inbox.google.com/search/rfc822msgid%3A%3Cadrienjoly/chrome-inbox-permalinks/issues/[email protected]%3E is a 404. 🤔

Does this code work as expected? If so I'd love to see a short screencast that shows it in action, and way to install this extension without having to create it myself from your code snippet ^^

[jrmgx]

see https://github.com/jrmgx/chrome-inbox-permalinks for a working version
Install the extension, reload inbox, then use the "Show original" option of any email and you'll have the link for that email copied in your clipboard.
Tested with last chrome and last vivaldi.
Other comments from my first message still apply (need polishing)

[adrienjoly]

I just tried it. Unfortunately the URL that was generated from one of my emails (the one I mentioned on a previous comment above) does not work: https://inbox.google.com/u/0/search/rfc822msgid%3A%3Cadrienjoly/chrome-inbox-permalinks/issues/[email protected]%3E

[jrmgx]

It gives me:

https://inbox.google.com/search/rfc822msgid%3A<5b4cb04db515d_42ab24a1853181235c4%40fb84a5df-efc0-4488-bc94-828ee2552c83.mail>

a little bit different from the one you have, note the /u/0 part and also < and > not escaped on my side but @ is ... it seems that the escaping behave differently. Weird.

I confirm it works with a like like this one,
maybe you could forge one to test and then we could check what is wrong with the escaping?

[adrienjoly]

Maybe it's because I use several google/gmail accounts. (hence the `/u/1` suffix, as explained in another closed issue of this repo) Le mar. 17 juil. 2018 à 22:53, Jérôme Gangneux <[email protected]> a écrit :

It gives me: https://inbox.google.com/search/rfc822msgid%3A<5b4cb04db515d_42ab24a1853181235c4%40fb84a5df-efc0-4488-bc94-828ee2552c83.mail> a little bit different from the one you have, note the /u/0 part and also < and > not escaped on my side... weird totally working here — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAgdRW8MfZ3vZVwo1PTqtaMA0LmO0UeEks5uHk7IgaJpZM4VP9nq> .

-- Adrien Joly https://adrienjoly.com/now