[meta] DOMWindow::m_securityOrigin must die
Created attachment 121574 [details] crazy large proof-of-concept
It's crazy that DOMWindow has its own secret version of m_securityOrigin. We should only have one canonical place to store that state (which is the SecurityContext base class). Unfortunately, removing this state triggers a massive yak shave to move a lot of bindings code away from using DOMWindow as a context object and towards using ScriptExecutionContext, which is the right thing anyway. I'll post the real patches on separate bugs that block this one.
I'm going to try this again. I'm going to take a somewhat long path to make this happen, but hopefully I'll improve a bunch of things about the bindings along the way.
As of <http://trac.webkit.org/changeset/125592>, DOMWindow::m_securityOrigin is now dead. I'm going to use this meta bug to various related cleanup patches now that we're "over the hump."
(In reply to comment #4) > As of <http://trac.webkit.org/changeset/125592>, DOMWindow::m_securityOrigin is now dead. I'm going to use this meta bug to various related cleanup patches now that we're "over the hump." Whoa.