Please don't make non-trivial changes to chrome/browser/privacy_blacklists
if possible. I have a big change which I'll be soon (today) submitting for
review. It will be needed to integrate privacy blacklists with extensions.
--~--~-~--~~~---~--~~
Chromium
Hi Brett,
Thank you for your suggestions.
I would like to use the default size and resize it in my code that
creates tab thumbnails.
Regards,
Hironori Bono
E-mail: hb...@chrommium.org
2009/10/24 Brett Wilson bre...@chromium.org:
2009/10/23 Hironori Bono (坊野 博典) hb...@google.com:
Hi Brett,
Hi Mike,
Thank you for your question and suggestion.
On Sat, Oct 24, 2009 at 2:19 AM, Mike Pinkerton pinker...@chromium.org wrote:
All the screenshots show this with a single window. What happens if
you have multiple windows open? Does it only show the selected window?
Unfortunately, the
Hi there,
I rebuilt chromium yesterday from yesterday's tip on Linux (last time
I did that was about 8 weeks ago or so). I'm involved in developing
some NPAPI plugins that used to work well with my older chromium linux
build and that work without any issues in all other NPAPI supporting
browsers
Hi,
I am writing a new browser (source at
http://github.com/danielrh/berkelium/ ) using the RenderViewHost layer
of chrome.
I want to be able to send messages to the host process, and it looks
like the chrome.extensions.sendMessage() API is perfect for this.
However, when I do
Hi,
I am writing a browser (BSD source at
http://github.com/danielrh/berkelium/ ) that uses the RenderViewHost
layer of chrome.
I want to be able to send messages to the host process, and it looks
like the chrome.extensions.sendMessage() API is perfect for this.
However, when I do
in-line :-
On Thu, Oct 22, 2009 at 05:00, Peter Kasting pkast...@google.com wrote:
Update: So far I have 26 responses. Google Groups tells me these two
groups combined have as many as 4789 members (although there is probably a
lot of overlap between the two so that number is lower), so
On Mon, Oct 26, 2009 at 9:31 AM, Antoine Labour pi...@google.com wrote:
On Fri, Oct 23, 2009 at 1:58 AM, Anselm R Garbe garb...@gmail.com wrote:
The problem is that the chrome
executable (in particular statically linked in
libnpGoogleNaClPluginChrome.a) exports 'char
We only expose the extension bindings for pages with URLs of the form
chrome-extension://*. See chrome/renderer/render_thread.cc and search for
RegisterExtension. The (unfortunately named) v8 extension mechanism is how
the bindings get added.
On Fri, Oct 23, 2009 at 2:13 PM, Patrick Horn
I reopened http://code.google.com/p/chromium/issues/detail?id=17943 .
Please leave further instructions there and I'll fix it.
On Mon, Oct 26, 2009 at 10:19 AM, David Sehr s...@google.com wrote:
If what Antoine's saying is true, it has to do with ELF symbol visibility
and the dubious concept
On Sat, Oct 24, 2009 at 6:35 PM, Nicolas Sylvain nsylv...@chromium.orgwrote:
On Fri, Oct 23, 2009 at 2:16 PM, Andrew Scherkus scher...@chromium.orgwrote:
On Fri, Oct 23, 2009 at 12:28 PM, Nicolas Sylvain
nsylv...@chromium.orgwrote:
On Fri, Oct 23, 2009 at 12:21 PM, Andrew Scherkus
If what Antoine's saying is true, it has to do with ELF symbol visibility
and the dubious concept of symbol preemption. The NPAPI interface should
actually only require a small number of symbols be visible from the
plugin, and none (the best I know) from the browser. There's an interface
Darin, Peter,
I'm digging up this thread because the current Mac behavior turns
out to be problematic. Cocoa sets up the proper clipping region
before calling drawRect:. We can't just expand the invalid rect and
paint wherever we want, since Cocoa will ignore any drawing outside of
the
We need to change the address used by the issue tracker from '
codesite-nore...@google.com' to 'chrom...@googlecode.com'.
I'll be making this change immediately. Your mail filters might be affected.
--Mark
--~--~-~--~~~---~--~~
Chromium Developers mailing list:
Many of our HTML files have CSS in them (about_credits.html,
about_memory.html, etc) which needs to be tweaked per-platform (more
specifically, using an appropriate sans-serif font; see
http://crbug.com/21458). We already do templating with jstemplate, but from
what I can tell it can't swap out
On Mon, Oct 26, 2009 at 2:33 PM, Avi Drissman a...@google.com wrote:
Many of our HTML files have CSS in them (about_credits.html,
about_memory.html, etc) which needs to be tweaked per-platform (more
specifically, using an appropriate sans-serif font; see
http://crbug.com/21458). We already do
Why should these pages be treated any differently to any other
webpage? i.e. what's wrong with font-family: Helvetica, Arial,
sans-serif; - I'm pretty sure Windows users who have Helvetica
installed won't mind too much, and it's not like these pages are meant
to look native.
On Mon, Oct 26,
On Mon, Oct 26, 2009 at 5:44 PM, Evan Martin e...@chromium.org wrote:
Why not use sans-serif in the HTML, and then rely on the appropriate
platform specific mapping of sans-serif - font of choice in the
WebKit prefs?
Good question. If the page is considered our UI then we would have an issue
Thanks to all who took the recent survey on contributing to Chromium and the
barriers involved. We've looked at the feedback. A few themes stand out:
* A lot of you would like to contribute more than you currently do.
Awesome!
* A large number of you find Chromium developers friendly,
On Mon, Oct 26, 2009 at 4:15 PM, Peter Kasting pkast...@google.com wrote:
* Visit http://sites.google.com/a/chromium.org/dev/getting-involved . Two
of the top areas of interest for contributions were in testing builds to
file bugs, and helping users. This short page has some links that
For those interested parties, those labels are being deprecated at the end
of this week and are being replaced with Feature-Sync and Feature-Extensions
to better fit in the with the pattern we have been following with the issue
tracker. Please update your procedures accordingly, I'll make the
Correction Friday is the 30th. Also for awareness, the new labels are
already live in the issue tracker.
Kind Regards,
Anthony Laforge
Technical Program Manager
Mountain View, CA
On Mon, Oct 26, 2009 at 6:18 PM, Anthony LaForge lafo...@google.com wrote:
For those interested parties, those
I'm looking over our issue tracker and we currently have 10 bugs that are
marked as P0 (of which the majority haven't been touched in over 5 days),
and 17 issues that are marked as releaseblock-dev, either of which by
themselves would warrant attention. Until we have these under control, I'm
Quick correction re: the releaseblock-dev issues, there are in reality 5
label:releaseblock-dev bugs. However even at 5, that level
is unacceptably high, particularly in the context of so many P0 bugs.
24 matches
Mail list logo
