lat9
... and the debug-log's contents?
How about using the language's `code` instead? Otherwise, sounds like a good idea.
If you'll notice, one is public and one is protected.
No, the idea is that one's used by internal-to-class functions while others are "anticipated" to be issued from POSM's observer, where that additional string is added to the front of...
When used internally, the caller has already prepended the "where is this from" text to the message; that's not true when the debug is coming externally/publically.
OK, so I've set **_Configuration :: Minimum Values :: State_** to `0` and have **_Configuration :: Customer Details :: State field - Display as pulldown when possible?_** set to `true`....
There are a couple of variables "in play" here and I think that they're at odds with themselves: - The language constant 'ENTRY_STATE_TEXT', which (if not an empty string) displays...
FWIW, I couldn't reproduce this issue on any "standard" size viewport.
Perhaps a teeny comment to indicate that the `‑` is a non-breaking hyphen?
@scottcwilson, clarification required in the docs.