Julian

kinda surprised i didn't stumble over this while looking at #320, #258, #262 (?). would you guess that this might fix these? i was under the impression that CORS adherence...

i'm a bit puzzled by these restrictions; if a request's "non-simple" headers cannot be modified after setting `no-cors`, should that not also include the `Authentication` field? if you have a...

the label and directory selector are ordered by last usage, that's true (and so by design). i suppose if you use a lot of different entries, it'd be more comfortable...

couple of points. 1. what version of qbt? the more recent versions require you to use the qbt-v2 client in the options. 2. the QBT code currently doesn't support sub-paths...

those requests look identical to me. weird. just updated to that same qbt version locally and the extension seems to have no issue with it. > Here's the full response...

for this particular use case, i'm guessing doing the open-in-new-tab route, as you chose, is the best option. [the code](https://github.com/bogenpirat/remote-torrent-adder/blob/master/miscapis/background.js#L53) for the new-tab grabbing functionality doesn't currently eat magnet links....

it's an idea. but it's a per-torrent setting, so we'd have to somehow copy the prompt that rutorrent has over to qbittorrent. i've been thinking of re-designing the per-torrent prompt...

for the record, here's a really dirty workaround for this particular situation making use of `onrendered`, centering the text per sub-bar. should be easy to extend for the left/right requirement....

other than the fact that chromium based browsers generally don't show notifications when they're (or some other app is) in full screen mode, nope