not working for sciencedirect papers

[MarcYin]

The citedrive browser plugin seems working for MDPI but not for sciencedirect.

Example:

https://www.sciencedirect.com/science/article/pii/S0034425707003896?via%3Dihub

[MarcYin]

Issues from the console:

Uncaught (in promise) DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.

async function handleButtonClick() {
  const doi = retrieveDOIFromMetaTags();

  let bibtexEntry;

  if (doi) {
    try {
      bibtexEntry = await fetchBibTeX(doi);
    } catch (error) {
      console.error(error);

      alert("Failed to fetch BibTeX entry.");

      return;
    }
  } else {
    const citationInfo = collectCitationInfo();
    bibtexEntry = citationInfo ? citationInfo : generateBibtexWebEntries();
  }

  window.open(
    "https://app.citedrive.com/api/" + btoa(bibtexEntry),
    "_blank"
  );
}

[garethbilaney]

Thanks for the reporting this bug and showing the output of the error! I will have to take a closer look. In meanwhile, you can use our "online search" tool, directly in CiteDrive:

[garethbilaney]

Quick update: Just had a closer look and it looks like btoa(unescape(encodeURIComponent(bibtexEntry))); will do the trick. Will let you now as soon as possible and when I will ship a hot fix patch to the browser extension stores. Thanks again for sharing this bug!

[MarcYin]

Yes, it seems works after update the code. It would be great if you could update the extension.

Thanks.

[garethbilaney]

I have just made the patch fix available for publication. It may take a few days for Google and Microsoft to accept the changes. I will let you know as soon as I hear anything.

[garethbilaney]

Good news! The review process on Google's side has been faster than usual. The new changes should be in place if you use Google Chrome from now on.

[MarcYin]

Yes, I can confirm it's working on sciencedirect pages now.

Thank you very much.