[webkit-dev] how to debug the playbin2 used while playing video files from youtube using webkit browser application?

HI, how to debug the playbin2 used while playing video files from Youtube.com using webkit browser application? Regards Shiv The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the recipient and may contain privileged

[webkit-dev] Developing Desktop applications

Hey There, Can we develop the desktop application using QTWebkit. Our appplication mainly be using HTML,CSS,Javascript and C++ as its backend. If we can develop the application , then can we know What are the Softwares we need to download to start the devlopmwnt of the application. And also it wo

Re: [webkit-dev] Developing Desktop applications

> Can we develop the desktop application using QTWebkit. Please read http://webkit.org/contact.html first. This is the wrong place to ask that question. This webkit-dev list is for WebKit contributors to discuss the development of WebKit itself. You can use webkit-help instead: http://lists.webk

Re: [webkit-dev] how to debug the playbin2 used while playing video files from youtube using webkit browser application?

On Fri, 2010-03-19 at 15:28 +0530, Shivaprasad P wrote: > how to debug the playbin2 used while playing video files > from Youtube.com using webkit browser application? Please stop posting to both webkit-dev, and webkit-help request. Unless you wish to request/share information to devel

Re: [webkit-dev] Developing Desktop applications

Oh... i will post my question in the correct category...sorry abt that On Fri, Mar 19, 2010 at 10:09 AM, Ariya Hidayat wrote: > > Can we develop the desktop application using QTWebkit. > > Please read http://webkit.org/contact.html first. > > This is the wrong place to ask that question. This web

Re: [webkit-dev] minimum python version to support

No one responded back with a summary of the Python 2.4 discussion, so I'll attempt a summary of my own after reading-- https://bugs.webkit.org/show_bug.cgi?id=35584 (If you recall, we are trying to decide what Python code we write needs to work with Python 2.4.) The Chromium project still uses P

[webkit-dev] WebKit Icon license?

Dear WebKit folk, Would you happen to know how WebKit icon is licensed? :DG< ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] WebKit Icon license?

On Mar 19, 2010, at 8:40 AM, Dimitri Glazkov wrote: > Would you happen to know how WebKit icon is licensed? The icon currently on webkit.org has the icon for Apple’s Safari web browser in it. Because of that, Apple has provided no license to use the icon; we are continuing to use it with inform

Re: [webkit-dev] minimum python version to support

My understanding is that some of the libraries we use, like Mechanize, don't work in Python 2.4. My complaint in Bug 36063 is that we're re-implementing Mechanize poorly. I'd rather we just upgraded the machines that need to run-webkit-tests to a more modern version of Python. Adam On Fri, Mar

Re: [webkit-dev] minimum python version to support

Mechanize (and ClientForm on which it depends) does work with Python 2.4: http://wwwsearch.sourceforge.net/mechanize/ (See the section on compatibility.) On Fri, Mar 19, 2010 at 9:19 AM, Adam Barth wrote: > My understanding is that some of the libraries we use, like Mechanize, > don't work in

[webkit-dev] Chromium layout test expectations coming today

WebKit folks, We're finally ready to land our port's expected results in the WebKit tree. It's been a long journey, but we are now to the point where it no longer makes sense to keep Chromium expectations separate from the rest of the WebKit. It's a pretty large chunk of files, so please bear wit

Re: [webkit-dev] minimum python version to support

Awesome! /me goes and comments on the bug. Adam On Fri, Mar 19, 2010 at 9:57 AM, Chris Jerdonek wrote: > Mechanize (and ClientForm on which it depends) does work with Python 2.4: > > http://wwwsearch.sourceforge.net/mechanize/ > > (See the section on compatibility.) > > > On Fri, Mar 19, 2010

Re: [webkit-dev] Chromium layout test expectations coming today

That is really good news! Congratulation! Kenneth On Fri, Mar 19, 2010 at 2:13 PM, Dimitri Glazkov wrote: > WebKit folks, > > We're finally ready to land our port's expected results in the WebKit > tree. It's been a long journey, but we are now to the point where it > no longer makes sense to ke

Re: [webkit-dev] Chromium layout test expectations coming today

Before you commit it: Would it make sense to stuff this data somewhere outside of the main checkout, like we do in Chrome with the deps/ dir? I know that's a departure from how the WebKit test results currently work, but I also expect people are not going to be too happy about XXXmb of not-useful-

Re: [webkit-dev] minimum python version to support

FYI, Chromium folks on Windows will be on python 2.6 real soon(tm). The CL to bug them to upgrade should be committed within the next few minutes. [Thread hijack] If you're not a Chromium-Webkit committer running on Windows, please ignore the rest of this email. Otherwise, please "del depot_tool

Re: [webkit-dev] minimum python version to support

Chromium already uses the installed python for Mac/Linux, which defaults to 2.5. So it sounds like we can safely use 2.5. Ojan On Fri, Mar 19, 2010 at 10:26 AM, Marc-Antoine Ruel wrote: > FYI, Chromium folks on Windows will be on python 2.6 real soon(tm). > The CL to bug them to upgrade should b

Re: [webkit-dev] Chromium layout test expectations coming today

I agree that the idea of only pulling down expectations that you would actually need sounds great -- in fact we did try to think of ways of how this could be accomplished. So far, no great proposal materialized, but it doesn't mean the door of opportunity closes at this commit. I would think of thi

Re: [webkit-dev] Chromium layout test expectations coming today

Checking it into the main WebKit checkout seems very much in keeping with the standard WebKit practice. Several times folks have noted that they like only having one respository to deal with (just sync webkit and you're set). On a personal note, I appreciate the simplicity of the WebKit approach -

Re: [webkit-dev] Chromium layout test expectations coming today

Also, one sometimes needs to update test expectations even for platforms they don't build on. - WBR, Alexey Proskuryakov On 19.03.2010, at 10:50, David Levin wrote: Checking it into the main WebKit checkout seems very much in keeping with the standard WebKit practice. Several times folks

[webkit-dev] Gtk and Qt bots need love

Gtk and Qt bots need love. Looks like Gtk needs 5 new results, and Qt needs 42. Various other tests are failing there too. Do any Qt/Gtk folks have a minute to try and green up the bots so we can start tracking regressions on those platforms again? -eric

Re: [webkit-dev] Gtk and Qt bots need love

On Fri, Mar 19, 2010 at 9:59 PM, Eric Seidel wrote: > Gtk and Qt bots need love. > > Looks like Gtk needs 5 new results, and Qt needs 42. > > Various other tests are failing there too. > > Do any Qt/Gtk folks have a minute to try and green up the bots so we > can start tracking regressions on thos

Re: [webkit-dev] Gtk and Qt bots need love

Hey, these 42 missing results files on Qt are there for a while, indeed. I am also trying Kenneth and Ossy w/ the crashy Qt bot, by looking at fast/media/print-restores-previous-mediatype.html On Fri, Mar 19, 2010 at 3:41 PM, Xan Lopez wrote: > On Fri, Mar 19, 2010 at 9:59 PM, Eric Seidel wrote

Re: [webkit-dev] Chromium layout test expectations coming today

As I understand it, the single repository is important for allowing developers to atomically commit a patch that includes both a code fix, a corresponding test, and expected results for that test. -Darin On Fri, Mar 19, 2010 at 11:08 AM, Alexey Proskuryakov wrote: > > Also, one sometimes needs

Re: [webkit-dev] Chromium layout test expectations coming today

Also, note that in Chromium, the expected results for layout tests are not in a separate deps/ dir :-) http://src.chromium.org/viewvc/chrome/trunk/src/webkit/data/layout_tests/platform/ -Darin On Fri, Mar 19, 2010 at 10:26 AM, Evan Martin wrote: > Before you commit it: > > Would it make sens

Re: [webkit-dev] Chromium layout test expectations coming today

The expectations are in as of r56278. Huge thanks to Dirk Pranke for battling svn all day! :DG< On Fri, Mar 19, 2010 at 10:13 AM, Dimitri Glazkov wrote: > WebKit folks, > > We're finally ready to land our port's expected results in the WebKit > tree. It's been a long journey, but we are now to t

Re: [webkit-dev] Chromium layout test expectations coming today

platform/chromium/test_expectations.txt contains bug references to crbug.com. I presume that newly filed bugs will be in bugs.webkit.org instead. Unfortunately, it is going to be a bit hard to tell the difference given only the bug number. Is there a system we should use to annotate the differen

Re: [webkit-dev] Chromium layout test expectations coming today

On Mar 19, 2010, at 10:35 AM, Dimitri Glazkov wrote: I agree that the idea of only pulling down expectations that you would actually need sounds great -- in fact we did try to think of ways of how this could be accomplished. So far, no great proposal materialized, but it doesn't mean the door o

Re: [webkit-dev] Chromium layout test expectations coming today

Currently we do BUG12345 for Chromium bugs. There are no WebKit bugs listed. How about we instead use CR12345 for Chromium bugs and WK12345 for WebKit bugs? Ojan On Sat, Mar 20, 2010 at 12:09 AM, Darin Fisher wrote: > platform/chromium/test_expectations.txt contains bug references to > crbug.co

Re: [webkit-dev] Chromium layout test expectations coming today

Uh, good point. I forgot about this. Ojan's suggestion (later in thread) sounds like a good one. -- Dirk On Fri, Mar 19, 2010 at 5:09 PM, Darin Fisher wrote: > platform/chromium/test_expectations.txt contains bug references to > crbug.com.  I presume that newly filed bugs will be in bugs.webkit.

Re: [webkit-dev] Chromium layout test expectations coming today

On Mar 19, 2010, at 5:30 PM, Ojan Vafai wrote: Currently we do BUG12345 for Chromium bugs. There are no WebKit bugs listed. How about we instead use CR12345 for Chromium bugs and WK12345 for WebKit bugs? Another possibility would be to use bug URLs. WebKit bugs can be referenced as

Re: [webkit-dev] Gtk and Qt bots need love

If you cannot get it working, please add it to Skipped and I will look into it on monday when I'm back at work. I was actually talking to a co-worker about our long list of new results while on the plane yesterday and I will see if my team can dedicate a day per week to look into these. Kenneth