5 ms·
I've been trying to contribute to playwright for years! All of my issues have been closed / rejected without much consideration because they're not part of the
by nikisweeting 1y ago
I've been trying to contribute to playwright for years! All of my issues have been closed / rejected without much consideration because they're not part of the core "QA testing" use-case that playwright is built for.
Personally have not found their team to be the easiest to work with on Github. I would've loved to use puppeteer instead, their team is quite reasonable but they abandoned their python bindings and we want to stay in python.
- hugs 1y agore: ms -- thank you for calling that out. i've been thinking we had been collectively sleepwalking into ms owning everything (again). they've owned everything once before -- it wasn't great! related side-note: have you had to interact with the core chrome / cdp devs?
- nikisweeting 1y agoChromium bug tracker is where issues go to die, but aside from that I've had nothing but lovely individual interactions with core chrome devs so far. The devtools frontend/protocol repo is definitely active and more approachable than Chromium itself. I have not spoken to people that work directly on CDP yet, but I believe we have a call with them soon!
- hugs 1y agoawesome! tell them there are dozens of python fans. dozens!
- gregpr07 1y agore side-note: if you know anyone who would be willing to interact connect me :)
- hugs 1y agoi was going to ask the same to you. :-) i'm just stubborn enough to find out, though. and i still have a few contacts at the googleplex...