This inconsistency is confusing and could cause different behavior between scraping and interactive modes.
Discussion
The Chromium choice for interactive makes sense (better DevTools compatibility), but it should be documented. Consider adding a comment explaining the rationale, or unify to a single default.
**Parent:** #3
## Description
`NewBrowser()` in `playwright.go:91-97` defaults to **Firefox**:
```go
opt := mergeOptions(BrowserOptions{
Browser: BrowserFirefox,
// ...
}, opts)
```
But `NewInteractiveBrowser()` in `interactive.go:59-69` defaults to **Chromium**:
```go
opt := mergeOptions(BrowserOptions{
Browser: BrowserChromium,
// ...
}, opts)
```
This inconsistency is confusing and could cause different behavior between scraping and interactive modes.
## Discussion
The Chromium choice for interactive makes sense (better DevTools compatibility), but it should be documented. Consider adding a comment explaining the rationale, or unify to a single default.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent: #3
Description
NewBrowser()inplaywright.go:91-97defaults to Firefox:But
NewInteractiveBrowser()ininteractive.go:59-69defaults to Chromium:This inconsistency is confusing and could cause different behavior between scraping and interactive modes.
Discussion
The Chromium choice for interactive makes sense (better DevTools compatibility), but it should be documented. Consider adding a comment explaining the rationale, or unify to a single default.
Starting work on this as part of PR 7 (also includes #16). Will align
NewInteractiveBrowserdefault from Chromium to Firefox to matchNewBrowser.Work finished. PR: #38 (merged)
Aligned
NewInteractiveBrowserdefault from Chromium to Firefox.