abaevbog

For reference, I imagine it would look somewhat similar to this? I think we are running into a small issue of new buttons not looking very fitting into the existing...

Yeah, the border of the button was of the wrong color and I did make the dialog a bit too wide... There were a few other smaller things with spacing...

Chrome looks good to me now as well. Per https://github.com/zotero/safari-app-extension, do I need to be a part of the team to build and sign the safari extension? Sorry if that's...

Sounds good! Meanwhile, I added some final touches to remove unwanted spacing after buttons and to not show the "done" button unless target selector is expanded per https://github.com/zotero/zotero-connectors/pull/512#issuecomment-2364926136. I unintentionally...

> You should test the manifestv3 build on chrome. Gotcha, so from now on, I'll use `manifestv3` build folder for chrome but still `firefox` for firefox. > One more thing....

@adomasven, after the recent connector changes, we have a lot of conflicts here. Is it safe for me to look into rebasing this now? Or will there be more significant...

I tested this on Firefox and Chrome with and without the linked PR that passes sends the tags. Not sure what are the steps for building on Safari though

> Can we not detect it from mouse events, or maybe blur or something is called on click? That is the main limitation of using `input` with ``. The autocomplete...

The `datalist` does seem a bit too restrictive ... Even not being able to properly tell if the user clicked on an autocomplete suggestion is inconvenient. And we are at...

I re-pushed because there were too many differences with the first commit. I created a new component `` that's responsible for the entire tags-related area. It handles the autocomplete, focus/blur,...