108906 2013-02-04 22:07:21 -0800 'dictionary' should be supported by WebKit IDL 2023-05-28 09:22:32 -0700 1 1 1 Unclassified WebKit WebCore JavaScript 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED P2 Normal --- 111911 1 haraken tonikitoo annevk ap a.renevier cdumez eoconnor haraken igor.oliveira laszlo.gombos tonikitoo oldest_to_newest 825136 0 haraken 2013-02-04 22:07:21 -0800 Web IDL spec: http://www.w3.org/TR/WebIDL/#idl-dictionaries Use cases: https://cvs.khronos.org/svn/repos/registry/trunk/public/webcl/spec/latest/index.html Currently 'dictionary' is parsed by IDLParser.pm but it is ignored by code generators. 825144 1 haraken 2013-02-04 22:15:54 -0800 FYI, there had been a plan to use 'dictionary' for event constructors. There should be other use cases in the future. 832703 2 tonikitoo 2013-02-13 20:36:11 -0800 Kentaro told me, @nbarth won't be able to work on this for now. Taking ... 938542 3 ap 2013-10-10 14:19:11 -0700 WebCrypto uses dictionaries too. That said, it seems unclear how "dictionary" is different from "interface", except for minor syntactic sugar. Can someone please explain? 938549 4 ap 2013-10-10 14:37:59 -0700 Or rather how it's different from Object, I guess. 938565 5 tonikitoo 2013-10-10 15:03:34 -0700 (In reply to comment #3) > WebCrypto uses dictionaries too. > > That said, it seems unclear how "dictionary" is different from "interface", except for minor syntactic sugar. Can someone please explain? That is a good question. I would say a 'dictionary' is the as a strong-typed 'interface with only read-only parameters'. For example: - in JS: var a = {x: bleh, y: blah}; - in c++: the dictionary would have "x" member variable defined whose type is a Bleh class. IDL would have something like: dictionary Foo { Bleh x; Blah y; } Based on the, the the binding could do the casts needed. Please correct if I am wrong. It lacks a formal definition in WebIDL as far as I can tell. 1958524 6 annevk 2023-05-28 09:22:32 -0700 Looking at how this works for addEventListener() this appears to be resolved.