Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BrowserTab - Quality Quest #12717

Open
18 tasks
sethkfman opened this issue Dec 16, 2024 · 1 comment · May be fixed by #12731
Open
18 tasks

BrowserTab - Quality Quest #12717

sethkfman opened this issue Dec 16, 2024 · 1 comment · May be fixed by #12731

Comments

@sethkfman
Copy link
Contributor

sethkfman commented Dec 16, 2024

What is this about?

This ticket summarizes the work for improving the BrowserTab functionality:

Pre-fix all branches associated with work

  • qq/browser-<work>

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

  • Engineering (needed in most cases)
  • Design
  • Product
  • QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
  • Security
  • Legal
  • Marketing
  • Management (please specify)
  • Other (please specify)

References

No response

@joaoloureirop
Copy link
Contributor

joaoloureirop commented Dec 20, 2024

TODO

  • test webview on iOS
  • test webview on Android
  • fix handleIpfsContent with ipfswayGatewayEnabled or not
  • fix account connect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@sethkfman @Cal-L @tommasini @joaoloureirop and others