1431431 - Android doesn't like placeholder-shown in some input types.

Status: NEW

(Core :: DOM: Core & HTML, enhancement, P3)

Description

[Emilio Cobos Álvarez (:emilio)]

See bug 1431041, where I added a reftest for it that only failed on android like:

  https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/TvlgXZA5T7KOoft1iSnUoA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

I'm landing a fails-if(Android) reftest with those types referencing this bug number.

Comment 1

[Emilio Cobos Álvarez (:emilio)]

I guess that's because bug 773205, which as of right now is android-only.

Anyway, that explains the platform difference.

Comment 2

[Jonathan Watt [:jwatt]]

(In reply to Emilio Cobos Álvarez [:emilio] from comment #1)
> I guess that's because bug 773205

Wrong bug number?

Also, what specifically are you asking for with the needinfo? I wrote the original number input code years ago, but I don't think placeholder was even working in my version. I don't have any suggestions that wouldn't involve me spending a chunk of time debugging this. (And the code is clunky since I ended up implementing type=number as a form field within a form field which was much harder than expected, so I suspect the fix may not be simple.)

Comment 3

[Emilio Cobos Álvarez (:emilio)]

(In reply to Jonathan Watt [:jwatt] (needinfo? me) from comment #2)
> (In reply to Emilio Cobos Álvarez [:emilio] from comment #1)
> > I guess that's because bug 773205
> 
> Wrong bug number?

Well, I meant that the number inputs have native UI on android, so that _may_ explain that.
 
> Also, what specifically are you asking for with the needinfo? I wrote the
> original number input code years ago, but I don't think placeholder was even
> working in my version. I don't have any suggestions that wouldn't involve me
> spending a chunk of time debugging this. (And the code is clunky since I
> ended up implementing type=number as a form field within a form field which
> was much harder than expected, so I suspect the fix may not be simple.)

Sorry, I was just told that you were the person to contact re. input type="number", but you're right I wasn't clear at all. My ni? was just in case you knew what was going on / whether this is expected. But it doesn't make much sense in light of the above I guess.

I don't plan to debug this anytime soon either, I don't think it's too important.