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

[bugzilla-daemon at webkit.org]

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

--- Comment #6 from mitz at webkit.org ---
(In reply to Wenson Hsieh from comment #5)
> (In reply to mitz from comment #4)
> > (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?
> 
> Ah, no, I misread your comment — I had thought that the method you proposed
> would return the attachment element it created, but it seems this is not the
> case.
> 
> On the topic of what happens if the img already has an attachment though...I
> think it should be a no-op? And we could call the method something like,
> "ensureAttachmentElement", which would return the attachment identifier of
> either an existing attachment element or a newly associated attachment
> element, if there was no existing attachment element.

Seems reasonable. I can’t think off the top of my head of a situation where a client would want to replace an img’s existing attachment, since they presumably own that attachment and can change it.

-- 
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/20180925/84792696/attachment-0001.html>