Closed Bug 399433 Opened 16 years ago Closed 16 years ago

[Proto] Automatic scrolling feature doesn't work when searching for the next free meeting slot

Categories

(Calendar :: General, defect)

Product:
Calendar
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: andreas.treumann, Assigned: michael.buettner)

Details

Attachments

(1 file)

patch v1
914 bytes, patch
Fallen
: review+
Details | Diff | Splinter Review 
STEPS TO REPRODUCE:
===================

- use a WCAP calendar
- create an event
- open the attendees dialog
- invite someone
- push the 'next slot' button

RESULT:
=======

- the timescale jumps two days in the future
- the eventmarker is out of view

EXPECTED RESULT:
================

- only the event marker should jump to the next free time slot

REPRODUCIBLE:
=============

- always
Flags: blocking-calendar0.7?
Status: NEW → ASSIGNED
Component: Provider: WCAP → General
Attached patch patch v1 — — Splinter Review 
This is a regressions that has been introduced with bug 370435. Fortunately, it's just a missing call to one of the initialization functions.
Attachment #284462 - Flags: review?(philipp)
Since this is a low-risk one-line patch it really should take the 0.7 train.
Flags: blocking-calendar0.7? → blocking-calendar0.7+
QA Contact: wcap-provider → general
Version: Trunk → unspecified
Comment on attachment 284462 [details] [diff] [review]
patch v1

Looks fine, r=philipp
Attachment #284462 - Flags: review?(philipp) → review+
Summary: [attendees dialog] push `next slot` button -> timescale moves unnecessarily → [Proto] Automatic scrolling feature doesn't work when searching for the next free meeting slot
patch checked in on trunk, MOZILLA_1_8_BRANCH and SUNBIRD_0_7_BRANCH

-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.7
Checked issue in Lightning RC2 and Sunbird RC2 -> VERIFIED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.