[Webkit-unassigned] [Bug 21826] New: Add accessor for SecurityOrigin::m_domainWasSetInDOM

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=21826

           Summary: Add accessor for SecurityOrigin::m_domainWasSetInDOM
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: abarth at webkit.org
                CC: sam at webkit.org


It will help Chromium unfork SecurityOrigin.cpp if we add an accessor for
SecurityOrigin::m_domainWasSetInDOM.  If this flag is false, Chromium can do a
same-origin check in one pointer comparison by atomizing the toString() of the
SecurityOrigin (with some other caveats).

Currently they have YASOTSF (Yet Another SecurityOrigin toString Function)
called SecurityOrigin::securityToken that knows about m_domainWasSetInDOM. 
Adding an accessor for m_domainWasSetInDOM seems better than adding this
function to our tree.

Now, if only I can get rid of the YASOTSF called
SecurityOrigin::databaseIdentifier, my plans for grand unification of the
SecurityOrigin toString methods will be complete!

Patch forthcoming.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.