@poeti8 commented on GitHub:
@abhijithvijayan any updates on this?
@enoy19 commented on GitHub:
my kutt works with 4 different domains. the default one and 3 extra. Do I need to reconfigure it to use one of the 3 custom domains? isnt that what the dropdown is for?
@poeti8 commented on GitHub:
You can use it if you have already installed it. I'll check with the issue myself soon, seems like @abhijithvijayan doesn't have free time.
@abhijithvijayan commented on GitHub:
Please acknowledge the above scenarios if it is right.
@abhijithvijayan commented on GitHub:
So the only problem now is, you are seeing empty strings in the dropdown for all the domains you have configured, right?
And you are able to shorten using…
@abhijithvijayan commented on GitHub:
Try validating the key once again or press the refresh icon in popup,
If it didnt work still, i will check
@brianantonelli commented on GitHub:
No, you can't use it just fine. It's missing from the store.
@poeti8 commented on GitHub:
Kutt is now back on Chrome Web Store: https://chrome.google.com/webstore/detail/kutt/pklakpjfiegjacoppcodencchehlfnpd
Firefox review is still pending.
@poeti8 commented on GitHub:
@abhijithvijayan That's good news. I appreciate the work you have done so far, but can we completely remove the build the step? I wouldn't want it any other way. Just…
@abhijithvijayan commented on GitHub:
I am re-writing the underlying repo https://github.com/abhijithvijayan/web-extension-starter to work with v3 manifest extensions. Will migrate this repo to…
@abhijithvijayan commented on GitHub:
Can you share a disposable credentials(api key & custom domain) for me to debug these?
Currently I dont have a custom host setup with custom domains.
@Lancaban commented on GitHub:
Any updates on this yet?
@enoy19 commented on GitHub:
So the only problem now is, you are seeing empty strings in the dropdown for all the domains you have configured, right?
And you are able to shorten using all…
@enoy19 commented on GitHub:
I tried refreshing but it didn't work. I also tried restarting chrome. didn't work either
@poeti8 commented on GitHub:
Any updates on this yet?
For FireFox? I submitted many times but each time they respond with something weird that I don't know how to fix. I should try again soon.
@mimalef70 commented on GitHub:
I fix this issue, it's because you use {option} to the select box; I fix this with this code in line 225 ( Form.tsx )
{domainOptions.map(({id, value,…
@abhijithvijayan commented on GitHub:
This was not exactly an issue with the libraries, it was because of chrome deprecating Manifest v2 way faster than other browsers leading to partial support.…