[Webkit-unassigned] [Bug 177722] New: Support nullable and optional interfaces as members of a dictionary

[bugzilla-daemon at webkit.org]

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

            Bug ID: 177722
           Summary: Support nullable and optional interfaces as members of
                    a dictionary
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Bindings
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sam at webkit.org
                CC: cdumez at apple.com

We currently treat a nullable interface that is an non-required member of a dictionary, just like we would a non-nullable interface that is an non-required member of a dictionary. That is for,

interface Test {
}

dictionary Foo {
    Test? test;
}

dictionary Bar {
    Test test;
}

Foo and Bar have the same backing struct:

struct Foo/Bar {
    RefPtr<Test> test;
}

To implement abort support for Fetch, we need to be able to distinguish these two cases to support the signal member on RequestInit (https://fetch.spec.whatwg.org/#requestinit) where differentiating between null and not-present is observable.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171001/10e8ebea/attachment-0001.html>