[Webkit-unassigned] [Bug 189934] No DOM API to instantiate an attachment for an img element

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 24 16:00:58 PDT 2018


--- Comment #4 from mitz at webkit.org ---
(In reply to Wenson Hsieh from comment #2)
> (In reply to mitz from comment #0)
> > Given an img element that’s not backed by an attachment, there’s currently
> > no way to get it to be backed by an attachment. It would be useful to have a
> > function on HTMLImageElement that one could call from JavaScript that would
> > create a new attachment element, then call
> > HTMLImageElement::setAttachmentElement to associate the attachment with the
> > img. The caller could then use webkitAttachmentIdentifier to get the unique
> > identifier of the attachment that’s been created.
> Hm...I'm a bit more partial to adding a method to HTMLImageElement that
> ensures an attachment element, and returns just the attachment identifier so
> we don't need to worry about cases where a client could remove the
> attachment element of the image afterwards via script.

I am not sure how your proposal differs from what I described in comment #0. Is it about the behavior when the img already has an attachment?

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/20180924/ab3b0695/attachment.html>

More information about the webkit-unassigned mailing list