Hi,
I've released first (and hopefully last) RC build of new Gecko package and attached a patch against current Wine Git to bug 16198 http://bugs.winehq.org/show_bug.cgi?id=16198 It's critical to make sure, that there will be no regressions due to the new Gecko, it'd much more work to fix such regression than a usual regressions. I'd appreciate any help with testing it. Instructions how to do it are in the bug report. Any application that uses MSHTML is worth testing, esp ones that extensively use it.
I will write more about the new release and future plans later in an other subject.
Thanks, Jacek
On Sun, Dec 21, 2008 at 4:49 PM, Jacek Caban jacek@codeweavers.com wrote:
Hi,
I've released first (and hopefully last) RC build of new Gecko package and attached a patch against current Wine Git to bug 16198 http://bugs.winehq.org/show_bug.cgi?id=16198 It's critical to make sure, that there will be no regressions due to the new Gecko, it'd much more work to fix such regression than a usual regressions. I'd appreciate any help with testing it. Instructions how to do it are in the bug report. Any application that uses MSHTML is worth testing, esp ones that extensively use it.
I will write more about the new release and future plans later in an other subject.
Thanks, Jacek
(Let me know if you'd prefer to discuss this in the bug report instead)
The patch didn't apply cleanly against today's wine-git. Can you regenerate the patch? I tried applying the patch by hand, compiled, but running wine iexplore causes a crash. Maybe I didn't apply the patch correctly?
Hi Lei,
Lei Zhang wrote:
(Let me know if you'd prefer to discuss this in the bug report instead)
It doesn't matter for me.
The patch didn't apply cleanly against today's wine-git. Can you regenerate the patch?
That was because it contained a few patches that were committed today. I've attached a new patch.
I tried applying the patch by hand, compiled, but running wine iexplore causes a crash. Maybe I didn't apply the patch correctly?
That may be the reason.
Thanks!
Jacek