Everything Apple (the Mac heads thread)

You are reading a single comment by @duncs and its replies. Click here to read the full conversation.

•

duncs
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"
/>
```

•

Soul in reply to @duncs

^ @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.
•

Velocio in reply to @duncs

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).

Everything Apple (the Mac heads thread)

About

LFGSS