Remove UsePointersEvenForNonNullableObjectArguments from DataTransfer
Created attachment 276221 [details] Patch
Comment on attachment 276221 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=276221&action=review > Source/WebCore/dom/DataTransfer.idl:41 > + void setDragImage(Element? image, long x, long y); Hmm, this does not match the spec: https://html.spec.whatwg.org/multipage/interaction.html#datatransfer
Comment on attachment 276221 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=276221&action=review >> Source/WebCore/dom/DataTransfer.idl:41 >> + void setDragImage(Element? image, long x, long y); > > Hmm, this does not match the spec: > https://html.spec.whatwg.org/multipage/interaction.html#datatransfer Our behavior of accepting null to mean we should remove/clear the drag image predates the spec by many years. It’s OK to change to match the specification, but we’d want to add regression tests and consider the backwards compatibility costs of making the change.
Maybe we should add a FIXME comment about matching the specification in the future?
(In reply to comment #4) > Maybe we should add a FIXME comment about matching the specification in the > future? Sound good to me.
Created attachment 276326 [details] Patch
Comment on attachment 276326 [details] Patch r=me
Comment on attachment 276326 [details] Patch Clearing flags on attachment: 276326 Committed r199500: <http://trac.webkit.org/changeset/199500>
All reviewed patches have been landed. Closing bug.