README: added information on links and elinks

README.md

@@ -328,6 +328,24 @@ Therefore, for desktop browsers:
     UI should be functional (not pretty) in IE8+ (2008) and dysfunctional in IE7 and lower
     (fixable by refactoring the approach to displaying/hiding elements to avoid the usage of `:not` selector,
     but this is outside the scope of the task).
+* links: checked on 2.30, half-broken:
+    * Everything that depends on the game state is always displayed,
+        i.e. we get "Start game", "Restart game", "make computer play for X",
+        "make X moves manually", and most importantly,
+        "Player X won", "Player Y won" and "Draw" all displayed always;
+        this can be worked around by using Web Components templates
+        instead of controlling state visibility by CSS.
+    * Additionally, Links doesn't support disabled buttons
+        so all board fields are always clickable (even if they're already filled),
+        this does not cause any functional issues (clicking on the occupied field,
+        or clicking on an empty field when the game is over, does not change anything),
+        but still that's a poor UX.
+* elinks: checked on 0.17.1.1, half broken in the same way as on links, not easily fixable
+    because even with Web Components templates, elinks will still display template content:
+    https://github.com/rkd77/elinks/issues/341.
+    Fixable by building all state-dependent components on frontend manually
+    (so that backend only sends those that are relevant for the current state),
+    but that would be too significant redesign for no benefit besides making things work in elinks.
 
 So presumably, according to caniuse.com,