Closed Bug 1414534 Opened 7 years ago Closed 5 months ago

Calendar doesn't switch day/week/month whenever a new window is opened

Categories

(Calendar :: Calendar Frontend, defect)

Lightning 5.4.3
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: growl1, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [closeme 2024-09-20])

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20171024165158 Steps to reproduce: I use Lightning 5.4.4 1. Open a mail via double-click (opens in a tab) 2. Open this tab (with the mail) in a new window 3. Close the window again Actual results: 4. Lightning won't switch the day/week/month, if the cursor in the upper area is clicked Additional: The error console throws a "currentView (... ) is undefined" error Expected results: 5. Lightning should switch the day/week/month
growl, do you still see this when using a current version??
Flags: needinfo?(growl1)
Keywords: perf
Summary: Calendar freezes whenever a new window is opened → Calendar doesn't switch day/week/month whenever a new window is opened
Whiteboard: [closeme 2018-07-15]
Component: General → Calendar Views
Confirming with TB 52.8/Lightning 5.4.8 with the mentioned STR. From the error console: >TypeError: currentView(...) is undefined[Weitere Informationen] calendar-views.js:687:39 > cal.navigationBar.setDateRange chrome://calendar/content/calendar-views.js:687:39 > setDateRange chrome://calendar/content/calendar-month-view.xml:671:15 > showDate chrome://calendar/content/calendar-month-view.xml:618:15 > goToDay chrome://calendar/content/calendar-views.xml:240:11 > moveView chrome://calendar/content/calendar-views.xml:267:15 > calendarController.doCommand chrome://calendar/content/calendar-common-sets.js:397:17 > goDoCommand chrome://global/content/globalOverlay.js:100:7 > oncommand chrome://messenger/content/messenger.xul:1:1 >An error occurred executing the calendar_view_prev_command command: [snipping the above stack trace] globalOverlay.js:103 > goDoCommand chrome://global/content/globalOverlay.js:103:5 > oncommand chrome://messenger/content/messenger.xul:1:1
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(growl1)
Whiteboard: [closeme 2018-07-15]
See Also: → 1402745
Severity: normal → S3

gorwl1,

When using version 128, does this still reproduce for you?

Flags: needinfo?(growl1)
Whiteboard: [closeme 2024-09-20]

No, the error doesn't seem to be reproducable anymore.

Thank you very much.

Flags: needinfo?(growl1)

Thanks for the update

Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.