And other parts of the Closure code effectively assume that at least one of IE, EDGE, WEBKIT, or GECKO is set to true. So awesome.
-
-
Show this thread
-
Oh, and Closure assumes that all "mobile" browsers must be "WebKit": <https://github.com/google/closure-library/blob/a1ada022cd322396755a5c42b8942a1b5d1d7544/closure/goog/useragent/useragent.js#L176-L179 …>. There's just no way to win here...
Show this thread
End of conversation
New conversation -
-
-
I don't see anything wrong with all UA strings converging, at least in theory? Like they all did on Mozilla/ long ago? Just one more round through the spin cycle. Now, in practice this may be bad because it breaks other Firefox-sniffing codepaths that you still need...
-
I mean, yes, we can just switch to a WebKit UA string wholesale. That does require introducing a bunch of bugs, etc.
End of conversation
New conversation -
-
-
Let's go with a "like Edge" UA string and fix the other bugs, too, that we haven't been able to fix because the bugs are assumed Geckoisms.
-
Tempting, but the set of stuff we would likely need to change might be ... large. Including explicitly breaking some things that are broken in Chrome/Edge and that we'd rather not break, I expect.
End of conversation
New conversation -
-
-
Hmm online input method editors, especially Han (Chinese), typically rely on ctrl or shift key being pressed once without other keys to switch between Latin/Han mode and full-width mode. I remember in the past some browsers would fire a keypress event, ...
-
But now every editor needs to use a state machine with keydown and keyup
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.