Yes, I think you are right. On Mon, Nov 3, 2008 at 10:40, Darin Fisher <[EMAIL PROTECTED]> wrote:
> Thanks Finnur. There are some interesting challenges to get it working > properly. We have to re-implement the tick marks code upstream. The issue > of find-in-page not working at all is probably unrelated to tick marks > presentation, so we should be able to fix that separately. > -Darin > > > > On Mon, Nov 3, 2008 at 10:31 AM, Finnur Thorarinsson <[EMAIL PROTECTED]>wrote: > >> >> I'll assign that bug to me, although I won't get to it until next week. If >> someone needs it earlier, you are welcome to pick it off of my plate and see >> what the problem is. >> >> >> On Mon, Nov 3, 2008 at 10:24, Ojan Vafai <[EMAIL PROTECTED]> wrote: >> >>> Sigh. Apparently I've been emailing myself here. Shouldn't I get a bounce >>> message when my email just gets dropped on the floor? >>> In either case, here's the very belated summary of the merge landing last >>> week. The only part worth noting really is the one bug that still needs an >>> owner (find-in-page doesn't work). >>> Ojan >>> >>> On Thu, Oct 30, 2008 at 3:43 PM, Ojan Vafai <[EMAIL PROTECTED]> wrote: >>> >>>> Merge is done (woot! to darin and dglazkov!). The good news is that, >>>> other than failing layout tests and the JSC build, there's not much fallout >>>> this time. The page cyclers actually show better performance and memory >>>> usage than before the merge! The tree is now open and there's only one >>>> unassigned bug (other than failing layouttests): >>>> >>>> http://crbug.com/3908: Find in page highlighting and tickmarks are broken >>>> >>>> >>>> As far as layout tests failures that need fixing, here's the stats: >>>> ~100 new tests >>>> ~100 tests we're currently failing that were changed or rebaselined in >>>> WebKit 36102:37604 >>>> ~90 tests that we've regressed (~20 of which are flaky!) >>>> >>>> Ojan >>>> >>>> On Thu, Oct 30, 2008 at 1:40 PM, Ojan Vafai <[EMAIL PROTECTED]> wrote: >>>> >>>>> We need to get the tree geener, but not totally green given 1.0 >>>>> demands. >>>>> In order to get the tree green: >>>>> -Disabled UI tests that are failing (pkasting) >>>>> -Submit layout tests results for those without expected results >>>>> (dglazkov) >>>>> -Make webkit test lists match the state of the tree (ojan) >>>>> >>>>> Things that should happen today if possible, but don't need to keep the >>>>> tree closed (http://crbug.com?q=label:WebKitMerge37604): >>>>> -Fix linux build >>>>> -Fix JSC build >>>>> -Fix purify failure (there's only one! Document::dominantScript) >>>>> -Selenium tests failing >>>>> -Fix the UI tests that were just disabled above >>>>> >>>>> Please volunteer to do some of the above as noone is currently working >>>>> on them. >>>>> >>>>> Ojan >>>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
