15348 2007-10-02 15:38:20 -0700 DOM Inspector hits exception when inspecting SVG 2007-10-26 00:05:31 -0700 1 1 1 Unclassified WebKit Web Inspector (Deprecated) 523.x (Safari 3) Mac OS X 10.4 RESOLVED FIXED http://www.croczilla.com/svg/samples/butterfly/butterfly.svg HasReduction P2 Normal --- 15422 1 eric webkit-unassigned oldest_to_newest 57676 0 eric 2007-10-02 15:38:20 -0700 DOM Inspector hits exception when inspecting SVG (event handler):Null value 1. Inspect the path element (click on the orange or black part of the butterfly. 2. click on the "svg" "tab" at the bottom of the source display (5-sided figure, square with attached triangle) 3. click on the "path" "tab" at the bottom of the source dispaly: 4. you'll see this exception: (event handler):Null value I assume this is actually a bug in the JS bindings for SVGElement and not a bug in the inspector, but it could be either... 57677 1 eric 2007-10-02 15:46:34 -0700 I cant seem to get Drosera to stop at the event handler null value. However, when I run Drosera I seem to get these additional logs in my console: Unsafe JavaScript attempt to access frame with URL http://www.croczilla.com/svg/samples/butterfly/butterfly.svg from frame with URL file:///Stuff/Users/eric/Projects/build/Debug/WebCore.framework/Resources/inspector/inspector.html. Domains must match. It seems strange to me that those only started after I launched Drosera, but perhaps I just missed them before. 58077 2 eric 2007-10-08 00:24:34 -0700 Turns out that the line having trouble was: if (!priorityUsed && style.getPropertyPriority(name).length) style.getPropertyPriority(name) was returning null, because name was null. Instead of fixing the JS, I implemented getComputedStyle for SVG, which stopped "name" from being null (at least for now). This isn't a full fix, but it solved my issue. If someone would like to make this hunk of inspector JS more robust, be my guess. I wasn't exactly sure what the "correct" behavior was when "name" was null. The security exceptions are covered by: http://bugs.webkit.org/show_bug.cgi?id=15419 58122 3 eric 2007-10-08 13:49:50 -0700 Now that bug 15422 is solved, it is not absolutely necessary to change this JS. But I leave that up to ya'll inspector folks to decide. If so, just close the bug. 59515 4 timothy 2007-10-26 00:05:31 -0700 I think this can be closed since it no longer happens.