Alexander Prinzhorn

> So far, I've only encountered examples where they provide the possibility to switch between the two modalities through a button. Could you please share screenshots and name the tools?...

Are you aware of [`client_replay_concurrency`](https://docs.mitmproxy.org/stable/concepts-options/#client_replay_concurrency)? ```sh mitmproxy --set client_replay_concurrency=-1 ``` Keeping this open as a feature request to allow other values https://github.com/mitmproxy/mitmproxy/pull/4842/commits/15a300dc6ecca24ed847448ed3788680a092744c

Thanks for reporting this. Does this happen with the latest 10.1.1 as well?

unfortunately it works well in Firefox and Chrome and there's no Safari for Linux

We can write tests for this case. However, in general things like these can be fuzzed. I'm thinking about creating a list of behaviors an allowed props and then just...

When a new element with a layout behavior is attached we have another issue. `_render` is called immediately, because the parent guides-layout hasAlreadyNotifiedOnce. But rendering does not make sense at...

The interpolate behavior suffers from a similar timing issue. ```js this.connectTo('^guides-layout', this._createInterpolators.bind(this)); ``` For new elements `_createInterpolators` is called immediately. However, just because the layout engine did layout once doesn't...

In theory we could get rid of all these problems by recreating _everything_ when an element is added or removed. This way there would be a guarantee that everything is...

So far the fuzz tests I'm writing right now caught all of these 🙌

> So far the fuzz tests I'm writing right now caught all of these raised_hands Aaaand another one. I assume this happens when an element is added and removed from...