[Webkit-unassigned] [Bug 200037] Allow Clients to make an input field considered autofilled and secure while viewable

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Aug 6 13:39:59 PDT 2019


--- Comment #16 from Priyanka <pagarwal999 at apple.com> ---
(In reply to Daniel Bates from comment #15)
> (In reply to Daniel Bates from comment #13)
> > Comment on attachment 375633 [details]
> > Patch
> > 
> > I just realized that this patch does not handle the case where the field's
> > value changes programmatically. We need to patch up setValueFromRenderer()
> Actually, I'm not sure what you intended the behavior to be for this feature
> when this happens. Either need to patch up setValueFromRenderer () or code
> is okay as-is and you just need to explain in the ChangeLog why we don't
> need to touch setValueFromRenderer().

As per off-line discussion, behavior is intentional and WebCore ChangeLog updated to describe the reason why we don't change setValueFromRenderer.

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/20190806/6bc108b5/attachment.html>

More information about the webkit-unassigned mailing list