We are using various variations of fullscreen/full screen/full-screen and are even patching upstream TigerVNC between two variants. We should probably try to be consistent in our use. So what is the proper way? Right now it seems like "full screen" for a noun, and "full-screen" as an adjective is the majority opinion, even if "fullscreen" is tolerated. See: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/full-screen https://english.stackexchange.com/questions/162421/fullscreen-or-full-screen https://ell.stackexchange.com/questions/157952/full-screen-full-screen-or-fullscreen
When fixing this we should probably also fix it upstream so we can avoid distracting diffs.
I've done some looking around too and have come to the same conclusions as in comment 0. So let's go ahead and stick to the following conventions: • "full-screen" when referring to the adjective/mode • "full screen" when referring to the noun
A pull request has been submitted that address these issues in upstream TigerVNC: https://github.com/TigerVNC/tigervnc/pull/1382
TigerVNC, noVNC, the documentation, and tlclient have now all been updated to use the conventions in comment 2 and all changes to the former two have been upstreamed. Worth noting is that I didn't bother updating our downstream version of noVNC since we've disabled the full-screen features in WebAccess. Grepping for "screen" in the `ctc/' tree no longer result in any incorrect full.*screen hits. Regarding release notes, I did some grepping around in our old release notes and couldn't find any release notes on changes with the same theme as this one. If there are any objections to this bug being marked prosaic, feel free to reopen it.
Also, a note on testing: Be aware that the words "full screen" can span multiple lines and may have other characters in between: Example: > char *some_string = "full\n" > "screen"; So make sure to put some extra love into your regexps!
Apparently, there are a couple of screenshots that need updating as well
The screenshots have now been updated!
Tried to find things that were still wrong. Found lots of variable names and comments, but I guess it's not worth the effort to change those. We also have stuff like configuration values that cannot be changed for backward compatibility reasons. And as mentioned, Web Access still has some incorrect uses that aren't visible in ThinLinc. However I found this in the documentation: > doc/external/client_options_screen.rst: you run in full screen mode and want to reach the native session that (used pcregrep -M to catch any occurences split over two lines as well) Screenshots look good.
The issue mentioned in comment 12 has now been corrected.
Looks good now. I also checked the commits and everything looked correct there.
