Resolve `view_to_component` limitations
Opened this issue · 0 comments
Archmonger commented
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.
- The initial HTTP request will probably always have to be
- 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.
- All hyperlinks that point to the current domain should probably be intercepted by ReactPy and rendered via