Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogle Chrome extension: Mac Compatibility
    primarykey
    data
    text
    <p>I've this <a href="https://chrome.google.com/extensions/detail/libokbfffpaopdjmeofdfpmlanaenaje" rel="nofollow noreferrer">Tab Sugar</a> Google Chrome extension which <strong>works fine under Windows</strong>: when installed, the user can click on its icon right in the browser, and access the Tab Sugar dashboard, as a new page in a new tab.</p> <p>But for some reason, it <strong>doesn't seem to work at all on Google Chrome under OSX</strong>: users experience that nothing happens when clicking on the extension icon. Nothing at all. No new tab.</p> <p>Since I don't own any Mac, any help on this subject would be more than welcomed!</p> <ol> <li>Be sure you use a Mac and Google Chrome (or Chromium)</li> <li>Then <a href="https://chrome.google.com/extensions/detail/libokbfffpaopdjmeofdfpmlanaenaje" rel="nofollow noreferrer">install the Tab Sugar extension</a></li> <li>Click on the extension icon in the browser</li> <li>If nothing happens, then you just reproduced</li> <li><p>Open the background.html page in a new tab:</p> <p><code>chrome-extension://libokbfffpaopdjmeofdfpmlanaenaje/background.html</code></p></li> <li><p>Open the developer traces console (<code>Ctrl+Shift+i</code>)</p></li> <li>Try to understand what's going on there?!</li> </ol> <p><strong>Edit:</strong> As an alternative, Tab Sugar's code is browsable from its <a href="http://github.com/arnaud/chrome-tab-sugar" rel="nofollow noreferrer">GitHub repository</a>.</p> <p><strong>Edit 2:</strong> An <a href="http://github.com/arnaud/chrome-tab-sugar/issues#issue/5" rel="nofollow noreferrer">issue</a> was reported on this specific subject</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload