WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
CLOSED WORKSFORME
15419
Inspector throws "unsafe access" exceptions when inspecting SVGs with Drosera attached
https://bugs.webkit.org/show_bug.cgi?id=15419
Summary
Inspector throws "unsafe access" exceptions when inspecting SVGs with Drosera...
Eric Seidel (no email)
Reported
2007-10-07 21:19:55 PDT
Inspector throws "unsafe access" exceptions when inspecting SVGs with Drosera attached. I'm not sure this is an SVG specific issue, likely more a Drosera-being-attached issue. I don't see these exceptions when Drosera is not attached. (I see different exceptions: (event handler):Null value in the 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.
Attachments
Add attachment
proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1
2007-10-08 00:26:30 PDT
I no longer see these now that I've implemented getComputedStyle for SVG and thus no longer hit
bug 15348
(which was what was tripping me into the debugger, and thus revealing this error).
Adam Roben (:aroben)
Comment 2
2008-03-13 23:15:20 PDT
(In reply to
comment #1
)
> I no longer see these now that I've implemented getComputedStyle for SVG and > thus no longer hit
bug 15348
(which was what was tripping me into the debugger, > and thus revealing this error).
So should we close this bug?
Eric Seidel (no email)
Comment 3
2008-03-13 23:26:41 PDT
I expect that the security model w/ the inspector has changed enough so that this bug probably no longer exists.
Timothy Hatcher
Comment 4
2008-05-17 09:56:05 PDT
Closing since Drosera has been replaced by the new Web Inspector debugger. Moving to the New Bugs component so the Drosera component can be closed and removed.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug