The phone is flawless for me; let's put that out of the way! 
After the update (but I have no evidence to say "due to the update"), the hyphen function on the physical keyboard has been acting up in the strangest manner-it sends the next typed character back to the position just before the hyphen. (It just did for my previous hyphen!) For instance: offtopic- off-topic (first is the problem, the second, my fix.) The hyphen sent the t in topic back, so I am forced to use the arrow keys to properly type hyphens. This makes "fast" typing quite cumbersome. The problem happened (or I noticed it) after the update, corrected itself without my direct intervention, and came back today. It does NOT happen when typing hyphens on the web address bar, nor when using any of the touch keyboards-it only happens when typing hyphens within a website itself with the physical keyboard, such as this forum reply (I am typing from my D3). I wonder if there's a setting that is setting itself on and off, therefore it not being a bug per se, or if this is a genuine physical keyboard to web browser problem to be worried about.
I don't imagine many will chime in, as nobody else seems to be having this problem, but if anybody has anything to say to help, thanks in advance!

After the update (but I have no evidence to say "due to the update"), the hyphen function on the physical keyboard has been acting up in the strangest manner-it sends the next typed character back to the position just before the hyphen. (It just did for my previous hyphen!) For instance: offtopic- off-topic (first is the problem, the second, my fix.) The hyphen sent the t in topic back, so I am forced to use the arrow keys to properly type hyphens. This makes "fast" typing quite cumbersome. The problem happened (or I noticed it) after the update, corrected itself without my direct intervention, and came back today. It does NOT happen when typing hyphens on the web address bar, nor when using any of the touch keyboards-it only happens when typing hyphens within a website itself with the physical keyboard, such as this forum reply (I am typing from my D3). I wonder if there's a setting that is setting itself on and off, therefore it not being a bug per se, or if this is a genuine physical keyboard to web browser problem to be worried about.
I don't imagine many will chime in, as nobody else seems to be having this problem, but if anybody has anything to say to help, thanks in advance!