Move Goja entirely out of the business logic

[inancgumus]

What?

Move Goja entirely out of the business logic.

Why?

• Prevent Goja data races.
• Better type-safety using native Go constructs.
• Developer productivity increase.
• Separation of concerns.
• Moving Goja handling to the mapping layer will make the code easy to reason about, reduce the business logic's Goja dependency, and simplify the business logic code and tests.
• Having Goja in the business logic requires constant encoding and decoding.

Tasks

Tasks

Beta Give feedback

1. Refactor goja out of screenshots and byte pointer changes #1198
   +0
2. Refactor goja out of browserContext.addinitscript #1228
   +0
3. De-gojaify Browser methods? (these are not meant to be mapped) #1269
   +0
4. De-gojaify BrowserContext methods #1270
   +0
5. De-gojaify ElementHandle methods (maybe we should split this more?) #1272
   +0
6. De-gojaify Frame methods #1271
   +0
7. De-gojaify Page methods #1273
   +0
8. De-gojaify Locator methods #1274
   +0
9. De-gojaify Request methods #1275
   +0
10. De-gojaify Response methods #1276
    +0
11. De-gojaify Keyboard methods (move them to the mapping?) #1277
    +0
12. De-gojaify TouchScreen methods (move them to the mapping?) #1278
    +0
13. De-gojaify Worker methods #1280
    +0
14. De-gojaify Connection.Close method? #1281
    +0
15. Remove NetworkManager.ExtraHTTPHeaders that returns a goja.Value (an unused method)? #1282
    +0

Related PR(s)/Issue(s)

#271