Thank you Coda! Love these improvements!
One thing to add:
After using this for a bit I would LOVE a keyboard shortcut to activate/deactivate the full screen mode. Its too much mouse movement to find the expand button, scroll through a roll, then find the expand button again.
Find myself just preferring small layout vs. having to move my mouse all around. Haha I know it sounds picky, but really messes with flow.
Is there a keyboard shortcut to do it already I just don’t know about?
This is an encouraging step in the right direction, thanks team!
However am I missing something or does the full-screen not give you any actual additional horizontal space within the layout? all the columns widths are preserved and I just get wide white margins on each side. Maybe it would have been better to call it focus mode 
?
Also, it doesn’t really play nice with Details Display which has its own full screen mode that preserves the navigation panel. I get that the new feature only affects the layout within the Details display, but this may not be obvious to all users.
Fullscreen is certainly nice, but 
all I want for Christmas is 
… in-canvas adjustable-width Details Display with conditional formatting and input validation! (and yes, I’m a greedy kid)
Being able to Unlock the document from a row detail is still sorely needed in modal and fullscreen views.
This is awesome 
Most people I work with tend to have issues finding the rows’ Expand button, so I usually add a button column with Activate(). Is there a similar formula for opening the row straight into full screen?
You can do some sneaky URL manipulation to force it: See doc below
Unfortunately, when I have done this in the past (in very similar circumstances) it opens within the same window though, and for some reason this button is opening it in a new tab?
Anyone else want to chime in if they have a way to open it in the same window?- its bothering me.
@Scott_Collier-Weir, if you create the Full View Row URL using this formula :
Concatenate(thisRow.Url().ToText(),"&view=full")
or this one
Format("{1}{2}",thisRow.Url(),"&view=full").ToText()
The Full view opens in the same page instead of a new tab 
… for some reasons …
(See the buttons Open 2 and Open 3 and the columns URL 2 and URL 3 in the copy I’ve made from your sample below 
)
Just in case : An editable version of this doc is available here 
Copy of OpenRow Fullscreen - Edit
Hi Pch, please set it to play mode.
Hmmm … I just checked @Tomislav_Mamic and it seems to already be in Play Mode …
Here’s another Copy of the sample in Edit Mode 
→ Copy of OpenRow Fullscreen - Edit
Great! I knew there was something fishy going on
Sorry for the naive question, but what is the added value in being able to display a table row in full screen mode?
As far as I’m concerned, the added value lies in a better UX when it comes to the upcoming “Canvas Columns” 
(which is part of Coda New Editor 
- Still in Beta)… But that’s just my humble opinion 
Ok, that makes sense.
Haven’t had the time for the block-party this time. Looking forward to these releases! I have been Coda advocate since beta in early 2018 and supporting them by paying for the service (this didn’t stop them from blocking my account after the above comment). I know that it’s not fair to expect them to do everything community wants but I have more than 40 frozen projects for which we used alternatives due to some seemingly simple and straightforward functionality. 1-2-3 years of waiting gets frustrating. As a project-, product manager and enterprenuer Coda could be a livesafer and I hope that what they are baking is finally going to help me use Coda more with external users. There are some great tweaks and workarounds from amasing people in this community but they are not stable and require often bug-fixing, so Codans need to handle these.
Some great updates today! Really valuable ones. And hope for some more in the security and publishing soon.
This is neat @Pch and @Scott_Collier-Weir. Strangely there seem to be a multiple “full view” modes. There’s this one, then there’s also a slightly different one (a little better I think) that you can get only by first viewing the table as detail view right on the canvas (not pop-up modal) and then clicking on the expand button from there.
Is there a URL shortcut to get to that second one as well, I wonder?
Hi @Stefan_Stoyanov, that’s quite a few projects to abandon. I’m curious could you provide an example of the deal-breakers you encountered? Thanks.
Hi Ed,
To give you a bit of background, we work with a lot of contributors - companies, individuals, state agencies, freelancers. It’s unlike having an internal team.
The positives in Coda are a lot and N1 are the formulas - I just love how easy it is to create a complex action.
Here are some of the limitations on top of my head which made us find alternatives:
The above are really important and in the discussions for 2+ years now. We got fed up with exposing our data, people messing up with columns, formulas, views. We lost suppliers and clients because we created docs which supposedly should’ve helped us streamline processes. Instead we spent the first 15 min. of every meeting explaining bugs and why that happened.
The below are somehow less important but still stumbling blocks for some of the abandoned projects:
I love some of the ideas that are here since the beginning and will continue to support Coda and Codans but making business is my main goal, not doing QA and experimenting. I have enough kid toys around me for that 
I need to see more stable releases with actual - wow, that really solved it 100%.
PS: I would be happy if Codans contribute with some replies and prove me wrong on the above 
Hi Stefan, thank you for the detailed information. You really listed some great pain points that need tackling. We haven’t been publishing or sharing docs much for our clients (we don’t have a strong need for this), but the locking & permissions issues are the most glaring that make it difficult to scale the use of Coda to larger applications / teams.
Now that the new editor is launching and the canvas column type have been added, I would love to see a roadmap of the next areas of focus and hope that permissions are central to that, along with a general focus on improving all the existing features instead of adding new ones.
But that is the difficulty with Coda - there are so many potential use cases and different people are going to have different deal breakers which makes prioritization a challenge. For example I’ve seen people upvote various blockers. To name a few:
Personally I haven’t noticed many bugs recently (web only), but we tend to go for a very minimal and out-of-the-box approach to doc structure and feature usage to avoid hitting edge cases or using tricky formulas that might break with UX or formula changes.
I would love to see a coda bug tracker or at least a way to know if a reported bug has been logged and what the status is of it, like what is available for many popular highly technical products.
I suspect we may need to transition to other solutions for certain needs if some of these critical issues aren’t tackled in the next year or two, but so far we are definitely enjoying the benefits of custom streamlined flows for our business without having to jump between various different products for different needs.
Hi Ed,
I agree that there are many use cases varying from a simple internal blog to an actual data-collecting website (especially if we add a layer of marketing). This makes it difficult to satisfy all needs, I get that. But some are really important and they are in this community discussions and suggestion box since 2018.
You are quite generous with “year or two” I start a new investment every second year, so this is like ages for a very much needed “remove the hyperlink so that people can’t see my data” change. The big guys (e.g. Google) are watching and they have an eye on all these Notion, Coda, Clickup, nTask, etc. I don’t like the big corps lack of flexibility but Data Studio and AppSheet cover some of the essential points missed by Coda.
Thanks for the nice conversation and hope you find the best tools for your adventures.
Very good discussions @Stefan_Stoyanov and @Ed_Liveikis. I love Coda and want to continue support it, and wish for its success. And I believe, it will do good for Coda if it embraced constructive feedbacks like yours, which may appear critical on the surface but has potential to make Coda more powerful and useful.
I’m also constantly looking at different solutions (Airtable, Notion, Smartsheet, etc.), and there are few wishes from Coda, the lack of which is still keeping me from implementing Coda for the corporate purpose.
Am excited about some of the features being planned and I have hope that they will look at the highly voted features/improvements/fixes that are pending for years.
Coda, we are well wishers and we still have hopes with you. Help us change our minds and make you the only thing we need.