This is an extension of the feature request: Admin Determines Column Width (Table View) but directed a discussion about the current setup in Fibery and what benefits, if any, can be had.
In short, table views in Fibery render with default settings for each user per browser. If you change the column widths, it only applies when you are signed in from that browser, as that user. This is quite a departure from industry standard, which is that field widths are stored as a part of the view configuration and all users experience the same setup on all devices.
I haven’t seen much explanation from the Fibery team explaining why this is, or if it’s intentional. But I also haven’t seen any plans to make changes. So, I’m wondering if there are any benefits/examples of how to leverage this?