[Webkit-unassigned] [Bug 68916] New: [fileapi] WebKitFlags should not be constructable per Directories & System spec

[bugzilla-daemon at webkit.org]

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

           Summary: [fileapi] WebKitFlags should not be constructable per
                    Directories & System spec
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: adamk at chromium.org
                CC: arv at chromium.org, kinuko at chromium.org,
                    ericu at chromium.org, adamk at chromium.org


Per http://dev.w3.org/2009/dap/file-system/file-dir-sys.html#the-flags-interface, Flags is marked as [NoInterfaceObject], yet in Chromium WebKitFlags is a constructor hanging off of DOMWindow.  And there's custom V8 code that knows to transform a V8WebKitFlags into a WebKitFlags.

According to ericu, WebKitFlags shouldn't actually be constructable, so this bug just calls for deletion.  We shouldn't have to worry much about compat, since the normal use case is to just use an object literal in the API and the thing is vendor-prefixed anyway.

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