[Keyboard] input type=time, « hh:mm AM » not encoded correctly

RESOLVED INCOMPLETE

Status

Firefox OS
Gaia::Keyboard
RESOLVED INCOMPLETE
5 years ago
5 years ago

People

(Reporter: nbp, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(blocking-b2g:-)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
I can reproduce this bug on a 2 weeks old build made on top of the latest Gecko, can somebody confirm that this does not affect old nor recent versions of Gecko. (build with NO_FTU, and no change in the settings)

STR:
 - Start UI Tests
 - Keyboard test
 - input type=time
 - Select 12, 00, AM

Expected:
 - 0:00 (or 12:00 AM) to appear in the text field

Seen:
 - Nothing appear.


On the same topic, all time selected as « hh:mm PM » are converted in 24h times in the input field.
Keywords: qawanted

Comment 1

5 years ago
Hi, Nicolas and all,

Because I don't have build version, in order to save communication effort.
So, I directly tried to use following 4 PVT builds to reproduce this problem.

In the following test, I cannot reproduce this bug.


* Build: Mozilla-b2g18-unagi-eng/2013-04-12-07-02-04
  + Mercurial-Information:
    - Gecko revision="950db80b82cb"
    - Gaia revision="a4c84e48ef6e"
  + Git-Information
    - Gecko revision="5178d9cb55473577ca8005f5b8e1de9baf023313"
    - Gaia revision="54ab4ce3f9107d1624c18bed2a09ace6bbc6601f"

* Build: Mozilla-b2g18-unagi-eng/2013-04-30-23-02-04
  + Mercurial-Information:
    - Gecko revision="765d296cff66"
    - Gaia revision=""
  + Git-Information
    - Gecko revision="a16e0162d71b6debadc14b338f24bab4503b328a"
    - Gaia revision="e420d71c9528786621f176fb4ce67d291e0a530e"

* Build: Mozilla-b2g18_v1_0_1-unagi-eng/2013-04-12-23-02-03
  + Mercurial-Information:
    - Ggecko revision="91fc54411a34"
    - Gaia revision="058522d169c0"
  + Git-Information:
    - Gecko revision="d7a6db4fc48e4091da842f408e69f969a0e704ec"
    - Gaia revision="3e7dda88950ae09166109783adea8181eb857d21"

* Build: Mozilla-b2g18_v1_0_1-unagi-eng/2013-05-01-23-02-01
  + Mercurial-Information:
    - Gecko revision="1198ae654986"
    - Gaia revision=""
  + Git-Information
    - Gecko revision="d12f4b1d3a9ec82a138693d62c950f7959729a97"
    - Gaia revision="09046df332cd217cf4fad55c48ce9ce3f14ee5a4"

Attach the screenshots.

Could you please use latest build to try this problem?
If you still need QA to follow this problem, could you please provide the build information?
Thanks. Have a nice day!

Comment 2

5 years ago
Created attachment 744576 [details]
Screenshots of time field
Seems to be working,I'd suggest we close as worksforme
Whiteboard: [tef-triage]

Updated

5 years ago
Keywords: qawanted
Whiteboard: [tef-triage] → [tef-triage][closeme 5/9/2013]
(Reporter)

Comment 4

5 years ago
Sorry for not mentioning the Gecko / Gaia versions before.

hg changeset of Gecko: 1fdf667ca50644746cfb094546c6201258458fdb
git sha1 of Gaia: 4e2d757cc50d41c7614c1c1ebf039f21781a5e3b

These are recent versions, I opened the bug as a tef? as I have no idea if the bug was on b2g18 as I have no spare device for testing.

Comment 5

5 years ago
Hi, Nicolas,

Thanks for your help.
Could you please also provide the branch name of each project?
(ex: mozilla-central, b2g18, v1.0.1 etc....)
One more question, I assumed the build was made by yourself.
It is not official build. (PVT build)
So, I doubt that the problem might cause by wrong Gaia and Gecko mapping.
I will try/test the similar PVT build on my device after you provide the further information.
blocking-b2g: tef? → -
Whiteboard: [tef-triage][closeme 5/9/2013] → [closeme 5/9/2013]
(Reporter)

Comment 6

5 years ago
(In reply to William Hsu [:whsu] from comment #5)
> Hi, Nicolas,
> 
> Thanks for your help.
> Could you please also provide the branch name of each project?

the Gecko changeset is in mozilla-central (maybe inbound)
And Gaia is in the mozillaorg/master branch.

> It is not official build. (PVT build)

No, it is not.
I am making my own builds because I need some probes in the JavaScript Engine.

Comment 7

5 years ago
Hi, Nicolas,

Sorry for my late reply! I would like to help on this case but the build you used was a customized build.
I don't know the detail information while you built the customized build.
So, I only can pay attention on PVT build to trace whether the PVT build have this problem.
Thanks for your feedback. Have a nice day!


Best Regards,
William

Comment 8

5 years ago
So, closing this per whiteboard?
Whiteboard: [closeme 5/9/2013]

Updated

5 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.