Chromium bugs we're tracking

Key handling

48107 Different keydown event behavior between Windows and OS X

48111 Keydown event under Windows doesn’t return correct keyIdentifier for non-US keyboard layout.

27702 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.

Clipboard manipulation

28941 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)
NOTE This has been resolved, finally. We can implement yy more cleanly than we do today, and we can implement “open new tab with contents of clipboard”.

55188 execCommand(“Copy”) broken within content scripts

Simulating user-generated events

27048 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:

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

14737 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.

Content Script Injection

30516 Content scripts on view-source: pages

12082 Content scripts doesn’t work on image-view pages
Content scripts don’t run on non-html (images). Issue #99.

32619 document_start is not run on raw data URLs (like images and text)
Content scripts don’t run on non-html (images). Issue #99.

Cross-frame content script access

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

20773 Content scripts do not have access to a page’s iframes.

This would make interactions between iframes easier.

New tab page

136111 New tab page override cannot be toggled via extension options

136112 Multiple extensions with NTP overrides silently disrupt each other’s behavior

Miscellaneous issues

110149 scrollHeight is broken for nodes with pseudo-elements of height 0

28084 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.)

Search engines:

70700 An API to access a user’s search engines, so we can implement the “keyword”[tab] search UX that Chrome’s omnibar offers. This would be useful for the Vomnibar.