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

Duncan Booth duncan.booth at suttoncourtenay.org.uk
Tue Jan 1 14:40:43 CET 2008


Jay Batson <batsonjay at mac.com> wrote:

> First, thanks for the update.
> 
> Second:
> On Dec 29, 2007, at 4:18 PM, Duncan Booth wrote:
>> 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
> (snip)
>> 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.
> 
> 
> So, I interpret this to say that the bottom line is Kupu "works  
> problematically" using Safari3+webkit.  However, what was less clear  
> is whether:
> - The "problematic" issues that remain are unresolvable until Apple  
> whacks their <span> stuff?
> - The problematic issues could be made to go away with programming  
> effort (which would presumably be backed out once Apple whacked their  
><span> stuff)?
> 
> ??

Yes, one of those.

The "problematic" issues are obscure until apple whacks their span stuff. 
i.e. there may or may not be further issues which just haven't been spotted 
yet.

The situation could undoubtedly be improved by programming effort, but 
since the webkit developers are working to fix their side of the problem 
there doesn't seem much point putting in excessive effort working round 
bugs which are due to go away soon in any case. I've improved the filtering 
on trunk so that when it filters out all the attributes on a span tag it 
can remove it entirely: that seems a useful improvement in any case.

Of course, if anyone else wants to put in further work on workarounds then 
they are most welcome.



More information about the kupu-dev mailing list