Closed sirdarckcat closed 3 years ago
https://github.com/google/tamperchrome/commit/20d3870b1e91a3d9cab701d467604771977df563 makes this a lot faster, but it's still slow.
I tried to do virtual scroll https://github.com/google/tamperchrome/commit/3ab63005fa3884ba17294958a93b82540e8528bc but its still slow.
leaving it open
once the user selects the hex editor, the tab stays there for all requests, so it becomes slow. we should default to non-hex editor while its slow
some other ideas to make it faster:
One more idea is to render as text, and only when the user clicks or focuses it, transform a single char into input.
https://github.com/google/tamperchrome/commit/064105f072300ffe26f30ed0a6ccb5b60326637a is now constant regardless of the size of the body. this was achieved by making the input only render when selected (otherwise it is displayed as text), having a single scrolling element in a single virtual for loop.
it's still not super fast, though, but it's getting hard to make it faster now.
when a request body is very large, the request editor slows down the ui significantly.
we should delay rendering the component until the user selects the hex editor tab, and perhaps limit the number of inputs generated to the ones visible on the web view.