Everything Apple (the Mac heads thread)

What happens if you text zoom in until there's no longer screen space for the input and vanishes...

My message tell tale doesn’t work either- I’d assumed that was the same for everyone?

Howard- it happens on page load, so you get what you get.

No VPN, wifi or mobile makes no difference, I’ve cleared stored data for the site and re-authenticated, nothing makes a difference.

It's very consistent for me too

No VPN
Content blocker (Blockbear) makes no difference
Amplosion extension makes no difference
Wifi (either home or at work via their proxy), or phone network makes no difference

Happens on both iPad (i.e. large screen) and iPhone mini (small), Safari only
Doesn't happen when simulating an iPhone (iOS 16.4) through Xcode on a Macbook

Happens when you load a forum page from a location bar url or from reloading a page
Happens when you click a numbered page button or the focum prev/next button
Doesn't happen when swiping or clicking forward/back browser buttons

No change when clearing cookies or cache, or resetting browser preferences to default
No change when disabling javascript

Maybe I need to grab and host a static instance of a page and see if it happens that way. Then at least I'd be able to change it

Howard- it happens on page load, so you get what you get.

Yeah I know - the site dynamically hides the offending number input box when the screen size gets restrictive. Try zooming the text until you can no longer see the offending text box. Would be interesting to see if it still does it.

1 Attachment

changing the default zoom to 150% so that the text box part of the form isn't rendered does stop the keyboard jumping up. presumably because there's no text box available anymore to focus on

Neither of my iPads do it, interestingly.

because there's no text box available anymore to focus on

Heh, yes. Even this bug has half a brain.

There's at least two, hidden by

display:none

My guess is it's some behaviour based on autofill. That would explain why it happens for some people but not others.

The browser has been told to remember a specific entry for a text box with that name, and so it comes up with the keyboard automatically.

This keyboard issue happens on my iPhone too. If I navigate to any page where the 'page counter' is in view it auto-focusses and the keyboard pops up. If I navigate back or forward with the browser arrows it won't auto-focus only when linking to a new page. Very annoying, tried clearing caches and changing settings but nothing seems to stop it.

My guess is it's some behaviour based on autofill. That would explain why it happens for some people but not others.

Interesting! Just tried disabling autofill passwords on my iPhone and it seems to have fixed the issue.

A little playing around suggests that It may be the Bitwarden autofill specifically which is the issue.

Ooooooooh.

Yeah, that does it for me too
I use BitWarden for passwords, I previously used 1Password

(might be enough for me to find a new password manager. Bitwarden generally feels clunky to me, and the integration with biometric auth on Chrome windows is flaky too)

@Dammit @motman you Bitwarden users too?

1 password is great but the new version they now want money

No Bitwarden here. I do have Adguard installed but turning that off doesn't seem to effect the auto-focus thing.
It's a mystery!

Me too. Totally vanilla set up, using native PW management (Keychain).

ok... so

I've done a simple copy/paste of a page here and dumped it to
https://....com/lfgss.html

I then created a dummy login in bitwarden for that url, (just test / test), so not actually sending anything sensitive anywhere

and the annoying keyboard popup happens

I then changed the form type from text to number tel, removed the regex pattern and saved that as
https://....com/lfgss2.html
https://....com/lfgss-tel.html

and the keyboard popup doesn't happen

so before

<input
  type="text"
  min="1"
  value="4712"
  max="4712"
  step="1"
  pattern="\d*"
  title="Enter the page number to jump to"
  class="form-control"
/>

after

<input
  type="tel"
  min="1"
  value="4712"
  max="4712"
  step="1"
  title="Enter the page number to jump to"
  class="form-control"
/>

^ @Velocio - will that change break loads of things? Seems to solve the issue.

For what it's worth, I use Bitwarden and it's not appearing for me but I don't have lfgss.com as a domain saved so I assume you could resolve by just deleting lfgss from your Bitwarden instance.

actually - I probably only have lfgss saved as a hangover from before we had auth0 here
I don't need my old username/password saved

lemme bin that from bitwarden and see if that also solves it

...

Yup - that solves it too.

Nice one, ta for the nudge

On Android the second option removes the total pages count.

Edit: Actually it doesn't remove it, there's an extra little scroll bar for that section so you need to scroll down just there to see the count.

2 Attachments

So you also found it triggers without anything from my side.

And that the input change does fix it.

What I do not know, is what now breaks. At the time we wrote this, that didn't work... I wanted to do that, but it wasn't supported fully.

Perhaps it is now supported more fully, I'm open to testing it in a week when I'm back in London (right now I'm on the West Coast in St Helena, Napa on a work trip).

I do recall one issue was that the number field couldn't have a pattern, and inserted an up / down increment scroller, and also permitted scientific numbers (!?).

But if the general direction works... I'll test that.

But you got as far as I did... it doesn't need JavaScript or CSS to trigger it. Safari triggers this off of basic valid/compliant HTML. Hence it's a Safari bug.

There may be workarounds to how the HTML is presented... but then we're going from standard compliant HTML to just different HTML to achieve the same task. And that's harder for me to test (in Firefox, Chrome, Safari across Linux, Windows, Mac, iOS) given that I don't have hardware for all those things... so any testing I do will likely break stuff for a section of people at any time (so I left the breakage with the browser that broke it).

The up/down scroller is a usability issue btw... on some browsers scrolling the page by touch screen could trigger the field, scroll the number, and auto-navigate the page to the new searched page.

Basically a different nightmare.

Ideally Safari just fix their bug.

@Velocio

incase it gets lost in the chat above - seems a Safari/Bitwarden/iOS password manager combination. It's the password manager getting involved that triggers it for me too, and specifically when it thinks that it has a password to fill.
Removing my (legacy) lfgss login info from Bitwarden has stopped the popup too. So maybe Bitwarden getting overly enthusiastic and seeing the text input as a login field?

For what it's worth, I use Bitwarden and it's not appearing for me but I don't have lfgss.com as a domain saved so I assume you could resolve by just deleting lfgss from your Bitwarden instance.

This seems to have worked for me. I just deleted the lfgss url from my lfgss Bitwarden entry and now seem to be able to use autofill without the focus stealing in lfgss.

The number input type is specifically meant for incrementing/decrementing numbers, which makes it the wrong choice here. tel is more appropriate. @duncs Can you add that to your test case?