Open Pashaminkovsky opened 6 days ago
Adding "specification required flag" because, as per the discussions/proposal we don't have a technical workaround for this. So it needs clarification before engineering picks it up
One option that has been floated is to open the sidebar on all tabs (i.e., keep it globally open) to avoid having to reopen it. But that solution may not be suitable
Another option would be to re-add support for an embedded sidebar (aka MV2 sidebar) to better support these use cases
@mthek10 would either of the workarounds that Todd mentioned^ suffice in the meantime?
@twschiller can you share documentation so I can read up on the MV2 embedded sidebar?
@twschiller can you share documentation so I can read up on the MV2 embedded sidebar?
The MV2 sidebar isn't a Chrome affordance. It was a sidebar we implemented. It injects a frame into the page and attempts (sometimes unsuccessfully, due to absolute element positioning) to shift the main content over
You can find videos of the old behavior on our YouTube channel: https://www.youtube.com/watch?v=iL7IXGFt1Ys
Next steps: @Pashaminkovsky to sync w/ @mthek10 on what we can do here
MV3 requires a user gesture before opening the sidepanel. This is causing friction with a number of use cases (e.g. compliance).
This was available in MV2 but broke in MV3. Are there any workarounds to the user gesture requirement that we can implement?
Relevant discussions: