Closed Bug 448771 Opened 17 years ago Closed 17 years ago

Open task context menu in calendar view -> output in error console

Categories

(Calendar :: Calendar Frontend, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: andreas.treumann, Assigned: mschroeder)

Details

Attachments

(1 file)

STEPS TO REPRODUCE: =================== - enable 'Show task in view' - create a task with start and due date - open the context menu of this task in the calendar view RESULT: ======= - error console output: Error: Failed to read 'deleteTaskAccesskey' from chrome://calendar/locale/calendar.properties. Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://calendar/content/calUtils.js :: calGetString :: line 638" data: no] Source File: chrome://calendar/content/calUtils.js Line: 642 moving the mouse to the 'Convert to' entry generates the same error a second time EXPECTED RESULT: ================ - no error REPRODUCIBLE: ============= - always
Flags: blocking-calendar0.9?
There only exists "deletetaskAccesskey" but not "deleteTaskAccesskey" in <http://mxr.mozilla.org/mozilla/source/calendar/locales/en-US/chrome/calendar/calendar.properties#437> To avoid a late-l10n change you probably want to change the calling code to read "deletetaskAccesskey" and fix the entity name after the 0.9 release.
Flags: blocking-calendar0.9? → blocking-calendar0.9+
Assignee: nobody → mschroeder
Status: NEW → ASSIGNED
I think we need an late-l10n checkin, or leave it as is for 0.9 because we have to adjust either calendar.properties (1 change), or http://mxr.mozilla.org/seamonkey/source/calendar/base/content/calendar-common-sets.js#504 (change last argument to "task") + calendar.properties (1 change). If we decide to do a late-l10n checkin we should go for solution 1. sipaq, what's your opinion?
An late-l10n change is out of the question for such a small fix, that we can easily work around. Please fix this in calendar-common-sets.js, then file a followup bug. Oh, and please set yourself a reminder in Lightning to fix in like seven weeks :)
Whiteboard: [needs-patch]
Attached patch Patch v1Splinter Review
Additionally removed superfluous second argument of adaptModificationMenuItem function. Also filed follow-up bug as bug 450391.
Attachment #333537 - Flags: review?(philipp)
Whiteboard: [needs-patch]
Whiteboard: [patch in hand] [needs review]
Comment on attachment 333537 [details] [diff] [review] Patch v1 >-function adaptModificationMenuItem(aMenuItemId, aItems, aItemType){ >+function adaptModificationMenuItem(aMenuItemId, aItemType){ While you're at it, please add a space before the { >- adaptModificationMenuItem("calendar-item-context-menu-delete-menuitem", items, "Task"); >+ //XXX Workaround added in bug 448771 because of string freeze >+ var menuItem = document.getElementById("calendar-item-context-menu-delete-menuitem"); I'd suggest to also add a bug# for the followup bug. r=philipp
Attachment #333537 - Flags: review?(philipp) → review+
Whiteboard: [patch in hand] [needs review] → [patch in hand]
Checked in on HEAD and MOZILLA_1_8_BRANCH -> FIXED
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: [patch in hand]
Target Milestone: --- → 0.9
Checked in lightning 2008081803 and sunbird 20080817 -> VERIFIED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: