tselit

The majority of this work will be more about testing. We're anticipating covering the following test scenarios, to get ready for alpha: - page with single iframe (then with one...

Decided on 24 April that to handle limiting the scope for the alpha build as follows: - Only evaluate/inspect the first link tag we encounter in the iframe. - If...

What remains is to implement the following (estimate 8 hrs to have this ready for review): ensuring that the WM icon display is correctly updated when a website has iframes,...

Please expand on the context & description @raducristianpopa (this update is also low priority)

Prioritising compatibility for Chrome first. Agreed to work on compatibility for other engines after work-week.

Diana will investigate the approach that we'll need to ensure that the extension's polyfill capability is secure once we are MV3 compatible There seems to be an issue with Firefox...

> Another difference we need to handle: By default, MV3 disables our all hosts permissions. That's something we need to request user, otherwise much of the extension won't work -...

> Question: @tselit @ioana-chiorean @raducristianpopa @dianafulga Should we remove manifest v2 support, or continue to support it? I found extension worked fine with Firefox MV3. Thanks @sidvishnoi...it's interesting to hear...

Ready to merge. Further discussion/consideration about the UI design/composition to address the issue with the scroll bar. The other consideration (also a separate ticket) would be possibly overhauling the entire...

**Update on 30 Apr**: the background functionality for once-off payments is working, but feedback to the user on the extension's pop-up that the payment was successful is, not implemented yet....