[webkit-dev] SVG external referencing not working as of latest chrome canary

[Filip Pizlo]

Sent from my PDP-11

On Jan 14, 2013, at 12:51 AM, Steve Williams <stephen.j.h.williams at googlemail.com> wrote:

> Hi Maciej,
> 
> 1.  It's been on your bug database for ages hence filing another entry won't move anything forwards.
> 2. svg 1.1 spec seems a little over the top in places so not personally interested in full support - just the good stuff.
> 3. Have provided you with a minimal test case in the previous post.
> 4. "Cite real-world sites using the functionality to the relevant bugs."
> 
> ????? chicken and egg. that's not how we make progress ! I'll use it in our site when it works but can't until it does. 
> For now I have to iframe as a workaround but that sucks because iframes grab the entire rect for mouse input which means you can't subtly blend svg over html.

While step (4) is helpful, it is not a necessary prerequisite for a bug to be filed, assigned to the relevant people, and fixed. We understand and appreciate the chicken-and-egg problem you speak of. ;-) 

I think the point is that if you know of a site that uses SVG and the site doesn't work right in WebKit, then this is a highly relevant piece of information to put in the bug report. 

> 
> 5. Like you, I am busy. I don't have time to fix this (really). Sorry,  appreciate you don't like that but it is what it is. 

We're all busy. ;-)

> 
> 6. Would be great if this could be advanced in priority to enable us to raise the bar, cross browser.

The act of filing bugs is a pretty good way of raising the priority. 

> 
> Am sure you won't appreciate this fired back at the mailing list & I realise I'm risking a ban when you've asked me not to do this, but I'm a bit of a rebel :)
> 
> Thanks for all your hard work.
> 
> FF has svg bugs too - different (lower priority niggles). Will go hassle them next. IE9 a bit wobbly too, but well ... :)
> 
> If basic support can be solidified cross browser, we have an interesting platform over & above html5.
> 
> Best regards,
> Steve.
> 
> On 13/01/2013 21:37, Maciej Stachowiak wrote:
>> 
>> Hi Steve,
>> 
>> If you're interested in more complete SVG support, here are some things you can do:
>> 
>> (1) File bugs for any missing features that don't have bugs already.
>> (2) Create a meta-bug for "complete SVG 1.1 support" or what have you that's blocked by all the relevant feature bugs.
>> (3) Add useful reduced test cases to the relevant bugs.
>> (4) Cite real-world sites using the functionality to the relevant bugs.
>> (5) Work on implementing some of these features yourself.
>> (6) Persuade WebKit hackers that you know (offlist) to work on some of these features.
>> (7) Contact one of the vendors that works on WebKit via their developer relations channels and ask them to implement the features you care about.
>> 
>> If you are interested in more complete SVG support, I encourage you to do some or all of these things.
>> 
>> Note, however, that posting feature requests or advocacy for specific bugs is not really appropriate for this list. It's for talking about the development of WebKit itself, and no one uses         requests on this list as a way to drive priorities.
>> 
>> I'm glad to see you are interested in WebKit's SVG support and I hope you will consider some of the possible steps above to improve it.
>> 
>> Cheers,
>> Maciej
>> 
>> On Jan 13, 2013, at 8:37 AM, Steve Williams <stephen.j.h.williams at googlemail.com> wrote:
>> 
>>> Hi all,
>>> 
>>>  
>>>    I've done a little experimenting to see where we're at wrt to svg feature set and it seems webkit is lagging some way behind gecko.
>>> 
>>> Of particular concern is lack of external referencing capability through the svg use tag.
>>> 
>>> I attach a simple example that works in firefox for your consideration.
>>> 
>>> root.svg should link through to object.svg and render it.
>>> 
>>> It doesn't in latest chrome canary. You've had a bug filed on this for a long time but it's still unresolved so thought I'd mail.
>>> 
>>> https://bugs.webkit.org/show_bug.cgi?id=12499
>>> 
>>> 
>>> "We are lowering the priority because this is not heavily used." 
>>> The feature is not used heavily because it doesn't work properly.
>>> Never use lack of use as a reason to not do something :)
>>> 
>>> SVG is important because it's the lowest common denominator high spec graphics interface across all major browsers. Looks like you're behind ie9 in terms of implementation. You should at least match their implementation so we can raise the bar. Of course IE should implement webgl but until they do SVG is the best we've got across all mainstream browsers.
>>> 
>>> Thanks in advance for your consideration.
>>> 
>>> webkit is behind the curve in implementation of this web standard - please address this.
>>> 
>>> Best regards,
>>> Steve Williams
>>> <root.svg><object.svg>_______________________________________________
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org
>>> http://lists.webkit.org/mailman/listinfo/webkit-dev
> 
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20130114/1bc080ee/attachment.html>