Solved it myself through trial and error. Thought I’d report back if someone else stumbles upon this problem. It shall still be noted that this problem did not occur before Chrome updated itself to Chrome 13 (13.0.782.107m). The trick here seems to be to add a translate3d operation to the underlying <div> (sq2) element upon … Read more
For anyone that finds this in the future, since version 20 Chrome supports window.performance.memory, which returns something like: { totalJSHeapSize: 21700000, usedJSHeapSize: 13400000, jsHeapSizeLimit: 1620000000 }
Use @match, as described here. Example: // ==UserScript== // @match http://*/* // @match http://*.google.com/* // @match http://www.google.com/* // @match https://www.google.com/* // ==/UserScript==
It’s relatively easy to add whole web pages by having your content script inject them in an iframe. Just follow these guidelines: Place the *.htm or *.html files in your extension’s source folder(s). Place any *.css and *.js files, that the HTML uses, in the extension folder(s) too. Declare the HTML file(s) as resources. EG: … Read more
Chrome doesn’t seem to expose this setting, but what you can do is the following: get the ModHeader plugin for Chrome: https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj?hl=en (or any other that allows you to fiddle with your browser request headers) set a new custom header accept-encoding to either: an empty value or gzip;q=0,deflate;q=0 either should work
The browser cache behaves differently on different settings. You should not depend on user settings or the user’s browser. It’s possible to make the browser ignore headers also. There are two ways to prevent caching. –> Change AJAX request to POST. Browsers don’t cache POST requests. –> Better Way & good way: add an additional … Read more
Let’s assume all browsers we are interested in are Internet Explorer 8 or newer (e.g. IE5 has some terrible behaviour with caching headers). There is only ONE standards based way of controlling caching (introduced with HTTP/1.1) – the Cache-Control HTTP header. Since at least 1996 IE has been using an opt-out policy for caching HTTPS … Read more
What’s described in the question is actually expected behavior — required per the HTML spec: https://html.spec.whatwg.org/multipage/#nonce-attributes:attr-nonce Elements that have a nonce content attribute ensure that the crytographic nonce is only exposed to script (and not to side-channels like CSS attribute selectors) by extracting the value from the content attribute, moving it into an internal slot … Read more