An extension "registers" callbacks to Chrome for a specific situation given you described a specific interface to do so
can some one elaborate on this? ty
An extension "registers" callbacks to Chrome for a specific situation given you described a specific interface to do so
can some one elaborate on this? ty
It will be solved by "allow cookies" for me. However, I can't reply here, so I reply & note by hypothes.is.
cf. The "Change your cookie settings" section in this website: https://support.google.com/chrome/answer/95647?co=GENIE.Platform%3DDesktop&hl=en
For some reason, no one ever seems to thing of this... but it has always worked for me... Have you tried unchecking Use hardware acceleration when available at the bottom of chrome://settings/ (advanced area)?
This worked for me when Chrome was freezing every time I loaded a page. I was seriously worried I had a rootkit or key logger that I couldn't detect!
We do not support casting from Android or iOS at this time.
Good to know. Somewhat surprising.
this app DOES NOT do
History Trends
History Trends Unlimited - Chrome Web Store google.com pmP site directo procurar11 chromea14.1_d3ext
Type “dh” and hit the “tab” key to enter Deep History search mode. Then type in search terms and Deeper History will search pages you have visited for those terms and return matching pages right there in your browser bar, just like google search.
What about extensions for other browsers? We’re working on that. The next supported browser is likely to be Firefox.
I'm writing this note in... Safari!
I thought hypothes.is could only work with the Chrome applet.
Still looking for a way to use hypothes.is from a tablet.
does anyone not use Chrome?
I think that plenty of users, perhaps especially those keen on open source, prefer Firefox.
Readium plug-in for Chrome
The temporary solution we found is to wrap chrome.* api callback with setTimeout() function. In that case errors thrown within chrome.* api call are passed to window.onerror with correct line number. Example:
Wrapping all the chrome.* async API calls such that exceptions in the callback result in an error being logged to a handler that we control looks like the way to go.
In Chrome extensions, errors thrown in callbacks for async APIs do not trigger the global window.onerror handler.
The following selection from The Yale Law Journal is not paginated and should not be used for citation purposes.
Note that this disclaimer only says the document should not be used for citation purposes, but doesn't say we can't use it for annotation purposes like testing out the Chrome PDF.js + Hypothes.is extension! :)
You can install the extension from the Chrome Web Store with this link: