That sounds like about 8 features.
Seems we should think about this in smaller chunks...
On the surface "peer to peer video conferencing" does not seem like
something appropriate to add to WebCore/WebKit. Just like "an API for
reading my email" is out of scope for the project. (But certainly lo
Look under Sources/WebCore/platform/graphics.
Or just grep the source directory for "glyph". :)
-eric
On Mon, May 16, 2011 at 9:52 AM, Soheil Servati Beiragh
wrote:
> Hi
> I want to find out where does webkit saves the glyph data of characters and
> read from it? I think when it renders text it
o issue to fix. :) I suggest that you read
the CSS 2.1 spec and this will all become much clearer.
As to where the height of a block is calculated? I would have to dig around,
but I would start with methods like computeContentBoxLogicalHeight The
height is going to be calculated as part of la
e area.
>
> So, ther root cause of the problem is when for float image,
> positionNewFloatOnLine() is called, it has to appropriately set the
> paragraph framerect.
>
> Thanks.
>
> On Tue, May 17, 2011 at 11:48 PM, Eric Seidel wrote:
>
>>
>>
>> On Tue, M
If someone does that, seems we should turn it into a script in Tools/Scripts
for easy testing of buildbot! :)
On Mon, May 23, 2011 at 10:58 AM, Adam Roben wrote:
> On May 20, 2011, at 8:22 PM, Dmitry Lomov wrote:
>
> I am trying to make run-api-tests run at build time.
> I wonder what is the rig
***Mac-EWS machines down until further notice.***
I'm sorry for the unexpected outage. I may be able to bring them up as soon
as next week.
If someone else would like to try running a mac-ews, the instructions remain
the same as always:
1) Tools/Scripts/webkit-patch mac-ews
2) There is no step
Exciting times!
On May 23, 2011 8:57 PM, "Keishi Hattori" wrote:
> Hi webkit-dev,
>
> I just wanted to notify everyone that I will be adding a new feature
> flag, INPUT_COLOR. http://webkit.org/b/61273
>
> This flag will enable
>
> I need this flag because the color picker UI needs to be implemen
I appreciate that you've followed the master-bug idiom which is so common in
bugs.webkit.org these days!
I also would *strongly* encourage you to post your changes in as small of
patches as possible. Integrating features which have been developed outside
webkit.org is always difficult, but doing
I get a lot of these:
Revision r86028 cherry-picked into qtwebkit-2.2 with commit 7e1bab1 <
http://gitorious.org/webkit/qtwebkit/commit/7e1bab1>
as bug mail. Probably because I'm CC'd on a zillion bugs (and actually read
my bug mail).
This is probably the pot calling the kettle black, since I w
d to support it, imo...
>
>
> On Thu, May 26, 2011 at 7:05 PM, Evan Martin wrote:
>
>> On Thu, May 26, 2011 at 3:54 PM, Eric Seidel wrote:
>> > I get a lot of these:
>> > Revision r86028 cherry-picked into qtwebkit-2.2 with commit 7e1bab1
>> > <http://
Related:
We swapped out the guts of Tools/EWSTools/start-queue.sh a few weeks back.
If you run an EWS bot and haven't restarted it manually in a while, now
would be a good time to. start-queue.sh makes the EWS robust against python
changes, but when we change start-queue.sh bots require manual r
There are a couple steps missing, but this hits most of the important
points.
I think one could turn such into a blog post with diagrams if so desired.
-eric
On Sat, May 21, 2011 at 5:55 PM, Mustafizur Rahaman
wrote:
> Hi,
>
> When you are drawing some text, you create a RenderText(RenderObjec
Someone could check:
https://www.google.com/webmasters
I no longer have access (but I could go through the process of getting
access if needed).
-eric
On Tue, May 31, 2011 at 1:37 PM, Ademar Reis wrote:
> Hi there.
>
> Since a couple of days ago (when?), our trac/wiki is not appearing as
> rele
I know that Ahem is safe to use across multiple platforms (the font metrics
will be the same). Do we know if there are any other fonts for which this
is true?
I'd like to make the style-bot yell at people when they use pixel tests with
non-safe fonts. Right now that list would only include ahem.
Bill would have access to any logs there may be.
On Sun, Jun 5, 2011 at 7:20 PM, Matt Falkenhagen wrote:
>> Since a couple of days ago (when?), our trac/wiki is not appearing as
>> relevant on google search results anymore.
>>
>> I guess google blacklisted the site because of some sort of spam or
I think our .in files get pre-processed. So you can use normal c++
preprocessor definitions.
#if defined(ENABLE_CSS_REGIONS) && ENABLE_CSS_REGIONS
But I could be remembering wrong...
On Mon, Jun 6, 2011 at 4:25 AM, Alexandru Chiculita wrote:
> Hi,
> Until we have working CSS Regions and CSS Ex
No, there is no "stock" or "template" port of webkit. Chromium might
be the closest thing to such with it's PlatformBridge abstraction
(since webkit runs inside a restricted sandbox in chromium and can't
talk always directly to the OS).
But you're better off starting with whatever port is closest
ada, N9B 3P4
> Phone: 519-253-3000 Ext 3396
> Email: serv...@uwindsor.ca
>
> From: Eric Seidel
> To: Soheil Servati Beiragh
> Cc: "webkit-dev@lists.webkit.org"
> Sent: Monday, June 6, 2011 2:21 PM
> Subject: Re: [webkit-dev] WebKit port t
Do you have statistics on how much total time rendering flickr.com is
in CSS/Style code at all? I believe it to be very low.
-eric
On Mon, Jun 6, 2011 at 1:16 PM, Kulanthaivel Palanichamy
wrote:
> Hi All,
>
> At Qualcomm Innovation Center we have been working on a parallel algorithm
> for CSS s
I have posted a patch to (optionally) ASSERT whenever fastMalloc is
called with 0 size:
https://bugs.webkit.org/show_bug.cgi?id=55097
After fixing https://bugs.webkit.org/show_bug.cgi?id=55091 for a large
performance win in the HTML parser (by avoiding a single fastMalloc(0)
call) I now believe th
was to avoid those problems.
>>>
>>> Adam
>>>
>>>
>>> On Thu, Jun 2, 2011 at 1:29 AM, Hao Zheng wrote:
>>> > Actually, even the same Ahem font will be rendered differently on
>>> > different platform, depending on the font drawing
You noted it spends 66% of its "CSS time" in StyleForElement. What
about total page load time?
Then again 6450ms spent in CSS sounds like a lot of time regardless.
Answering what % of total page load time we're spending in CSS (or
StyleForElement) is important.
Loading www.flickr.com/photos/tags
Re-sending w/o the attached file.
On Wed, Jun 8, 2011 at 3:31 PM, Eric Seidel wrote:
> I used Safari's built-in Page Load Test mechanism to test the page.
>
> I created a flickr.pltsuite and placed it in
> /Applications/Safari.app/Contents/Resources/flickr.pltsuite with the
&
WebKit as we're very interested in making things faster!
Again, best of luck with your efforts. At this time WebKit does not
believe that parallel CSS styling would yield any noticeable
performance increase on standard page loads.
-eric
On Wed, Jun 8, 2011 at 3:31 PM, Eric Seidel wrote:
> I used
This is *so* importnat to the long-term health of your port.
Congrats! I'm happy to review what I can and will look through them now.
-eric
On Fri, Jun 10, 2011 at 12:02 PM, Leandro Pereira
wrote:
> Hey,
>
> At last, the EFL port of WebKit got a DumpRenderTree implementation!
> We're still wor
,
mostly due to the lack of smart pointers.
I'm ready to r+ the patches re-posted with some modern c++ usage.
I'm also OK with someone else approving them if EFL style requires
this ancient-C (and bad memory-management) look.
-eric
On Fri, Jun 10, 2011 at 12:10 PM, Eric Seidel wrote:
I would go so far as to suggest removing both Diff and Formatted Diff.
I guess I'm more excited about removing Formatted Diff than I am
Diff, since Diff actually has some built in bugzilla crazy features
(like diffing between attachments!?!) but Formatted Dfif is just a
lame version of Review Patc
Speaking of the "review patch" link. I really want a way to CC people
from there... I don't think that's easy to do, since it uses the
"details" view to actually do the submit, but it would be nice to
have. :)
On Mon, Jun 13, 2011 at 1:19 PM, Adam Barth wrote:
> On Mon, Jun 13, 2011 at 12:15 PM
My 2¢:
I'm confused by who the client of this API would be.
It seems that "web sites" don't really need to know my battery state.
But "web applications" that are on mobile phone (like WebOS, or
Apple's original vision for iPhone apps) would want battery state
information, but would want *more* in
> CPU usage, or run a timer at a lower frequency. Crazy idea: Maybe an
> advertising network could be "nice" and not show animated ads to such
> users? ;-)
> -Darin
>
> On Fri, Jun 17, 2011 at 10:47 AM, Eric Seidel wrote:
>>
>> My 2¢:
>>
>> I'm co
You should also feel welcome to land test suites which entirely/mostly
fail, and then later land the code changes which make them pass. We
used this method with great success for the HTML parser re-write.
This can be useful in cases where your individual tests have larger
coverage than any indivi
I'm running clean-pending-commit and clean-review-queue now. Adam and
I will make sure to set up a bot to run both next week.
-eric
On Sat, Jun 18, 2011 at 1:03 PM, Darin Adler wrote:
> On Jun 17, 2011, at 10:56 PM, Adam Barth wrote:
>
>> There are a 194 open bugs with an R+ patches attached to
On Sat, Jun 18, 2011 at 1:15 PM, Darin Adler wrote:
> On Jun 18, 2011, at 12:58 PM, Oliver Hunt wrote:
>
>> On Jun 18, 2011, at 12:24 PM, Darin Adler wrote:
>>
>>> http://trac.webkit.org/changeset/89190
>
> Looks like Ossy did look at this one; it was not a Qt issue at all, broken on
> all non-V8
m and I will look at next week).
-eric
On Sat, Jun 18, 2011 at 1:12 PM, Eric Seidel wrote:
> I'm running clean-pending-commit and clean-review-queue now. Adam and
> I will make sure to set up a bot to run both next week.
>
> -eric
>
> On Sat, Jun 18, 2011 at 1:03 PM, Darin Adle
webkit-patch upload clears all flags when obsoleting a patch. We
could make it not clear r- if you like. I know of no way to construct
a query like http://webkit.org/pending-commit in our current bugzilla
without clearing r+ on obsolete patches/closed bugs. We clear flags
(specifically r+) to ma
On Sun, Jun 19, 2011 at 11:31 AM, Darin Adler wrote:
> On Jun 18, 2011, at 9:01 PM, Antonio Gomes wrote:
>
>> I actually do not like the way the review flags are cleared today only in
>> order to make the tools and pending-xxx pages happier. IMO the review flags
>> give much about the history of
lso be helpful when sheriff bot rolls out a patch to attach the
> rolled out patch with a nice description like ROLLOUT(rX) to the bug?
>
> On Sun, Jun 19, 2011 at 8:36 PM, Eric Seidel wrote:
>>
>> On Sun, Jun 19, 2011 at 11:31 AM, Darin Adler wrote:
>> > On J
Please do not cross-post.
A cursory internet search shows HbbTV has little to do with WebKit.
What spec covers HbbTV? What other browsers implement such?
Your mail does not seem appropriate for this list.
-eric
On Sun, Jun 19, 2011 at 10:26 PM, Vicky Tux wrote:
> Hi,
> We have to implement Hb
I'm not sure this will help you Song, but here is a talk I gave a
couple years back which talks some about the DOM vs. Rendering tree
separation:
http://www.youtube.com/watch?v=RVnARGhhs9w
Best of luck in your exploration.
-eric
On Thu, Jun 16, 2011 at 4:34 PM, Darin Adler wrote:
> On Jun 16, 2
In general it's pretty safe to cq+ a patch, especially an old one.
Since the cq + EWS tests patches better than just about any committer
ever does manually. :)
We built infrastructure to have the sherriff-bot auto-rollout patches
which caused any tree redness. If folks want, we could turn that on
I think svn.webkit.org has been having some troubles today. I know
there was some discussion of SSL errors involving svn.webkit.org in
#webkit. wsiegrist maintains the hook (it's not even in the
repository iirc).
-eric
On Mon, Jun 20, 2011 at 2:40 PM, David Levin wrote:
> For example, this pa
I think it's better for our reviewers to review only things they're
comfortable with.
We could also teach bots (like the style-bot) to complain when seeing new API.
I'd rather not add another layer of process.
-eric
On Wed, Jun 22, 2011 at 11:31 AM, Ryosuke Niwa wrote:
> On Wed, Jun 22, 2011 a
I know you made some consideration of "fixed point" vs. "float point"
in your investigation. I suspect that decision is orthogonal to work
of plumbing more precise types through the engine... but I am still
curious to know if there was a decision if fixed point or float point
might be the eventual
Looking at the master bug, it looks like we're close to switching the
project to new-run-webkit-tests:
https://bugs.webkit.org/show_bug.cgi?id=34984
There appear to be 6 remaining blocking issues:
https://bugs.webkit.org/showdependencytree.cgi?id=34984&hide_resolved=1
We would like to hear from o
Correct. We convert from UTF16 to UTF8 (for libxml2) and then back to UTF16.
There has been at least one libxml-related security fix to WebCore in
recent memory.
We have various hacks in the libxml2 parser due to libxml2 being
designed to be a library used by applications, and not used by a
libr
That was done, long ago. You can find the old patches in our svn history. :)
On Tue, Jun 28, 2011 at 6:44 PM, Wyatt Carss wrote:
> If that were all, would it be possible to patch libxml2 to use UTF-16? That
> might be less of an undertaking than writing a new xml library, but that
> could just b
I like the idea of -failing. But what happens when you have both
-failing and -expected in the same directory? Are either accepted?
(in which case it's like a file-system version of test-expetations
flaky lists)
On Fri, Jul 1, 2011 at 12:49 PM, Ojan Vafai wrote:
> I proposed a while back to chr
;> enough concern to kill the idea. It would be interesting to see how
>> big of an impact there is, and, obviously, a given port could chose
>> not to use -failure files if it didn't want to.
>>
>> -- Dirk
>>
>> On Fri, Jul 1, 2011 at 12:56 PM, Eric Seide
; I suspect more issues will crop up once we actually flip the switch.
>>> Please do not hesitate to contact Eric or myself (either via #webkit
>>> or via bugs.webkit.org). We'll try to respond to any issues that
>>> arise as quickly as possible.
>>>
>>> Tha
patience in this process. Please let me know if you
see any issues you think we may have missed. We're still watching the
bots and fixing issues as they appear.
-eric
On Tue, Jul 5, 2011 at 4:03 PM, Eric Seidel wrote:
> We've turned NRWT back on for the WebKit1 Snow Leopard bots.
sses=1. So the bots are
running in very very slow mode (about as fast as ORWT was). We'll
turn on parallel testing with new-run-webkit-tests once we've
transitioned all ports.
On Tue, Jul 5, 2011 at 10:53 PM, Eric Seidel wrote:
> Update:
>
> Snow Leopard - Successful transition
ul 6, 2011 at 2:20 AM, Xan wrote:
> On Wed, Jul 6, 2011 at 11:10 AM, Eric Seidel wrote:
>> Update:
>>
>> Leopard Release, Gtk and Qt have been successfully transitioned.
>
> What do we exactly consider successfully transitioned? The GTK+ bots
> were still failing, so I
Xan and I found the issue regarding the timeouts, and Xan is trying
NRWT again on the machine:
https://bugs.webkit.org/show_bug.cgi?id=63983
On Wed, Jul 6, 2011 at 2:20 AM, Xan wrote:
> On Wed, Jul 6, 2011 at 11:10 AM, Eric Seidel wrote:
>> Update:
>>
>> Leopard Release,
We've intentionally left that decision up to the ports.
Mac has a stop-gap test_expectations.txt file, which depending on the
result of this discussion will likely be expanded, or removed:
http://trac.webkit.org/browser/trunk/LayoutTests/platform/mac/test_expectations.txt
That exists solely to rec
Nm, Adam Barth already split the thread in a nicer name too. Folks
can reply there. :)
On Wed, Jul 6, 2011 at 9:12 AM, Eric Seidel wrote:
> We've intentionally left that decision up to the ports.
>
> Mac has a stop-gap test_expectations.txt file, which depending on the
&g
One other difference I should point out:
Skipped lists "cascade" through the normal results fallback mechanisms
(if it ever doesn't exactly match ORWT, that's a bug!). For example,
Mac uses platform/mac-snowleopard/Skipped, combined with
platform/mac/Skipped.
http://trac.webkit.org/browser/trunk/
On Wed, Jul 6, 2011 at 10:18 AM, Xan Lopez wrote:
> On Wed, Jul 6, 2011 at 6:29 PM, Eric Seidel wrote:
>> NRWT uses both! It will read in all the port's Skipped files, covert
>> them to SKIP text_expectations, and add them to your test_expectations
>> file.
>>
"old-run-webkit-tests -2 --debug" produces:
107 test cases (<1%) had incorrect layout
1 test case (<1%) crashed
8 test cases (<1%) Web process crashed
24 test cases (<1%) had stderr output
"new-run-webkit-tests -2 --debug" (which is what I'm trying to make
work better) produces:
Regressions: Une
)
In other news, Qt, Gtk, Leopard and Snow Leopard all seem to be using
NRWT successfully. We've had very few reports of trouble over the
last 24 hours.
I'm working on the last few details for WebKit2 and plan to enable
NRWT on the WebKit2 bots tomorrow.
-eric
On Wed, Jul 6, 2011 at 2:10
I do not know the history as to why Chromium removed support for
test_expectations cascading.
Ideally we would have fewer test expectations, not more in the future. :)
On Thu, Jul 7, 2011 at 3:16 AM, Balazs Kelemen wrote:
> On 07/06/2011 07:24 PM, Eric Seidel wrote:
>>
>> On Wed,
There is code in old-run-webkit-tests attempting to support "msys"
configurations. (Which appears to be used by the WinCE port?)
Is this an active configuration? Or can we remove "msys" support when
transitioning to new-run-webkit-tests.
Is the WinCE port still active?
-eric
__
As part of fixing https://bugs.webkit.org/show_bug.cgi?id=64086 I
found that only the CYGWIN port still uses Apache 1.3. However, it
has its own special httpd.conf file to do so.
Now that Tiger is removed (and all known linux ports have moved to
Apache 2), LayoutTests/httpd/conf/http.conf no long
Thank you. Will do.
On Mon, Jul 11, 2011 at 11:10 PM, Patrick Gansterer wrote:
> On Mon, 11 Jul 2011 21:30:44 -0700, Brent Fulgham
> wrote:
>>> Is the WinCE port still active?
>>
>> I don't know about your other questions, but Patrick Gansterer (paroga)
>> maintains the WinCE port. I believe i
I believe what Adam means by this (it wasn't immediately clear to me),
is that we have 1500 redundant result files with duplicate git hashes
to some other file. This could be calculated by the
deduplicate_results.py script by removing any of the current fallback
logic and just look at raw duplicat
http://build.webkit.org/builders/SnowLeopard%20Intel%20Leaks/builds/18482/steps/layout-test/logs/stdio
2011-08-08 16:03:36,710 67413 manager.py:1403 ERROR worker/0 raised
OSError('[Errno 28] No space left on device:
'/var/folders/dR/dRbf9KVoHs0rNZjRONbHTU+++TI/-Tmp-/DumpRenderTree-CL_oFh''):
It's
you for your help.
-eric
On Mon, Aug 8, 2011 at 6:09 PM, Mark Rowe wrote:
>
> On 2011-08-08, at 17:16, Eric Seidel wrote:
>
>> http://build.webkit.org/builders/SnowLeopard%20Intel%20Leaks/builds/18482/steps/layout-test/logs/stdio
>>
>> 2011-08-08 16:03:36,710 67413 man
I suggest you pain the bikeshed MAC_CG instead of MACCG. The brains
our children's children will thank me.
-eric
On Tue, Aug 16, 2011 at 11:31 AM, Adam Barth wrote:
> Hi WebKit,
>
> In an effort to make the Chromium port more consistent across
> platforms, we're moving the Chromium Mac port fro
Exciting times!
Is there a Master bug that those of us interested in following along
at home can CC ourselves on?
Looking forward to seeing a real Android port in WebKit!
-eric
On Mon, Aug 22, 2011 at 12:25 PM, Andrei Popescu wrote:
> Hello WebKit!
>
> We would like to give an update about Web
We could also teach DumpRenderTree to lie about what "/" is, so we
could include the scripts like this:
On Thu, Sep 8, 2011 at 1:14 AM, Adam Barth wrote:
> On Thu, Sep 8, 2011 at 12:41 AM, Maciej Stachowiak wrote:
>> Do you have an idea for how to avoid needi
It seems the "sucessfullyParsed" question could also be answered by
some intelligent onerror handler added to the right script tag.
On Thu, Sep 8, 2011 at 10:16 AM, Ryosuke Niwa wrote:
> Yeah, if the script is located at LayoutTests/resources/js-test.js for
> example, all I need to type is
>
>
FYI: As many of you already know, the build.webkit.org bots run
"run-bindings-tests" on (almost) all platforms.
They've been running (mostly w/o incident) on the bots since 6/20:
http://trac.webkit.org/changeset/89267
These just make sure that our generated bindings look sane, by
comparing the
hat Darin Adler, was at one point at least one happy
customer of this script:
https://bugs.webkit.org/show_bug.cgi?id=62880#c5
-eric
On Thu, Sep 8, 2011 at 11:49 AM, Alexey Proskuryakov wrote:
>
> 08.09.2011, в 11:32, Eric Seidel написал(а):
>
>> FYI: As many of you already know,
If the objection against run-bindings-tests is that they're not part
of some larger test script which developers can run locally, it's very
easy to add a wrapper script which runs all known testing harnesses.
The test tests which currently run on the bots include:
run-webkit-tests (minutes)
run-ja
I'm curious how other developers search the WebKit code?
I use http://codesearch.google.com/#search/&q=package:webkit from time
to time. If others do too, we should make it a redirect from
cs.webkit.org (like we do for cia.webkit.org).
Or maybe folks have better code search solutions? grep -r?
On Thu, Sep 8, 2011 at 12:44 PM, Darin Adler wrote:
> On Sep 8, 2011, at 12:29 PM, Eric Seidel wrote:
>
>> I'm happy to write a run-all-tests script which runs all known tests that
>> platform can handle. :)
>
> I think run-webkit-tests should be this. We can come
I am interested in removing the ENABLE_SVG define, and all associated
sub-defines
ENABLE_SVG_ANIMATION
ENABLE_SVG_AS_IMAGE
ENABLE_SVG_FONTS
ENABLE_SVG_FOREIGN_OBJECT
ENABLE_SVG_USE
SVG is part of HTML5, and all major ports compile and ship with SVG
enabled (and have for years).
Please let me kno
-dev@lists.webkit.org
> Subject: Re: [webkit-dev] Do you compile with ENABLE_SVG diabled?
>
> When doing ports to various embedded systems we often disable SVG to reduce
> the size of the resulting library. It would be nice to retain the top level
> ENABLE_SVG define for this purpose.
&g
Folks can track the general task of feature removal at:
https://bugs.webkit.org/show_bug.cgi?id=68012
I will link all the "Remove ENABLE_*" bugs to that one.
-eric
On Tue, Sep 13, 2011 at 11:20 AM, Eric Seidel wrote:
> Hearing no objections to removing any of the sub-defines, I
I also noticed that WINCE looks abandoned in my work on bug 68018 this morning.
-eric
On Tue, Sep 13, 2011 at 12:00 PM, Antonio Gomes wrote:
> I believe it was maintained by Torch Mobile, and, according to George
> Staikos, it is not part of the plans any more (Torch was acquired by RIM).
>
> No
rote:
> On Tue, Sep 13, 2011 at 11:27 AM, Eric Seidel wrote:
>>
>> Folks can track the general task of feature removal at:
>> https://bugs.webkit.org/show_bug.cgi?id=68012
>
> Nice this is helpful, thanks.
>
>>
>> I will link all the "Remove ENABLE_*&
On Tue, Sep 13, 2011 at 2:38 PM, Patrick Gansterer wrote:
> How do we measure an "active port"??? I maintain a buildbot for WinCe and
> usually fix problems with the port within hours. Unfortunately I don't get
> paid to work on WebKit the whole day and so I can't make such big steps
> forward
I was actually considering removing ENABLE(FILTERS) since it seemed to
be on everywhere. It would probably be better for us to remove it
first and this feature to exist under its own define (if it even needs
a define?).
If you'll want folks to be able to turn this off w/o affecting their
existing
On Thu, Sep 22, 2011 at 11:44 AM, Dean Jackson wrote:
>
> On 23/09/2011, at 4:38 AM, Eric Seidel wrote:
>
>> I was actually considering removing ENABLE(FILTERS) since it seemed to
>> be on everywhere.
>
> Sorry to bring bad news, but Apple currently turns off ENABLE(FIL
Interesting. It is unfortunate that we currently have no easy way to
tell which ports are shipping with which defines enabled. I didn't
think to check the settings on the branch.
Thank you for the clarification.
-eric
On Thu, Sep 22, 2011 at 1:06 PM, Darin Adler wrote:
> The settings in TOT a
On Sun, Sep 25, 2011 at 9:12 AM, Ryosuke Niwa wrote:
> On Sun, Sep 25, 2011 at 2:30 AM, Adam Barth wrote:
>> Yeah, I'm not sure where we should draw the line, but this case seems
>> pretty clearly in the "unmaintained" camp, as was the old Android
>> port. Maybe a good rule of thumb is something
Every file:// url has a unique security origin in Chrome. So the test
only works in Safari.
Try using Tools/Scripts/run-safari.
-eric
On Fri, Sep 30, 2011 at 1:13 AM, Monil Parmar wrote:
> Hi,
>
> Iam trying to run the parser performance test on webkit through
> PerformanceTests.
> But iam fac
Interesting. I thought historical policy was universally against the
word "get" in function names. I guess you're suggesting that "get"
should only be applied to function names which have an out-argument?
-eric
On Tue, Oct 4, 2011 at 6:00 PM, Darin Adler wrote:
> On Oct 4, 2011, at 2:06 PM, Ry
That sounds very related to which features are enabled on which ports.
A per-directory map is probably easier to produce of course.
We have no good way to get any of this information out of our myriad
build and branch strategies employed by the numerous ports. :)
I too am in favor of [port] pref
At least as of Snow Leopard, it was impossible to run the layout
tests, without a login-session/security context.
You would need to be physically logged into the machine, and then run
the tests from VNC/Remote Desktop for them to work. In snow leopard
SSHing to a machine (without being physically
Adam is sitting on a committee today, but can boot the bot as soon as he's out.
-eric
On Mon, Oct 17, 2011 at 4:01 PM, Ryosuke Niwa wrote:
> I think abarth or eseidel need to "kick" the bot.
> - Ryosuke
>
> On Mon, Oct 17, 2011 at 3:51 PM, Darin Adler wrote:
>>
>> Hi folks.
>>
>> Something’s wr
Related:
Reducing sprawling includes, particularly in headers, can have a large
effect on incremental build times (and thus developer happiness).
Tightening layering practices between WebCore and WebCore/platform
also paves the way for splitting out platform into a separate .a, also
decreasing inc
After a long hiatus, I'm back working on NRWT.
As of this evening all of the blocking issues to switching the WK2 bot
are resolved:
https://bugs.webkit.org/show_bug.cgi?id=56729
Just waiting for the WK2 bot to have some smaller number of failures,
then I'll pull the trigger.
After WK2 is switch
After further testing tonight, I was able to reproduce the exact set
of 81 WebKit 2 failures with both NRWT and ORWT this evening. I'm
going to move the bots to NRWT shortly.
-eric
On Wed, Oct 19, 2011 at 9:59 PM, Eric Seidel wrote:
> After a long hiatus, I'm back working on NR
ilder to switch is Apple's Windows. (I
likely won't be able to takle that one myself.)
Thanks again for your patience in this process.
-eric
On Thu, Oct 20, 2011 at 9:54 PM, Eric Seidel wrote:
> After further testing tonight, I was able to reproduce the exact set
> of 81 WebKit
:41 AM, SravanKumar Sandela
wrote:
> Hi Eric,
>
> Can you please inform us, what are the major difference between NRWT and
> ORWT. I think it would of lot help for people like me who worked on ORWT
> long back and now to catch up with NRWT.
>
> Thanks a lot in anticipation.
&g
*happy* to help fix things.
:)
-eric
On Fri, Oct 21, 2011 at 12:52 PM, Antonio Gomes wrote:
> Hi Eric.
>
> So does it it mean that any "being upstream'ed" port which was also
> providing a ORWT based bot, should actually switch to NRWT instead?
>
> Cheers,
>
&
On Fri, Oct 21, 2011 at 1:37 PM, Nico Weber wrote:
> build-webkit will then use make instead of xcodebuild, and
> new-run-webkit-tests will use the make-produced binary. On my machine,
> this reduced full build times from 17 minutes to 12 minutes (50% of
> the original gcc & xcodebuild build time)
None of the Safari browsers (Mobile included) are open-source.
Chromium (chromium.org) is open source, if that helps you.
-eric
On Sun, Oct 23, 2011 at 7:36 AM, 道雄野口 wrote:
> Hi
>
> I am looking for a source code of mobile safari.(iOS Safari)
> I want to see address bar and search bar source co
This is the wrong list for this question. webkit-help is a better
choice for these topics.
There is no free-to-distribute version of WebKit for windows to my
knowledge. Apple's windows version (the DLLs from the nightly)
requires non-redistributable libraries from Apple. Making it
il-suited for
As of this afternoon, the Apple-Win bot is the only remaining buildbot
(to my knowledge) using old-run-webkit-tests
(https://bugs.webkit.org/show_bug.cgi?id=38756).
Unfortunately, that's not likely to change soon. But all other
platforms (and all other developers) besides Apple-Win should be usin
301 - 400 of 926 matches
Mail list logo