Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

how to i change the format for the event start and end time pickers from 24 hours to AM/PM?

  • 3 답장
  • 2 이 문제를 만남
  • 1 보기
  • 최종 답변자: Matt

more options

When you open or edit an event in lIghtning and select the drop-down arrow to pick the time, the preconfigured set up is for 24 hours, how can this be change to reflect 12 hours with AM/PM options.

Once the time is selected it displays the AM/PM format but I am attempting to set this up for elderly users who do not want to do the math just to set a calendar event.

Thanks.

When you open or edit an event in lIghtning and select the drop-down arrow to pick the time, the preconfigured set up is for 24 hours, how can this be change to reflect 12 hours with AM/PM options. Once the time is selected it displays the AM/PM format but I am attempting to set this up for elderly users who do not want to do the math just to set a calendar event. Thanks.

모든 댓글 (3)

more options

How is the time displayed by your operating system (eg Windows)?

I'm guessing Lighting might display the time mimicking the operating system and changing it in the OS might do the trick.

To change time settings in Windows 7: Start button -> Control Panel -> Clock, Language, and Region -> Change the date, time or number format.

Use h:mm tt and h:mm:ss tt for for Short time and Long time respectively.

more options

Yes I had already checked that possibility from posts that I found in the forum but I am set on AM/PM etc.

I realized once the time has been selected it converts to AM/PM in the text box but I would like to be able to select it that way and not use 0 - 23 for the hours. I am intending to set this up for use with elderly people and do want them to have to do the math and create possible confusing for setting a calendar event.

Thanks

more options

I was aware of a bug requesting such a change, and it appears in 12 hour in my copy of Lightning (Daily testing build), but I just can not find the bug to confirm what happened and which versions are involved.