No current plans to pursue this.

No longer reproduces.

No longer valid as far as I can find.

ehhh, not sure about this. It's not worse, like I can pinch to zoom in Safari, but not Chrome.

Rolling, so we'll see how accurate the simulator was.

I am just intrigued that user-scalable=no actually means "somewhat user-scalable".

No, I hate all zooming.

(I am glad to see the auto-zoom-on-controls gone and don't care about any other zoom feature.)

Right. Do you use that?

Oh -- but double-tap-to-zoom doesn't? 😕

I tested pinch to zoom, which still works. We just turn off the auto-zoom. I'll roll the server here and give a more thorough shakedown.

(Specifically, D17714 added user-scalable=no, which probably does the opposite of what this requested.)

Removed.

Hopefully Android browsers will hurry up and ignore that tag too..

There are at least some nontrivial effects, like searching for text without "maximum-scale" can imply a zoom:

I have an idea for this.

I'll probably build a conpherence package, but overall this is likely as good as it gets. I don't think there will be any additional benefit without building a full separate mobile app.

The first page I found on the internet claims the iPhone 7 will be 1920x1080, so my strategy looks like it's paying off!

@epriestley Missed a spot: D16325

D16323 uses <input type="text" pattern="\d*" />, which appears to have the best behavior.

On iOS 9.2 in the simulator, <input type="number" /> gives you this keyboard:

Oh, there's a "Toggle Software Keyboard" option that I somehow disabled.

On iPhone Simulator, the behavior of <input type="number" /> appears to be "draw the keyboard for 1 frame and then immediately hide it".

Looks like an iPhone with Gboard keyboard.

Offhand, do you know if <input type="number" /> has the desired behavior on your device?

thanks, I couldn't seem to find it.

Doesn't reproduce in any mobile browser (Safari, Chrome) I have access to. Presume resolved, but if still occurring please re-open with full reproduction steps.

Prose diffs have resolved this.

doesn't reproduce anymore

Truly our most useful project.

Wait for it...

Happens on test account too

I tried a couple of other devices in the simulator but couldn't get a repro -- can you try this to get a JS trace?

Let me try my spam account.

Nothing unusual. Latest iPhone/iOS

I can't immediately reproduce this in iOS Simulator or on my physical iPhone 4s. What hardware/OS version are you seeing it on?

This isn't the most thrilling UI but seems to get the job done. T10912 covers one minor followup issue.

Just more JavaScript.

Is adding a new project tag and "move on workboard" in the same set of stacked action a minor extension, or super hard?

I've upgraded our instance now this has hit stable, and our team is thrilled. The interface may not be perfect, but it satisfies the vast, vast majority of our use cases. Thank you!

Alright, a v0 of this is live here now -- "Move on Workboard" in the "Actions" menu above the comment box. This is a rough cut and we may not keep it in this form, but the infrastructure it needs is built now, at least.

ignore this - test

The infrastructure changes should now be complete, and we're clear to start experimenting with the UI. Progress so far:

I'm going to sort out the infrastructure issues first, then we can see where the UI goes. Specifically:

Does this being added to 'Prioritized' mean Phacility are working on it, so
there's really no point in me plodding along trying to do it? :-)

Evan basically answered my question in T5214. There are good reasons not to expose an API at this point, as due to possible future changes, it might be unstable. I'll try to figure out how to do these things within Phab only, perhaps by creating myself a temporary outdated-style API. Then I'll to understand the second bullet point above more fully. I'm pretty comfortable I understand the point made about EditEngine.

Thanks for the guidance. The exact UI is a minor detail. I'm pretty happy to contribute towards either of your leading contenders (and don't like either of the possible contenders much). But as you say, that's not going to become an issue until a little while down the track.

No, we're not open to implementing this as multiple separate select controls. We don't really have a UI in mind that we're happy with, but we have several we're less unhappy with than multiple select controls (leading contenders: single optgrouped select, alternate actions menu for workboard actions; possible contenders: visual table-layout control, select per-project in a dialog).

@epriestley, I'm not sure if/when I'll have time, but would a patch for this along the lines of my previous comment be considered? I'm conscious it must be forward-looking to T5474, and might take a few attempts for me to get up to standard. If the core team can review/guide me, I'm certainly willing to give it a go as time permits.