Support all browsers for our extension

[posix4e]

Currently we only support IOS. Let's support chrome. Let's provide tests,ci and cd

[kernel-loophole]

hi there ,this is zulqarnain from replit .I have some question about it .
What are the key features or functionalities that you would like to ensure work seamlessly in the Chrome version of the extension?
Are there specific aspects of the JavaScript codebase that need to be adapted for Chrome compatibility? Are there any iOS-specific features that need to be adjusted?
Looking forward to discuss more .

[posix4e]

I don’t think we should worry about breaking functionality. If it does break we should add a failing unit test . The existing logic is very trivial and only consists of a few html and js files. The real goal behind this issue is making a first stab on a working test and deploy framework

[kernel-loophole]

That's great.when you want this ready.

[posix4e]

When you can

[kernel-loophole]

2 weeks

[posix4e]

OkSent from my iPhoneOn Aug 19, 2023, at 22:19, Zulqarnain ***@***.***> wrote: 2 weeks —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[kernel-loophole]

great ,so i am sending proposal on replit .

[kernel-loophole]

can you accept my work on replit .

[posix4e]

You did tests, ci but not cd. You need to publish the extension as a zip file whenever a tag release event happens. Should be pretty easy now that we have ci working