Lightning - Can't edit start or end times of an event
Categories
(Calendar :: Dialogs, defect)
Tracking
(Not tracked)
People
(Reporter: jean.lafontaine, Assigned: darktrojan)
References
Details
(Whiteboard: [datetime-issue-6.2])
Attachments
(6 files, 1 obsolete file)
33.07 KB,
image/png
|
Details | |
28.82 KB,
image/png
|
Details | |
1.84 KB,
patch
|
Fallen
:
review+
|
Details | Diff | Splinter Review |
1.17 MB,
application/x-xpinstall
|
Details | |
1.94 KB,
patch
|
Details | Diff | Splinter Review | |
2.02 KB,
patch
|
Fallen
:
review+
Fallen
:
approval-calendar-beta+
Fallen
:
approval-calendar-esr+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0 Steps to reproduce: With Thunderbird 60.2.1 with xul-ext-lightning from Mint 19.1 or Solydx EE both OS are configure in french but calendar is in english only. Just trying to add a new event in my calendars (local calendar or google calendar) Actual results: To reproduce the problem just add a new event and try to modify the start hour. when you press tab to change field and go in end hour field, the start hour reset to 00h00 and vice versa. If you just create a new event and don't edit the hour fields, it will be created correctly but as soon as you enter the hour field and try to modify something it will reset the hour to 00h00 Its impossible to had a new event with the start hour and end hour edited. Expected results: It should be possible to edit the hour field at creation or when a modification is necessary on the event.
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Comment on attachment 9034243 [details]
Edition of the just created event.png
wrong image
Reporter | ||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
I can't reproduce this using Thunderbird 60.2.1 with Lightning 6.2.2.1 provided by Ubuntu running on Linux Mint 19. Both are English versions.
Reporter | ||
Comment 4•5 years ago
|
||
Thanks for your verification, it made me think that something with the local (system-wide)was not OK. I then have checked the language region setting in cinnamon parameters. The region system-wide was not set. So i apply it system-wide (Appliquer à tout le système). Now I'm able to edit the hour field in the lightning extension. It is strange because that bug only appears recently with a new version of Thunderbird on SolydX. Then i did a fresh install of Mint and i had the same issue. Do i change something to resolve or if this need more investigation? Thanks!
Reporter | ||
Comment 5•5 years ago
|
||
Post solution setting on mint 19.1
Reporter | ||
Comment 6•5 years ago
|
||
Sorry, I did not checked it properly and the problem is still present.
Reporter | ||
Comment 7•5 years ago
|
||
I made more verification. The only condition where lightning is working properly is when the language is set to English (AM-PM). I did not check in other language. By the way, I do not plan to use English so I'm still looking for a solution. Thanks!
Reporter | ||
Comment 8•5 years ago
|
||
Hi, Here is a temporary solution that i have put in place to be able to use lightning as my calendar application. I have simply create a launcher with that command: bash -c 'export LC_TIME=en_CA.UTF-8 ; thunderbird %u' en_CA locale has the right format aaaa-mm-dd (like in French) and the hour is now showing in AM-PM format. Lightning is functional but not fr_CA compliant. If someone has a better solution please don't hesitate to post. Thanks!
Comment 9•5 years ago
|
||
Please check with the upcoming TB66 beta [1] (available in the next couple of days) whether the issue is still present. If doing so, please use either a new profile or make sure to backup your TB profile before using it with the beta, since profile downgrading (from beta to esr after completing the test) is not supported and may cause problems.
Reporter | ||
Comment 10•5 years ago
|
||
Hi,
Just tried TB66b and i still have the same problem, the time reset to 00:00 when exiting the start time field.
Its only possible to create an event by doing a clik and pull in the day at the hours that you want.
Thanks!
Comment 11•5 years ago
|
||
Does the issue also reproduce for you if you have all addons but Lightning disabled in addons-manager and restarted TB?
Comment 12•5 years ago
|
||
Can you please also provide the last section "Internationalization & Localization" from the TB troubleshooting information (menu->help->troubleshooting information)?
Reporter | ||
Comment 13•5 years ago
|
||
All addons are disabled in TB
Langue et internationalisation
ParamΓ¨tres dβapplication
Langues demandΓ©es ["fr"]
Langues disponibles ["fr"]
Langues de lβapplication ["fr","en-US"]
PrΓ©fΓ©rences rΓ©gionales ["fr-CA"]
Langue par dΓ©faut "fr"
SystΓ¨me dβexploitation
Langues du système ["fr-CA"]
PrΓ©fΓ©rences rΓ©gionales ["fr-CA"]
Comment 14•5 years ago
|
||
Hi,
I have the same problem than Jean Lafontaine.
And I also see that we are not alone to experiment this bug.
Comment 15•5 years ago
|
||
(In reply to [:MakeMyDay] from comment #11)
Does the issue also reproduce for you if you have all addons but Lightning disabled in addons-manager and restarted TB?
All addons are disabled in TB
Langue et internationalisation
ParamΓ¨tres dβapplication
Langues demandΓ©es ["fr-CA","en-US"]
Langues disponibles ["fr"]
Langues de lβapplication ["fr","und"]
PrΓ©fΓ©rences rΓ©gionales ["fr-CA"]
Langue par dΓ©faut "und"
SystΓ¨me dβexploitation
Langues du système ["fr-CA"]
PrΓ©fΓ©rences rΓ©gionales ["fr-CA"]
Thank you.
Comment 16•5 years ago
|
||
Can you please check again with the new TB66 b3 available at [1] again and report whether the issue still exists?
Comment 17•5 years ago
|
||
(In reply to [:MakeMyDay] from comment #16)
Can you please check again with the new TB66 b3 available at [1] again and report whether the issue still exists?
No, I cannot check with a beta version ;
but I am told that 60.6 should be out in 2 weeks and correct the BUG.
And I can wait.
Thank you
Comment 18•5 years ago
|
||
This is not guaranteed until you verified that it works for you, since the reported issues is not present/reporducable here and can only be found and fixed with the help of people who are seeing the issue.
There are different datetime issues around and we fixed an issue different from the AM/PM issue, but we would like to know whether the AM/PM issue is fixed as a by-product. So, please reconsider and keep in mind this is a community project.
Reporter | ||
Comment 19•5 years ago
|
||
Hi!
Here my observations with the new TB66 b3. Maybe it was similar on the current release, i did not check in details.
When i create a new event by double clicking in the calendar, the edition windows opened with the right start time and with the end time one hour later (9:00 to 10:00) that a normal behaviour.
If i try to modifies the start time to begin my event at 9:15 (i did verified that i click on the right number 09 for hours and :15 for minutes). When i exit the start field, the start time change from 9:15 to 15:00. And the end time is automatically change to 16:00 to match the initial duration of that event.
If the modified start time is 9:20 i got 20:00 when leaving the start field edition.
If i try to edit the end hour field i always get an alert message saying that the end date is prior to the start date but both date are the same with start time an hour before the end time. So its not a right validation.
I can save the event with no problem (so the previous validation message was wrong?)
When trying to edit for a second time the save event, i can modify the start time (21:00) and without exiting the field, i then press the save button and the event is save but it shift the start time to 00:00 and saved the event at that time not the edited time of 21:00.
If i edit the start time to 21:00 again and try to exit the start field to edit the end time, The start time reset to 00:00 every time with no possibilities of editing to whatever you choose.
Then i tried to edit with the mouse by drag and drop or extend the time by pulling the mouse, this is working OK. Then again i tried to edit the event by double clicking. And the i can edit the event again and save it but with the same limitation (the minute become the hour etc..)
So by dragging there is a reset somewhere in the code that permit do come back to the first editing problem.
I home that those information will help you debug that code.
Thanks for your help!
Reporter | ||
Comment 20•5 years ago
|
||
Me again,
Just want to rectified the 00:00 reset is minute > hour problem, what i said in the previous post is not exact. You can always edit the time but the minutes always become the hours so if you choose 9:00 it will always reset the hour to 00:00.
Sorry for that!
Comment 21•5 years ago
|
||
(In reply to Jean Lafontaine from comment #20)
Me again,
Just want to rectified the 00:00 reset is minute > hour problem, what i said in the previous post is not exact. You can always edit the time but the minutes always become the hours so if you choose 9:00 it will always reset the hour to 00:00.
Sorry for that!
Jean,
I have the same issue.
Do you think it is a bright idea to try a beta version of TB ?
I have to add that as a retired programmer myself,
I have never installed a product that was not tried and foolproof.
Regards
Reporter | ||
Comment 22•5 years ago
|
||
(In reply to Roger Gravel from comment #21)
(In reply to Jean Lafontaine from comment #20)
Jean,
I have the same issue.
Do you think it is a bright idea to try a beta version of TB ?
I have to add that as a retired programmer myself,
I have never installed a product that was not tried and foolproof.Regards
Bonjour Roger,
I use another computer to test the beta to be sure that there will be no issues. You can also use a virtualbox installation to test those things. But i understand your concerns. I often face problem with testing software but when its not on my main computer, i can live with it.
Jean
Comment 23•5 years ago
|
||
It's safe to install the beta next to the esr version on the same machine. The beta starts with a fresh profile, which is enough to check the issue (just close the poping up account wizard).
Comment 24•5 years ago
|
||
Thanks you Jean for the helpful description. I will come back to this if I need further observations or checks from your end.
Comment 25•5 years ago
|
||
Ok, I'm able to reproduce the behaviour. The cuprit is that the "h" spearator in the screenshot is enclosed by spaces. When putting in a time using this pattern makes the time parser choking.
I spare an uplift request for now, since I cannot verify locally, whether the reported issue vanished with this fix.
Comment 26•5 years ago
|
||
Jean, can you check with the attached xpi (for TB66 b3) whether the issue is resolved for you with this patch? You can simply overinstall this by installing from file using the TB addons manager and restart TB afterwards.
Updated•5 years ago
|
Reporter | ||
Comment 27•5 years ago
|
||
(In reply to [:MakeMyDay] from comment #26)
Created attachment 9051565 [details]
{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi for TB66b3Jean, can you check with the attached xpi (for TB66 b3) whether the issue is resolved for you with this patch? You can simply overinstall this by installing from file using the TB addons manager and restart TB afterwards.
Hi, just back from skiing.
I think, you just resolved the issue with your patch on TB 66.0b3.
Just let me know when and on which non beta release it will be available.
Thanks!
Jean
Comment 28•5 years ago
|
||
So you are confirming it works for you? You will notice the ESR version once the patch gets uplifted.
Comment 29•5 years ago
|
||
Comment on attachment 9051562 [details] [diff] [review] IgnoreExtraSpacesWhileDetectingTimeSeparators-V1.diff The beta approval may be obsolete if the patch lands before the merges tommorrow.
Comment 30•5 years ago
|
||
Reporter | ||
Comment 31•5 years ago
|
||
(In reply to [:MakeMyDay] from comment #28)
So you are confirming it works for you? You will notice the ESR version once the patch gets uplifted.
Yes i do confirm that its working for me.
Thanks!
Updated•5 years ago
|
Updated•5 years ago
|
Comment 32•5 years ago
|
||
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/fdbbe7d76632
Ignore spacing around time separators when parsing times in timepicker. r=philipp
Updated•5 years ago
|
Comment 33•5 years ago
•
|
||
Backout:
https://hg.mozilla.org/comm-central/rev/58c62d0c0ebc0f750f45e600e749d6bf1ca9201d
Backed out changeset fdbbe7d76632 (bug 1517569) for test failures in testTimezones.js. a=backout DONTBUILD
Sorry, I had to back this out for eight test failures in testTimezones.js:
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones3_checkStJohns
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones4_checkCaracas
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones5_checkPhoenix
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones6_checkLosAngeles
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones7_checkBuenosAires
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones8_checkParis
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones9_checkKathmandu
TEST-UNEXPECTED-FAIL | /Users/cltbld/tasks/task_1553942585/build/tests/mozmill/testTimezones.js | testTimezones.js::testTimezones10_checkAdelaide
The test passes locally on Windows if the locale is set to en-GB, it fails with locale en-US.
EDIT:
Push was https://treeherder.mozilla.org/#/jobs?repo=comm-central&revision=9ec42b993238cc77d539150cfa3a934be3be6053&selectedJob=237031546
Failed on all platforms.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 34•5 years ago
|
||
With the previous patch, the regular expression was capturing the " pm" in "2:00 pm" as a separator instead of as the am/pm marker β¦ so it assumed there was no marker and the input was 2 am.
With this patch I explicitly look for a single character of white-space around the separators.
Assignee | ||
Comment 35•5 years ago
|
||
I might fix up the typo in the commit message too β¦ not sure what a spearator is but it sounds nasty.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 36•5 years ago
|
||
Note comment 35 if you're checking this in.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 37•5 years ago
|
||
Let's give this bug a spell on nightly/beta before we push it to ESR.
Comment 38•5 years ago
|
||
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/92831637a3fa
Ignore spacing around time separators when parsing times in timepicker. r=philipp
Updated•5 years ago
|
Comment 39•5 years ago
|
||
TB 68 beta / Cal 7.0:
https://hg.mozilla.org/releases/comm-beta/rev/15ed6f4a09a76a6fad4ae918f76eee842d517e6f
Comment 40•5 years ago
|
||
TB 60.8 ESR / Cal 6.2.8:
https://hg.mozilla.org/releases/comm-esr60/rev/8e1ce8a186e1e6736115177707ff3ecc51161d3a
Need 6.2.8.
Updated•5 years ago
|
Updated•5 years ago
|
Description
•