-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Chromium bugs we're tracking
48107 Different keydown event behavior between Windows and OS X
Closed Aug 2012. Status: IceBox
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).
Closed Jan 2013. Status: Fixed
Right now Previous / Next Tab does not work if the content scripts haven’t loaded, which is annoying.
28941 Add the ability to manipulate the clipboard from content scripts or background pages
Closed May 2011. Status: WontFix
(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
Closed Oct 2010. Status: WontFix
27048 Javascript: initKeyboardEvent has no effect
Closed Feb 2013. Status: Invalid
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.
Closed Sep 2010. Status: Duplicate of 54768.
Issue 54768 Closed Sep 2010. Status: Fixed
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.
28226 Implement APIs to trigger native context menu within extensions
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.
20773 Content scripts are unable to access window.frames[i].
Closed Aug 2013. Status: Fixed
This would make interactions between iframes easier.
63979 Should be able to use insertCSS and executeScript for a specific frame
136111 New tab page override cannot be toggled via extension options
136112 Multiple extensions with NTP overrides silently disrupt each other’s behavior
Closed Jul 2012. Status: WontFix
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.)
135146 PDF Viewer: Missing documentation of API (for web developers)
Resolving this bug would allow us to scroll/search PDFs (and possibly more).
155307 Provide eventListenerList to webpages or chrome extensions
357664 Content scripts cannot create Web workers from chrome-extension://..
Resolving this allows us to write asynchronous functions (eg. regexp search) much more simply. Any other non-dom-oriented code (eg. re-positioning link hints so they have minimal overlap) could also benefit from using web workers. Managing/labelling link hints across multiple frames in a tab would be much simpler/better using a SharedWorker too.
55804 Apply content scripts to about: and data: urls
#1239 / #934 where we don’t act on pages where the connection has errored would be resolved by this.
124989 Extension’s content scripts should be allowed to ignore CSP and web_accessible_resources
70700 An API to access a user’s search engines, so we can implement the “keyword”[tab] search UX that Chrome’s omnibar offers.
158277 Feature: Expose per-tab history in the API
This would also be useful for ensuring whether our H/L commands will work correctly.