Hi Richard, I'm rather clueless myself when it comes to submitting bug reports. Different browsers seem to have different methods, and then different cultures for dealing with them. Perhaps a common <bug> reporting spec that dictates how user agents should respond to users who think they find bugs? Of course since probably 98% of suspected bugs are user error, the implementer community would probably not be quick to embrace any standard which would strap their development teams with additional and standardized bureaucracy.
I am only after several years, becoming confident enough in my own reading of the SVG spec (and it is far simpler than the HTML5 spec) to understand things enough to diagnose a "bug" and figure out how to report it. Usually, I have found that I (like you) am just too busy to track down the problem, isolate it to a particular situation and then report it. Sometimes if you actually post the offensive code here (if it is small enough that people can read it) then somebody like Erik or Doug or Bjoern or a dozen others who really know this stuff will swoop in and diagnose it as a bug and actually file a bug report. Multiple uses within a clipPath, per se doesn't seem like it should be a problem. Take a look at http://srufaculty.sru.edu/david.dailey/svg/clipdrag12.svg in which content is added to a clippath-ed use through script (actually I rather forget quite what it is doing). When I first ran it in Safari a few months back , that browser rather humorously mishandled the clipPath's, so it could just be a version problem with WebKit. I'd suggest actually posting your simplified code all stripped down to the readable case, here, in hopes that the right person will actually have the time to be able to look into it. Different problems demand different "right people" and everyone's schedules allow funny bursts of energy at different times. Cross-compatability issues are among the most frustrating of problems, but then that's why we have a standard. I used to port GUI stuff from Sun 3 workstations running Solaris to Macs in the 1980's and oh my goodness, the web sure seems luxurious by contrast! Hang in there! David ----- Original Message ----- From: Richard Pearman To: [email protected] Sent: Thursday, September 04, 2008 6:14 PM Subject: [svg-developers] Re: Google Chrome - SVG support? Hi, OK I decided that a bug which stops most my comics from being viewed by Safari and Google Chrome was sufficiently important to develop a test case. I've uploaded this to the files as webkittest.svg. It seems that the problem is a clipPath with more than one use element referencing different paths. I don't know if multiple children of any type (or use elements referencing the same path - pressumably with a transform attribute on at least one of them) would have the same effect. This is rather anoying because it means I'll have to go through each file and combine paths or something but I'm not sure this will be easy (I know I have at least one file with a clipPath with two use elements referencing the same rect, one with a transform but there are problable some where I've applied the same filter to things with different fills or something). Richard Pearman http://www.pixelpalaces.com/ The next stage in the evolution of web comics: http://www.onlinecomics.net/pages/details/listing.php?comicID=4415 Read my Helium articles: http://www.helium.com/users/212199 South Alberta Cactus and succulent society: http://www.facebook.com/group.php?gid=20360241008 --- In [email protected], "Richard Pearman" <[EMAIL PROTECTED]> wrote: > > Hi, > > I've just checked it with the SVG parts of my web comic. > Unfortunately it refuses to display "Trial of Humanity" parts I to > VIII (this is most the comic to date) with a technical > sounding "Something went wrong" message. This wasn't a great > surprise because these same files crash Safari, which also uses > webkit but I suppose this suggests the problem is in Webkit rather > than how Safari uses it. > > I can't find a bug report page for Google Chrome. > > I know, perhaps I should develop test cases which demonstrate this > bug but I have other things to do with my time (these are complicated > files which more-or-less work in ASV 3, Firefox, Opera and Renesis). > I am working on a new test version of a new interface for my comic > and I'll try to get the bugs out of that (I think the Webkit problem > is due to the old version of the interface as the problem shows an > 100% correlation with files which use it). > > Richard Pearman http://www.pixelpalaces.com/ > The next stage in the evolution of web comics: > http://www.onlinecomics.net/pages/details/listing.php?comicID=4415 > Read my Helium articles: http://www.helium.com/users/212199 > South Alberta Cactus and succulent society: > http://www.facebook.com/group.php?gid=20360241008 [Non-text portions of this message have been removed] ------------------------------------ ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ----Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/svg-developers/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
