Re: [webkit-dev] DOM Mutation Event compatibility.

Kalle Alm <[EMAIL PROTECTED]> wrote: > We're in the process of making isolated test cases for as many of the > issues we found as we are able to. I think our reports will straighten > out most of your confusion. Since we're talking "user input=>issue", > I've made a template for mutation-event sty

Re: [webkit-dev] DOM Mutation Event compatibility.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maciej & Dave, We're in the process of making isolated test cases for as many of the issues we found as we are able to. I think our reports will straighten out most of your confusion. Since we're talking "user input=>issue", I've made a template for m

Re: [webkit-dev] DOM Mutation Event compatibility.

What Dave said about filing bugs is good advice, but some comments about the issues you mentioned... On Jul 3, 2007, at 2:54 AM, Kalle Alm wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello folks, In the process of making SynchroEdit compatible with Safari 3, we have done some pro

Re: [webkit-dev] DOM Mutation Event compatibility.

Please file bugs on http://bugs.webkit.org/ for each individual issue, even if you're not sure it's a bug. Reduced test cases for each bug (that fail on Safari/WebKit but work on MSIE or Firefox) would help a lot! Please attach the test cases as HTML files rather than pasting the HTML in a commen

[webkit-dev] DOM Mutation Event compatibility.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello folks, In the process of making SynchroEdit compatible with Safari 3, we have done some profiling in regards to DOM Mutation Events, comparing these between Safari 3 and Firefox 2, in order to detect compatibility issues, general bugs, and poten