Hi Petr, On Monday 19 October 2009 Petr Kobalíček wrote: > My post was mainly inspired by WONTFIX status of some of my bug > reports related to HtmlArea. It's few days I decided to report really > all problems I will find in qooxdoo and HtmlArea. Nice to hear that. Every bug report is welcome.
> With HtmlArea I had problems all the time, it's one year I wanted to use it > and I decided that it's not ready, so I waited, waited, waited ... it was at > Nov-2008. Currently there 4 bugs (with counting of #2954) which are reported by you. These bug reports are mainly (3 of them) targeted at the CSS styling which are the content receives by the HtmlArea and how the control is over the content. Sure, these are valid issues, but none of them are a show stopper in my opinion. > Yesterday I reported some issues but Alex told me that it is > not problem in HtmlArea but browser (I complained about html output, > exactly html styles set in <p> element is really not good). Maybe not "really good", but it's valid HTML. > When I found bug in HtmlArea I'm always trying other solutions (tinymce, > fckeditor, ...) to check if other devs solved it or not (and they > usually did). TinyMCE for example uses "b" elements to style bold text in Firefox 3.5 and no CSS styles at all. And CKEditor uses "string" element on newly created paragraphs. No judgement here, just the facts. I mean, every approach has it's pros and cons and their technical background. > If you look into HtmlArea code that it's code full of hacks, browser > specific workarounds, etc... This is really painful area in the web > universe, but it needs to be solved - by HtmlArea or by other > solution. Yes, there are hacks and I think we all would love to seem disappear and replaced by a clean solution. The thing is that sometimes they are necessary because some browsers are acting weird. And that's also the reason of browser specific workarounds. Anyway, if you localize any hack which can be replaced by a more clean solution, let us know and file a bug report (maybe even with a patch) to hunt them down. > Personally I don't need advanced undo/redo and zillion of > possibilities, I need stable and excellent support for basic editing - > Headings, Paragraphs and some styles that users can use to beautify > the text:) You can easily disable Undo/Redo with the property "useUndoRedo". The HtmlArea is only the editing component. If you only want to offer basic editing features you can create a basic toolbar. Headings for example are indeed not supported yet. Feel free to open a bug report for this feature. > And your issue is interesting, I'm using HtmlArea in modal dialogs and > I haven't problem with focus (only that I can't focus by TAB), but I'm > testing only in Firefox and Chromium. But I think that this bug is > solvable:) It's filed under http://bugzilla.qooxdoo.org/show_bug.cgi?id=2942 cheers, Alex ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
