Web pages on qrz.com now (?) set initial focus to callsign query, problem for keyboard navigation

I noticed in the last week or two (7 Feb now) that qrz.com web pages appear to set initial focus (user input) to the callsign search field. When I enter qrz.com web pages the callsign search field is automatically active. As I mostly navigate with a keyboard (rather than a mouse), the keyboard navigation keys (such as up/down/right/left arrows) now are trapped by the callsign search field, rather than operating as expected to move within the web page.

Example of other website that has this behavior (and has had for some time) - yahoo.com

Example of other website that lacks this behavior - almost any other web site with a search/input field embedded.

Does this change provide a user experience benefit I'm missing?

Thanks for any comment.

 

I’ve noticed too, on two different devices. I don’t get this behavior on numerous other XenForo-powered sites, only here.

It’s become annoying…

 

I've noticed this quirk this evening also. Also, the drop-down menu of previous lookups in the search box (upper left corner top) doesn't work here either. I have the same issue when using QRZ in browser or the app.

 

Ah, so it's not just me. I find it convenient that Digikey defaults to the search field, but the automatic drop-down of call lookup history on QRZ plus getting in the way of browsing with the arrow up/down without clicking out is inconvenient.

 

Will make some inquiries and report back. In the meantime, please use your mouse for navigation.

 

Like we have any option.

I appreciate the effort to investigate, thanks.

 

Thank you for that voice of support. Perhaps you could offer a better option?

 

No, I don't have a better option. I'm just being silly. Keep up the good work.

 

Silly is good. Sometimes we take ourselves too seriously. Thank you for the kind words.

 

(better option?) - the HTML code that was in use until this change had the more common behavior (must click into field to make use of search input field).

I believe it's some option in the base website HTML when configuring the input field, and the change could probably be backed out. Could be more involved if qrz.com is built on a toolkit or framework where that option got changed by the toolkit/framework provider.

 

I have an update from IT and WB0GAZ pretty much nailed the problem. It started with a Chrome update for Win 10 and Win 11 that affects certain QRZ HTML processes having to do with "autofill". The problem is ongoing because Google is still in the process of changing their code which presents IT with a moving target. This also affects the Edge browser as it is built on a Chrome foundation.
We don't have a workaround (other than using a mouse) or a timeframe yet. We will update as we know more.

 

Google and Microsoft - the gifts that keep on giving.

 

Some users have reported that updating Chrome partially resolves the problem. Select the three dots at the top right of a Chrome screen, scroll down, and select Settings near the bottom, then scroll down the left side to the bottom and select About Chrome. It should automatically check for and update Chrome on your Win 10 or Win 11 system.

 

Mac user here, and the issue is (or has been recently) present (and persistent) on two iDevices using Safari, not Chrome

 

On Firefox 118.0.1 here (Windows 10), appears that Firefox is on a different underlying engine than Chrome/Edge.