(In reply to Segun Famisa [:segun] from comment #14) > > > so we can call it when the list is changed > > Quick question about this part. Are we creating an API to be called when the login list changes, or when the content of the `<input>` changes? Let's start with when the content of the `<input>` is changed, if we feel we do need to optimize to only send the notification when list changed, we can update accordingly.
Bug 1890194 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Segun Famisa [:segun] from comment #14) > > > so we can call it when the list is changed > > Quick question about this part. Are we creating an API to be called when the login list changes, or when the content of the `<input>` changes? How about starting with when the content of the `<input>` is changed? If we feel we do need to optimize to only send the notification when list changed, we can update accordingly
(In reply to Segun Famisa [:segun] from comment #14) > > > so we can call it when the list is changed > > Quick question about this part. Are we creating an API to be called when the login list changes, or when the content of the `<input>` changes? How about starting with calling the API when the content of the `<input>` is changed? If we feel we do need to optimize to only send the notification when list changed, we can update accordingly
(In reply to Segun Famisa [:segun] from comment #14) > > > so we can call it when the list is changed > > Quick question about this part. Are we creating an API to be called when the login list changes, or when the content of the `<input>` changes? How about starting with calling the API when the content of the `<input>` is changed? If we feel we do need to optimize to only send the notification when list changed, we can update accordingly.