[kupu-dev] Safari - current state of issues?

[Duncan Booth]

Jay Batson <batsonjay at mac.com> wrote:

> So, two questions:
> - Has anybody looked at Safari / Kupu in the last several years to  
> know whether the previously-blocking issues are still blocking?

Yes.

> - Can somebody actually succinctly describe what the issues were /  
> are?  It wasn't immediately clear to me.  I'm looking for the level of  
> information that would help determine whether "It's basically not  
> possible," or "It's just a matter of doing a bunch of hard work, but  
> it can be done without massively rewriting Kupu."

It has been a slow process because until each major issue has been fixed 
the next issue doesn't become apparent. Initially the problem was lack of 
xsl support, then once that was fixed there were issues with Javascript 
regular expression support (fixed in October this year).

The main problem at present is that Safari inserts a lot of <span 
class="Apple-span-style"> tags every time you try to format anything (or 
even occasionally other things such as <font class="Apple-span-style">). 
The Safari developers are looking at this. This problem only seems to 
affect kupu as it happens when you try to edit html with css styling 
applied and I think Fckeditor etc. maybe don't apply css to the edit 
buffer.

Kupu now tries to filter these span tags out when saving, but it would be 
better if Safari didn't insert these at all: they do interfere with 
editing.

On Plone, kupu supports (i.e. is enabled for) recente versions of Safari 
3+webkit out of the box, however the remaining issues with Safari mean that 
actually using it is still somewhat problematic.