[webkit-dev] Nominate Vox.com Compose to Webkit Compatibility Hit
David D. Kilzer
ddkilzer at kilzer.net
Wed Dec 13 03:44:42 PST 2006
As Mark Rowe noted in the comments for Bug 10165, the best approach
to getting the rich text/wysiwyg editor used by VOX to work with
WebKit is to file individual bugs for specific bugs, then make these
new bugs depend on Bug 10165. The other helpful thing to do is to
reduce each of these isolated bugs to a test case that reproduces the
In general, there have been a large number of fixes for other rich
text editors for WebKit this year, and many times a fix for one will
fix others as well. That means that VOX's editor may be (much?)
closer to working now than when Bug 10165 was originally reported.
On Dec 12, 2006, at 9:58 PM, Shawn Smith wrote:
> The VOX (www.vox.com) social network tool does not support Safari
> within it's compose feature. A bug was opened ( http://
> bugs.webkit.org/show_bug.cgi?id=10165 ) which provides some detail
> related to the VOX issues on Safari.
> I suspected that this would quickly get evaluated and commented on
> by a webkit developer but not much has happened to it. How does a
> site compatibility issue make its way to the Compatibly Hit List?
> I have not seen that list get updated in some time?
> The Vox product manager made statements that the next version of
> Safari in Leopard was going to solve the HTML editor issues in the
> compose function and to try out webkit nightlies to see progress.
> So far I have not seen any progress, or even bugs being fixed which
> address the issues?
> The Vox post about safari problems is here:
> Thanks for your help and consideration of this issue.
> Shawn Smith
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev