Andrew Plotkin

The commented-out lines for glk_buffer_to_upper_case_uni() and glk_buffer_to_lower_case_uni() are in case you want to compare the behavior of those functions. They work correctly.

Useful test inputs: ``` abcde αβγδε fflfi (the first character of this line becomes three characters when title-cased) ```

I think this boils down to a question of what fields in the spec are optional. I'm sure I've done a bad job of documenting that.

I've merged in the input element changes. (Remove `position:absolute`; minimum width 200.) The "Tap to type" placeholder is also in. The click-inputel-to-focus handler causes problems. It sticks around forever, for...

The de-absolutization makes for one visual bug: if you narrow the window, the cursor (I mean, the text insertion point) briefly gets shoved down to the next line. It comes...

> Maybe we want it absolute except when the min=200 bound has been applied. I got this to work, although the calculation is a bit messier than it used to...

Huh, yeah. That's a fun thing to not notice for decades. > if it reads a line break, that line break should be copied to the buffer and then a...

Trying to reconstruct the intention here -- I think the scenario in question is: - Timer event goes out - Player triggers input - The other end sends the update...

> In that case user would just get a warning - not a fatal error, right? It shouldn't be a fatal error, but I hate to make assumptions. > You...

One case to consider is a rapid timer that usually does nothing. (E.g. you tick every second and watch for a clock time, or the contents of a file, or...