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

Resolve view_to_component limitations #269

Open
3 tasks
Archmonger opened this issue Dec 7, 2024 · 0 comments
Open
3 tasks

Resolve view_to_component limitations #269

Archmonger opened this issue Dec 7, 2024 · 0 comments

Comments

@Archmonger
Copy link
Contributor

Archmonger commented Dec 7, 2024

Current Situation and Proposed Actions

There are currently several limitations of using view_to_component.

  • Requires manual intervention to change HTTP methods to anything other than GET.
    • The initial HTTP request will probably always have to be GET, but it might be reasonable to automatically handle other kinds of HTTP methods depending on what the user clicked on.
    • Realistically, the end goal is to make view_to_component behave as similarly to an iframe as technologically possible.
  • ReactPy events cannot conveniently be attached to converted view HTML.
    • It might make sense to give the user some kind of interface to "query select" certain rendered items, and attach ReactPy event functions to them.
  • Has no option to automatically intercept click events from hyperlinks (such as <a href='example/'></a>).
    • All hyperlinks that point to the current domain should probably be intercepted by ReactPy and rendered via view_to_component.
    • Realistically, the end goal is to make view_to_component behave as similarly to an iframe as technologically possible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant