Chromium bugs we're tracking

Add the ability to manipulate the clipboard from content scripts or background pages
(this is required so we can implement “yy”, to yank the current page’s URL to the clipboard)
28941

Content scripts on view-source: pages
30516

Javascript: initKeyboardEvent has no effect
It may be possible to trigger the native find dialog programmatically by using something like
event=document.createEvent(“KeyboardEvent”);
event.initKeyboardEvent(“keydown”, true, true, null, “U+0046”, 0, “accel”); // 046 is F; accel = meta
document.body.dispatchEvent(event);

However, I can’t run this experiment because event.metaKey is always false, I believe because of this bug:
27048

Simulated links made from content scripts trigger the popup blocker. This is the root cause of #26.
32350

When restoring tabs, we don’t preserve Chrome’s tab order or history. Here is a feature request for Chrome to give us an API to hook into their tab reopening system, which would solve both issues for us.
14737

Content scripts don’t run on non-html (images). Issue #99.
12082
32619

Implement extensions APIs to execute browser commands. Would be nice if they exposed the ability do a native Restore Tab, to close the ‘save password’ or Download box, etc. (I.e. A more general form of the initKeyboardEvent issue.)
28084

Ability to add global keyboard shortcuts (without using a content script). Right now Previous / Next Tab does not work if the content scripts haven’t loaded, which is annoying.
27702

Content scripts are unable to access window.frames[i].
20773

When we support running on pages with the file:// protocol, note that Chrome only allows extensions to run on file:///, whereas files can be opened with file://
40846