Yes, between major stable versions and almost every dev version, the
rendering engine is improved\changed.
☆PhistucK
On Mon, Jun 8, 2009 at 08:57, kindy kind...@gmail.com wrote:
the page i browsed(http://www.163.com/) is incorrect now, but it's right
in google chrome v1.
the attachment is a
Changing the default class cursor to NULL in widget_win.cc makes not
difference that I can see. Any other thoughts?
On Jun 13, 4:00 pm, Ben Goodger (Google) b...@chromium.org wrote:
No problem. Get well soon!
On Sat, Jun 13, 2009 at 3:55 PM, Daniel Cowxdaniel.c...@gmail.com wrote:
Sure,
Has anyone actually gotten this to work? I'm having trouble with line
endings. It looks like my webkit.org checkout got converted to using
CR LF line endings, but WebKitTools seems to want LF line endings.
Relatedly, which svn.exe should I have in my path for WebKitTools
(depot_tools or
Yeah, that issue is a pain. I'm using a Windows svn.exe (from depot_tools).
The only time it bugged me was with ChangeLog. After running
prepare-ChangeLog, I run dos2unix ChangeLog, and then I convert \ to /
manually. Kind of sucks, so I filed
https://bugs.webkit.org/show_bug.cgi?id=26000.
On Mon, Jun 15, 2009 at 11:13 PM, Daniel Cowx daniel.c...@gmail.com wrote:
Changing the default class cursor to NULL in widget_win.cc makes not
difference that I can see. Any other thoughts?
Look at all the classes along the inheritance hierarchy between you and the
root and see if anyone
On Mon, Jun 15, 2009 at 11:15 PM, Adam Barth aba...@chromium.org wrote:
Has anyone actually gotten this to work? I'm having trouble with line
endings. It looks like my webkit.org checkout got converted to using
CR LF line endings, but WebKitTools seems to want LF line endings.
Relatedly,
On Tue, Jun 16, 2009 at 9:55 AM, Darin Fisherda...@chromium.org wrote:
On Tue, Jun 16, 2009 at 9:47 AM, Peter Kasting pkast...@google.com wrote:
WebKit trunk checkouts only work when you only use the cygwin svn. You must never use a depot_tools svn or you will hose your checkout.
PK
That's
On Tue, Jun 16, 2009 at 9:55 AM, Darin Fisher da...@chromium.org wrote:
That's not true anymore. The canary bot uses svn from depot_tools.
Then all I can say is: when I accidentally used the depot_tools svn on my
existing cygwin svn checkout late last week, I had to blow away the checkout
to
On Tue, Jun 16, 2009 at 10:01 AM, Peter Kasting pkast...@google.com wrote:
On Tue, Jun 16, 2009 at 9:55 AM, Darin Fisher da...@chromium.org wrote:
That's not true anymore. The canary bot uses svn from depot_tools.
Then all I can say is: when I accidentally used the depot_tools svn on my
There are a surprising number of comic characters on here. I bet you
know Meryl Silverburgh!
Generally this type of thing is on the dev site like here:
http://dev.chromium.org/developers/design-documents/multi-process-resource-loading
Brett
--~--~-~--~~~---~--~~
r18363 introduced mem leaks in test_shell_tests and unit_tests.
It would be nice if they get sorted out with this too.
http://build.chromium.org/buildbot/waterfall/builders/Modules%20Mac%20(valgrind)/builds/1084/steps/valgrind%20test%3A%20test_shell/logs/stdio
Is this project (or some other Google project) considering to provide
a browser extension for other browsers (like Internet Explorer), which
would allow existing JavaScript pages to run faster (and provide
Chrome behavior) on such browsers?
For example, a site that requires v8 performance or v8
Hey I'm looking into these layout tests:
LayoutTests/media/audio-constructor-src.html
LayoutTests/media/audio-constructor.html
LayoutTests/media/constructors.html
and I need to know how constructors are generated. The failures all
appear to be due to the Audio constructor, specifically:
Hey I'm looking into these layout tests:
LayoutTests/media/audio-constructor-src.html
LayoutTests/media/audio-constructor.html LayoutTests/media/constructors.html
and I need to know how constructors are generated. The failures all appear
to be due to the Audio constructor, specifically:
I'm trying to run chrome's tests, but find lots of failures up there.
I wanna ask:
1. most of tests fail like below, why?
[--] Global test environment tear-down
[==] 42 tests from 8 test cases ran. (3984 ms total)
[ PASSED ] 41 tests.
[ FAILED ] 1 test, listed below:
[ FAILED
2009/6/16 David Jones ds...@163.com:
1. most of tests fail like below, why?
[--] Global test environment tear-down
[==] 42 tests from 8 test cases ran. (3984 ms total)
[ PASSED ] 41 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] TextEliderTest.TestGeneralEliding
A good place to start would be to look at existing *Constructor.cpp
files in WebCore/bindings/v8 and see how they are hooked in (like
Image constructor). Also, you have dimich and levin in close proximity
you who have added a V8 constructor or two in the past (I think).
;DG
On Mon, Jun 15, 2009
AutomationProvider::GetActiveWindow() comes from
browser/automation/automation_provider.cc
on windows, but
common/temp_scaffolding_stubs.cc
on mac and linux. Is anyone working on a real
AutomationProvider implementation for Linux?
--~--~-~--~~~---~--~~
Chromium
I tried to shovel everything I knew that would be of interest to
packagers onto this page:
http://code.google.com/p/chromium/wiki/LinuxPackaging
If you know of other contacts (like for Gentoo), please add them there.
If you have any other packaging-related questions, feed free to ask here.
A bunch of automation provider is compiled and works on linux/mac
(it's what UI tests use). A bunch still needs to be ported (behind
#ifs and some test files are not compiled). File a bug and have at
it!
On Tue, Jun 16, 2009 at 1:20 PM, Dan Kegeldaniel.r.ke...@gmail.com wrote:
about:crash is quite naturally one of our top crashers. When the Mac
dev channel went out, I saw this an entered http://crbug.com/13453 ,
thinking that the fact that we were receiving those crashes probably
meant we'd forgot to disable something before executing the handler.
But, no, it's also a
On Tue, Jun 16, 2009 at 2:32 PM, Scott Hesssh...@chromium.org wrote:
So, I'm inclined to mark it WontFix, except that then searches in the
Issues database won't find it.
Do we think it's something people are actually likely to search for?
The crash aggregator will still have the bug number
Thanks a ton for posting this, BTW. I've been thinking about it but
didn't have much to say.
As he mentions, this guffaw scrolling trickery is all necessary for
scrolling a window and its child X windows simultaneously. He also
mentions in the first paragraph that Mozilla (and a commenter
Getting the same error -- can anyone say what the fix is? (I just
synced a few hours ago...)
On Jun 12, 3:06 pm, Nebojša Ćirić nci...@gmail.com wrote:
maruel fixed the issue.
On Fri, Jun 12, 2009 at 2:20 PM, Nebojša Ćirić nci...@gmail.com wrote:
I downloaded depot_tools today around
On Tue, Jun 16, 2009 at 3:37 PM, Stuart Morganstuartmor...@chromium.org wrote:
On Tue, Jun 16, 2009 at 2:32 PM, Scott Hesssh...@chromium.org wrote:
So, I'm inclined to mark it WontFix, except that then searches in the
Issues database won't find it.
Do we think it's something people are
Problem was that my depot_tools were so corrupted that they weren't
syncing properly (nor was svn cleanup having any effect). Complete
removal and reinstallation seems to have done the trick.
On Jun 16, 4:09 pm, miran...@chromium.org miran...@chromium.org
wrote:
Getting the same error -- can
Hi,
The GypLanguageSpecification does not document the meaning of + ? ! /
characters currently.
TODO(sgk+mark): document settings merging with new = + ? ! / characters
I guess these characters determine the merging policy of settings in
gyp, but I am not sure. Can I get the precise meaning?
Yes, they are to set the merge policy. Extensive documentation is here:
http://code.google.com/p/gyp/wiki/InputFormatReference
http://code.google.com/p/gyp/wiki/InputFormatReference- James
On Tue, Jun 16, 2009 at 11:51 PM, KwangYul Seo kwangyul@gmail.comwrote:
Hi,
The
I know that you typically generate the project files via gclient
runhooks --force, but I'm curious to know how to generate the project
files via python directly, instead of via gclient.
--~--~-~--~~~---~--~~
Chromium Developers mailing list:
In the same directory with your .gclient file run:src/tools/gyp/gyp
src/build/all.gyp
-BradN
On Tue, Jun 16, 2009 at 9:17 PM, Daniel Cowx daniel.c...@gmail.com wrote:
I know that you typically generate the project files via gclient
runhooks --force, but I'm curious to know how to generate
What is the recommended procedure for working on long/big features?
In the past, I've always created a separate branch and then done all
my work there. I then do regular integrations from trunk into my
branch to ensure that that my branch doesn't drift too far out of sync
with the trunk (i.e. so
Use git-svn? See http://code.google.com/p/chromium/wiki/UsingGit .
On Tue, Jun 16, 2009 at 9:35 PM, Daniel Cowxdaniel.c...@gmail.com wrote:
What is the recommended procedure for working on long/big features?
In the past, I've always created a separate branch and then done all
my work there.
It might take a bit of getting used to, but git is a revision control tool
that allows you to create your own personal branches. Many Chromium
developers use it for their daily work. The way it interfaces with svn is a
bit clunky, but if you're not committing very often, it probably won't
matter
sorry to evanerg for the remail, my @google.com one bounced
Hi,
I dunno what's up, but git isn't sync'ing to the latest svn revisions for me:
(21:37:35) willchan: any git experts around?
(21:37:35) mdengfeng left the room (quit: Read error: 104
On Tue, Jun 16, 2009 at 9:35 PM, Daniel Cowx daniel.c...@gmail.com wrote:
What is the recommended procedure for working on long/big features?
Make an off-by-default switch and write your code under the switch, in the
trunk.
Branches eventually have to be integrated. This is never as easy to
35 matches
Mail list logo
