In general, the bug database (crbug.com/new) is a better place to file feature requests (file each one separately) than just sending them to the list. Also, some of your descriptions are too minimal. For example, in (3) you should be more specific about what's not being efficient (and by how much).
Regarding native client in Chrome, chromium-dev is the right place to ask. Erik On Thu, Dec 17, 2009 at 6:41 PM, hassenbentanf...@gmail.com < hassenbentanf...@gmail.com> wrote: > Improvements to chrome extension API: > > 1) children tabs > chrome.tabs should have a function to retrieve tabs opened by other > tabs as children tabs > Example: chrome.tabs.getChildren(tab.id) > > 2) getListeners() > Most of the time, we add more than one listener and it has a different > behavior. > It would be great to have function to retrieve listener and choose > wich one we would like to remove if there is more than one. > Example: chrome.tabs.onCreated.getListeners() > > > 3) CSS Injection is not efficient. > The CSS injection should be similar to the way the CSS is injected in > the manifest.json > Otherwise, we should at least be able to manipulate the content_script > in manifest.json dynamically. > > 4) Ability to manipulate other elements of chrome is not available. > For example, on Firefox, I'm able to manipulate the displayed menus on > right click. > At the moment, it is impossible to add stuff to menus in tabs or on > the page > > 5) Permissions should be updated to support more protocols or at least > give the user the choice to enable them using the options page > > 6) It would be great if we can override key pages. > For example, the page asking a confirmation when we are submitting a > form etc. > By overriding, I mean executing a custom theme, template and maybe > some javascript > > 7) As a web developer, I tend to use firebug and web developer tools. > Firebug is easily replaced by the chrome debugger even if a few things > are missing (like multiline javascript log, there is already a bug > report). > > However, I started writing a few functions from the web tools > developer extension in firefox and I had a few security issues when > manipulating the DOM. > Totally understandable. But, I would like to know what can I do to > bypass the security. > It does not have to be an extension. Is native client a solution? > Anything like that? > > Please do not suggest something like modify the source code and > recompile it. > > Thanks > > PS: anybody can give me a clue on when is native client coming on > linux chrome? Where can I track the progress or read discussions on > the subject? > > -- > > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
