[Tracking] Web/Desktop - Browser Resizing

[trjExpensify]

Coming from here and here. Creating this parent tracker to house a growing list of issues related to resizing the browser.

As a next step, we'd like someone to own addressing the plan for tackling this holistically in NewDot, such that we don't piecemeal solving individual bugs that crop up and end up with a disjointed implementation.

In the thread we agreed this is pretty low value right now as it's relatively niche and not something we expect many customers in practice to do. Nevertheless, they are repeatable bugs and worth solving if someone has spare cycles outside of higher value issues.

Known Issues
#13912
#13929
#13945
#13879
#13959
#14128
#15768
#17752
#31503

[roryabraham]

Nice. As advocated in this thread, I think it would be great to enable landscape mode on mobile devices and tablets and support those aspect ratios as well.

[JmillsExpensify]

Interesting take. That definitely makes the project larger, but you make an good point that those are also just other aspect ratios.

[trjExpensify]

Yeah, do they need to come together? That's my question really.

[sketchydroide]

I think the resize part of it might be influenced byt the Navigation rework, since deciding what we show on a smaller screen cna be impacted by that work

[trjExpensify]

Oh hm yeah, maybe. Curious what @mountiny thinks about that sentiment given that he's very close to that project?

[mountiny]

We could hold on the navigation rework, there might be some change although after a quick look to some of the issues i am not completely sure it would be resolved.

But probably better to not spend much time on these if the situation could change after the navigation refactor

[JmillsExpensify]

Ugh, I guess that means I need to assign myself, along with the mountain of other navigation reboot issues. 😆

[JmillsExpensify]

Still held on navigation.

[MelvinBot]

Looks like something related to react-navigation may have been mentioned in this issue discussion.

As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.

Feel free to drop a note in #expensify-open-source with any questions.

[JmillsExpensify]

Still on hold.

[JmillsExpensify]

Coming off hold very soon!

[mountiny]

Added all the relevant issues to the https://github.com/orgs/Expensify/projects/39 and to those we need to go through and confirm if they are fixed are added to the TODO column.

[JmillsExpensify]

Still working to close the loop on these issues this week.

[JmillsExpensify]

Still trying to make time for this

[JmillsExpensify]

I'm going through the backlog of react navigation issues and this one is a doozy so I'm going to prioritize this one last.

[JmillsExpensify]

So with the reaction navigation project over, we need to decide if this is worth tackling right now. My first instinct is no, and that this should remain on HOLD.

[trjExpensify]

Yeah, I think that's fair. I kinda view it in the same bucket as the likes of supporting landscape for iPad etc.

[JmillsExpensify]

Yeah agreed. I think this is just not a priority.

[JmillsExpensify]

Very much not a priority still

[JmillsExpensify]

Still not a priority.

[JmillsExpensify]

Same

[JmillsExpensify]

My two cents is that we should really close this issue and related issues, as we're not planning to address it anytime soon.

[trjExpensify]

Yeah, makes sense. I agree this isn't a priority!

[JmillsExpensify]

Ok cool, thanks! I'll do the same in related issues.

[JmillsExpensify]

Also for posterity, I'm removing the HOLD given that the nav refactor has happened.