Skip to content

1.32 dev #49

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

Open
wants to merge 52 commits into
base: 1.25
Choose a base branch
from
Open

1.32 dev #49

wants to merge 52 commits into from

Conversation

tmahmood
Copy link

@tmahmood tmahmood commented May 1, 2023

Hey @octaltree

I have updated playwright-rust to version 1.32-beta, and all the tests are passing, and I have not faced any issues in regular usages.

Additionally, I have replaced Mutex/MutexGuard with parking_lot

Please review and merge.

Thanks :-)

Tarin Mahmood and others added 21 commits August 20, 2022 21:29
… the deserializer. Adding serde default to the `params` field resolves that
1. Load
2. DOMContentLoaded
3. Request
4. Response
Small changes to make the tests run (Not all tests are passing)
Added mime_type
…sting file upload api. Which works upto 100MB

Will not work for remote playwright server. We can continue work on it later
# Conflicts:
#	scripts/Makefile
#	scripts/src/api.rs
#	scripts/src/generate_api.rs
#	src/imp/playwright.rs
#	src/protocol/generated.rs
ConsoleMessage structure was changed, which caused playwright to fail if there was any console messages.
Updated files required to update protocol
Fixed issue with press
Updated to latest 1.25 and fixed issue with not being able to spawn multiple playwright instances
…` panicked as browser is None. Now checking if browser is actually set.
ConsoleMessage structure was changed, which caused playwright to fail if there was any console messages.
@tmahmood tmahmood changed the base branch from master to 1.25 May 1, 2023 14:28
@d4h0
Copy link

d4h0 commented May 26, 2023

Hi @tmahmood,

First of all, thank you so much for your work on updating playwright-rust!

I'm thinking about porting my current chromiumoxide-based code to playwright-rust, and I have a few questions (I hope it's okay that I ask them here. Issues seem to be closed on your fork).

(1) I'm wondering if you intend to continue to (help to) maintain this crate (it wouldn't make sense, to switch to playwright-rust, if it will be outdated in a few months again).

If I remember correctly, @octaltree isn't using playwright-rust anymore himself, so it's completely understandable that he doesn't want to/can't spend too much time on it.

(2) Because you probably have a good understanding now, regarding how playwright-rust works, I'm wondering if there is any chance that you'd create (more) documentation about how to update/maintain it.

I tried a few times to get playwright usable from Rust, but (because of time-constraints) I wasn't able to finish anything, yet.

(So far I've tried to update playwright-rust, to create my own bindings via Node.js or Deno, to create Wasm bindings and use playwright from Wasm executing in Node.js).

I think, with such documentation it would be much easier for other interested people (to which I count myself) to contribute to playwright-rust, and help to keep it up-to-date.

Thanks again, for your work!

@tmahmood
Copy link
Author

Hey, @d4h0 ,

Glad to be of help 🙂

I can get some documentation up for upgrading. And I'll try to keep it uptodate regularly. But not sure how long I can continue

@d4h0
Copy link

d4h0 commented May 28, 2023

Thanks, @tmahmood, that sounds great!

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

Successfully merging this pull request may close these issues.

3 participants