Re: [webkit-dev] Reporting FCKeditor related bugs
On Jan 13, 2007, at 4:52 AM, Frederico Caldeira Knabben wrote: Thanks for the comments Maciej. I've just filled 15 new reports with generic descriptions. I'll try to refine them in the future whenever possible. It seams that some bugs can be solved with workarounds in the editor code. I've still to check it. Having those bugs fixed will make FCKeditor close to be officially announced as compatible with Safari. I'm excited with it! Great, glad to hear it! We appreciate you working with us on this stuff and getting the bugs filed. Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
RE: [webkit-dev] Reporting FCKeditor related bugs
Hi Joost, > if you need any help with Bugzilla or reducing bugs, let me know, i'd love > to see your editor working! We have a Master Bug for FCKeditor: http://bugs.webkit.org/show_bug.cgi?id=9915 Check out the dependencies there. Any help you could give is more than welcome. Thanks for your message. Best regards, FredCK ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
RE: [webkit-dev] Reporting FCKeditor related bugs
Thanks for the comments Maciej. I've just filled 15 new reports with generic descriptions. I'll try to refine them in the future whenever possible. It seams that some bugs can be solved with workarounds in the editor code. I've still to check it. Having those bugs fixed will make FCKeditor close to be officially announced as compatible with Safari. I'm excited with it! Regards, FredCK > -Original Message- > From: Maciej Stachowiak [mailto:[EMAIL PROTECTED] > Sent: Saturday, January 13, 2007 12:36 AM > To: David D. Kilzer > Cc: Frederico Caldeira Knabben; webkit-dev@lists.webkit.org > Subject: Re: [webkit-dev] Reporting FCKeditor related bugs > > > On Jan 12, 2007, at 6:36 AM, David D. Kilzer wrote: > > > Hi FredCK, > > > > I'd recommend filing all of the bugs. That way if someone else > > gets the notion to create a reduced test case or fix the bug, > > that's less work you'll have to do in the long run! > > > > Please do a cursory search for existing bugs before filing new ones > > as well. For example, "links are clickable in the editing area" > > may be similar to Bug 11297. (It took me three searches to find > > that one, though, so don't spend all your time search for pre- > > existing bugs!) It's better to have the bugs documented and later > > marked RESOLVED/DUPLICATE than to not have them documented at all. > > > > http://bugs.webkit.org/show_bug.cgi?id=11297 > > I agree with Dave's suggestion. Having the bugs filed is more > important than level of detail in the bug. We will likely need > reductions for these at some point to be able to fix them, but those > don't have to be done at the same time or even by the same person as > originally filing the bug. > > Cheers, > Maciej > > > > > Thanks! > > > > Dave > > > > > > On Jan 12, 2007, at 4:40 AM, Frederico Caldeira Knabben wrote: > > > >> It is really nice to see that FCKeditor is almost running with the > >> nightly. > >> There are still some bugs, and before I do any move, I would like > >> to be sure > >> this is something acceptable. > >> > >> I've always tried to create bug reports whithout associating them to > >> FCKeditor. I simply got a buggy thing in the editor, and reducted > >> it as much > >> as possible to generate precise reports. > >> > >> All we know how reductions are important. And we also know that their > >> creation take a lot of time. So, the report of bugs were going > >> pretty slow. > >> > >> I've noted instead that, for the TinyMCE editor, there are many > >> generic bugs > >> strictly specifying TinyMCE compatibility. Something like > >> "TinyMCE: Format > >> pulldown doesn't work". Those reports have not so much > >> information. Many > >> times just a line of descrition of the bug. > >> > >> I have a list of bugs of FCKeditor with Safari. Should I start > >> filling > >> simple "FCKeditor: ..." reports for all of them? > >> > >> In these way we would all have a clear compatibility status, and > >> in the mean > >> time myself, and others interested would be working for the > >> regressions. > >> > >> Thanks for the information, > >> FredCK > >> > >> PS: The following are the current known bugs: > >> > >> - links are clickable in the editing area > >> - the "Save" button doesn't update the hidden field before posting > >> - bogus remain in the code > >> - "Templates" doesn't work when inserting in the cursor position > >> - paste buttons are always disabled > >> - find dialog doesn't work > >> - "Remove Format" button adds Apple tag to the code > >> - enter key inside forms create further forms. > >> - hidden fields doesn't show up > >> - when formatting > >> - , and have id="undefined" > >> - the "Link" dialog is not loading correctly > >> - objects are not selectable and dragable > >> - "Insert Special Char" doesn't work > >> - the "Size" toolbar combo has no effect in text > >> - panels on toolbar items are positioned wrongly > >> - panels are not hidden when clicking outside them > >> - context menu icons are not showing > >> - tables are compressed on creation > >> - form fields are enabled in the editing area > > > > ___ > > webkit-dev mailing list > > webkit-dev@lists.webkit.org > > http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Reporting FCKeditor related bugs
Fred, if you need any help with Bugzilla or reducing bugs, let me know, i'd love to see your editor working! Regards, Joost On Jan 13, 2007, at 12:36 AM, Maciej Stachowiak wrote: On Jan 12, 2007, at 6:36 AM, David D. Kilzer wrote: Hi FredCK, I'd recommend filing all of the bugs. That way if someone else gets the notion to create a reduced test case or fix the bug, that's less work you'll have to do in the long run! Please do a cursory search for existing bugs before filing new ones as well. For example, "links are clickable in the editing area" may be similar to Bug 11297. (It took me three searches to find that one, though, so don't spend all your time search for pre- existing bugs!) It's better to have the bugs documented and later marked RESOLVED/DUPLICATE than to not have them documented at all. http://bugs.webkit.org/show_bug.cgi?id=11297 I agree with Dave's suggestion. Having the bugs filed is more important than level of detail in the bug. We will likely need reductions for these at some point to be able to fix them, but those don't have to be done at the same time or even by the same person as originally filing the bug. Cheers, Maciej Thanks! Dave On Jan 12, 2007, at 4:40 AM, Frederico Caldeira Knabben wrote: It is really nice to see that FCKeditor is almost running with the nightly. There are still some bugs, and before I do any move, I would like to be sure this is something acceptable. I've always tried to create bug reports whithout associating them to FCKeditor. I simply got a buggy thing in the editor, and reducted it as much as possible to generate precise reports. All we know how reductions are important. And we also know that their creation take a lot of time. So, the report of bugs were going pretty slow. I've noted instead that, for the TinyMCE editor, there are many generic bugs strictly specifying TinyMCE compatibility. Something like "TinyMCE: Format pulldown doesn't work". Those reports have not so much information. Many times just a line of descrition of the bug. I have a list of bugs of FCKeditor with Safari. Should I start filling simple "FCKeditor: ..." reports for all of them? In these way we would all have a clear compatibility status, and in the mean time myself, and others interested would be working for the regressions. Thanks for the information, FredCK PS: The following are the current known bugs: - links are clickable in the editing area - the "Save" button doesn't update the hidden field before posting - bogus remain in the code - "Templates" doesn't work when inserting in the cursor position - paste buttons are always disabled - find dialog doesn't work - "Remove Format" button adds Apple tag to the code - enter key inside forms create further forms. - hidden fields doesn't show up - when formatting - , and have id="undefined" - the "Link" dialog is not loading correctly - objects are not selectable and dragable - "Insert Special Char" doesn't work - the "Size" toolbar combo has no effect in text - panels on toolbar items are positioned wrongly - panels are not hidden when clicking outside them - context menu icons are not showing - tables are compressed on creation - form fields are enabled in the editing area ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev Joost 'AlthA' de Valk [EMAIL PROTECTED] ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Reporting FCKeditor related bugs
On Jan 12, 2007, at 6:36 AM, David D. Kilzer wrote: Hi FredCK, I'd recommend filing all of the bugs. That way if someone else gets the notion to create a reduced test case or fix the bug, that's less work you'll have to do in the long run! Please do a cursory search for existing bugs before filing new ones as well. For example, "links are clickable in the editing area" may be similar to Bug 11297. (It took me three searches to find that one, though, so don't spend all your time search for pre- existing bugs!) It's better to have the bugs documented and later marked RESOLVED/DUPLICATE than to not have them documented at all. http://bugs.webkit.org/show_bug.cgi?id=11297 I agree with Dave's suggestion. Having the bugs filed is more important than level of detail in the bug. We will likely need reductions for these at some point to be able to fix them, but those don't have to be done at the same time or even by the same person as originally filing the bug. Cheers, Maciej Thanks! Dave On Jan 12, 2007, at 4:40 AM, Frederico Caldeira Knabben wrote: It is really nice to see that FCKeditor is almost running with the nightly. There are still some bugs, and before I do any move, I would like to be sure this is something acceptable. I've always tried to create bug reports whithout associating them to FCKeditor. I simply got a buggy thing in the editor, and reducted it as much as possible to generate precise reports. All we know how reductions are important. And we also know that their creation take a lot of time. So, the report of bugs were going pretty slow. I've noted instead that, for the TinyMCE editor, there are many generic bugs strictly specifying TinyMCE compatibility. Something like "TinyMCE: Format pulldown doesn't work". Those reports have not so much information. Many times just a line of descrition of the bug. I have a list of bugs of FCKeditor with Safari. Should I start filling simple "FCKeditor: ..." reports for all of them? In these way we would all have a clear compatibility status, and in the mean time myself, and others interested would be working for the regressions. Thanks for the information, FredCK PS: The following are the current known bugs: - links are clickable in the editing area - the "Save" button doesn't update the hidden field before posting - bogus remain in the code - "Templates" doesn't work when inserting in the cursor position - paste buttons are always disabled - find dialog doesn't work - "Remove Format" button adds Apple tag to the code - enter key inside forms create further forms. - hidden fields doesn't show up - when formatting - , and have id="undefined" - the "Link" dialog is not loading correctly - objects are not selectable and dragable - "Insert Special Char" doesn't work - the "Size" toolbar combo has no effect in text - panels on toolbar items are positioned wrongly - panels are not hidden when clicking outside them - context menu icons are not showing - tables are compressed on creation - form fields are enabled in the editing area ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
RE: [webkit-dev] Reporting FCKeditor related bugs
Hi David, Thanks a lot for the precision. I'll proceed with it, taking care to avoid duplicates whenever possible. Best regards, Frederico Caldeira Knabben http://www.fckeditor.net "Support Open Source Software" > -Original Message- > From: David D. Kilzer [mailto:[EMAIL PROTECTED] > Sent: Friday, January 12, 2007 3:37 PM > To: Frederico Caldeira Knabben > Cc: webkit-dev@lists.webkit.org > Subject: Re: [webkit-dev] Reporting FCKeditor related bugs > > Hi FredCK, > > I'd recommend filing all of the bugs. That way if someone else gets > the notion to create a reduced test case or fix the bug, that's less > work you'll have to do in the long run! > > Please do a cursory search for existing bugs before filing new ones > as well. For example, "links are clickable in the editing area" may > be similar to Bug 11297. (It took me three searches to find that > one, though, so don't spend all your time search for pre-existing > bugs!) It's better to have the bugs documented and later marked > RESOLVED/DUPLICATE than to not have them documented at all. > > http://bugs.webkit.org/show_bug.cgi?id=11297 > > Thanks! > > Dave > > > On Jan 12, 2007, at 4:40 AM, Frederico Caldeira Knabben wrote: > > > It is really nice to see that FCKeditor is almost running with the > > nightly. > > There are still some bugs, and before I do any move, I would like > > to be sure > > this is something acceptable. > > > > I've always tried to create bug reports whithout associating them to > > FCKeditor. I simply got a buggy thing in the editor, and reducted > > it as much > > as possible to generate precise reports. > > > > All we know how reductions are important. And we also know that their > > creation take a lot of time. So, the report of bugs were going > > pretty slow. > > > > I've noted instead that, for the TinyMCE editor, there are many > > generic bugs > > strictly specifying TinyMCE compatibility. Something like "TinyMCE: > > Format > > pulldown doesn't work". Those reports have not so much information. > > Many > > times just a line of descrition of the bug. > > > > I have a list of bugs of FCKeditor with Safari. Should I start filling > > simple "FCKeditor: ..." reports for all of them? > > > > In these way we would all have a clear compatibility status, and in > > the mean > > time myself, and others interested would be working for the > > regressions. > > > > Thanks for the information, > > FredCK > > > > PS: The following are the current known bugs: > > > > - links are clickable in the editing area > > - the "Save" button doesn't update the hidden field before posting > > - bogus remain in the code > > - "Templates" doesn't work when inserting in the cursor position > > - paste buttons are always disabled > > - find dialog doesn't work > > - "Remove Format" button adds Apple tag to the code > > - enter key inside forms create further forms. > > - hidden fields doesn't show up > > - when formatting > > - , and have id="undefined" > > - the "Link" dialog is not loading correctly > > - objects are not selectable and dragable > > - "Insert Special Char" doesn't work > > - the "Size" toolbar combo has no effect in text > > - panels on toolbar items are positioned wrongly > > - panels are not hidden when clicking outside them > > - context menu icons are not showing > > - tables are compressed on creation > > - form fields are enabled in the editing area ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Reporting FCKeditor related bugs
Hi FredCK, I'd recommend filing all of the bugs. That way if someone else gets the notion to create a reduced test case or fix the bug, that's less work you'll have to do in the long run! Please do a cursory search for existing bugs before filing new ones as well. For example, "links are clickable in the editing area" may be similar to Bug 11297. (It took me three searches to find that one, though, so don't spend all your time search for pre-existing bugs!) It's better to have the bugs documented and later marked RESOLVED/DUPLICATE than to not have them documented at all. http://bugs.webkit.org/show_bug.cgi?id=11297 Thanks! Dave On Jan 12, 2007, at 4:40 AM, Frederico Caldeira Knabben wrote: It is really nice to see that FCKeditor is almost running with the nightly. There are still some bugs, and before I do any move, I would like to be sure this is something acceptable. I've always tried to create bug reports whithout associating them to FCKeditor. I simply got a buggy thing in the editor, and reducted it as much as possible to generate precise reports. All we know how reductions are important. And we also know that their creation take a lot of time. So, the report of bugs were going pretty slow. I've noted instead that, for the TinyMCE editor, there are many generic bugs strictly specifying TinyMCE compatibility. Something like "TinyMCE: Format pulldown doesn't work". Those reports have not so much information. Many times just a line of descrition of the bug. I have a list of bugs of FCKeditor with Safari. Should I start filling simple "FCKeditor: ..." reports for all of them? In these way we would all have a clear compatibility status, and in the mean time myself, and others interested would be working for the regressions. Thanks for the information, FredCK PS: The following are the current known bugs: - links are clickable in the editing area - the "Save" button doesn't update the hidden field before posting - bogus remain in the code - "Templates" doesn't work when inserting in the cursor position - paste buttons are always disabled - find dialog doesn't work - "Remove Format" button adds Apple tag to the code - enter key inside forms create further forms. - hidden fields doesn't show up - when formatting - , and have id="undefined" - the "Link" dialog is not loading correctly - objects are not selectable and dragable - "Insert Special Char" doesn't work - the "Size" toolbar combo has no effect in text - panels on toolbar items are positioned wrongly - panels are not hidden when clicking outside them - context menu icons are not showing - tables are compressed on creation - form fields are enabled in the editing area ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
