The fact it has no borders in "full screen mode" is really disorientating. I like the concept but wouldn't use it because of the loss of visual feedback (but full screen mode is optional which is fine).
As an aside: It is a shame this "breaks" Chrome's ability to let you re-scale the non-full-screen box. So it is an all or nothing choice, you have to give up something to get something...
It looks like you disabled Chrome's resizing on purpose too, which seems unnecessary/annoying. Why break existing functionality just to add new functionality?
>It looks like you disabled Chrome's resizing on purpose too, which seems unnecessary/annoying. Why break existing functionality just to add new functionality?
That functionality can be re-enabled by changing the "resize" CSS style[0].
From a quick look, it looks like it's reasonably simple to add resizing back in. The CSS on the textarea has resize:none - removing that and removing the max-width should add that functionality back in, should you want it.
It should be trivial to get the resize functionality back. I think in cases like this breaking existing functionality is fine. This is obviously aimed at people with a relatively narrow use-case in mind. In a situation where the purpose of full screen mode is to remove the distractions of the surrounding document this seems fine. I personally would want my text box at a fixed size on some forms with the option to make it the only thing on the page (case in point is my own app https://writeapp.me [yes, an account is needed to see the text box]) so as to keep the design from breaking (it's a very opinionated page when it comes to design).
I think overall this is an improvement to text boxes generally which is why I can forgive the breakage of one bit of existing functionality.
As an aside: It is a shame this "breaks" Chrome's ability to let you re-scale the non-full-screen box. So it is an all or nothing choice, you have to give up something to get something...
It looks like you disabled Chrome's resizing on purpose too, which seems unnecessary/annoying. Why break existing functionality just to add new functionality?