Closed
Bug 351452
Opened 18 years ago
Closed 18 years ago
Fields for custom alarm time cut off in dialog New event
Categories
(Calendar :: Calendar Frontend, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: thorsten, Unassigned)
Details
(Whiteboard: [no l10n impact])
Attachments
(5 files)
34.96 KB,
image/png
|
Details | |
26.09 KB,
image/png
|
Details | |
51.55 KB,
image/png
|
Details | |
67.16 KB,
image/png
|
Details | |
1.20 KB,
patch
|
mattwillis
:
first-review+
mvl
:
second-review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1b2) Gecko/20060821 Firefox/2.0b2 Build Identifier: Lightning 0.1+ (2006030606) In the dialog New Event the three fields for a custom alarm time are cut off. See attached screenshot. Reproducible: Always Steps to Reproduce: 1. Start TB and create a new Event in Lightning 2. 3.
I think this bug should be solved for the 0.3 release.
Flags: blocking0.3-
Comment 4•18 years ago
|
||
(In reply to comment #2) > I think this bug should be solved for the 0.3 release. To nominate something as blocking the release, please set the flag to "?". The release drivers will then determine whether it will block (+) or not (-) and set the flag appropriately. For more information, see http://wiki.mozilla.org/Calendar/For_Everyone/Blocking_Flags (In reply to comment #3) > Duplicate of bug 351323? It could be related, but the axis of the cutoff is different. Perhaps a dupe.
Summary: Fields fors custom alarm time cut off in dialog New event → Fields for custom alarm time cut off in dialog New event
Comment 5•18 years ago
|
||
> http://wiki.mozilla.org/Calendar/For_Everyone/Blocking_Flags That URL should be http://wiki.mozilla.org/Calendar:For_Everyone:Blocking_Flags
Comment 6•18 years ago
|
||
Using Branch (Tb 1.5.0.x, Tb 2.0a1) or Trunk (Tb 3.0a1) build? What happens when you resize the dialog? Do you have a regression range? Maybe this is related to Bug 351323.
Flags: blocking0.3- → blocking0.3?
Summary: Fields for custom alarm time cut off in dialog New event → Fields fors custom alarm time cut off in dialog New event
Updated•18 years ago
|
Summary: Fields fors custom alarm time cut off in dialog New event → Fields for custom alarm time cut off in dialog New event
Even when I resize the dialog box, the three fields still remain cut off. I am using Thunderbird 1.5.0.5 and the lightning build 0.1+ (2006090506)
Comment 8•18 years ago
|
||
I think this is not a duplicate of Bug 351323. On Windows 2000 I can't see the custom alarm fields at all. But the dropdown menus stated in Bug 351323 are displayed fine. WORKS with Tbird/2.0a1 (20060905) + Ltn/0.1+ (2006090506-mozilla1.8) FAILS with Tbird/1.5.0.5 (20060719) + Ltn/0.1+ (2006090506-mozilla1.8) FAILS with Tbird/1.5.0.7 (20060905) + Ltn/0.1+ (2006090506-mozilla1.8) Tbird/3.0a1 (20060905) + Ltn/0.1+ (2006090508-trunk) shows Bug 351323
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•18 years ago
|
Flags: blocking0.3? → blocking0.3+
Comment 9•18 years ago
|
||
The problem only occurs with Event dialog, with Task dialog everything is OK. WORKS with Tbird/1.5.0.5 (20060719) + Ltn/0.1+ (2006-08-18-06-mozilla1.8) FAILS with Tbird/1.5.0.5 (20060719) + Ltn/0.1+ (2006-08-19-14-mozilla1.8) Bug 287550 was checked in during that time and changed the dialog. Maybe this revealed a xul bug regarding hidden/colapsed elements that is present on MOZILLA_1_8_0_BRANCH but fixed on MOZILLA_1_8_BRANCH. I also need to test if the changes from Bug 350375 can help here.
Updated•18 years ago
|
Whiteboard: [no l10n impact]
Comment 10•18 years ago
|
||
Same problem on Linux. In addition I have to revert my statement from Comment #9: Task dialog is also affected: Selecting custom alarm shows the custom alarm fields - but the privacy field above is no longer visible. Looking closer I think this is caused by the "max-height: 10em;" style set on calendar-attendee-list element.
OS: Windows XP → All
Comment 12•18 years ago
|
||
Comment 13•18 years ago
|
||
I verified that this is caused by the "max-height: 10em;" style set on calendar-attendee-list element. Removing that style rule fixes the problem. But then the attendee list will grow to infinite height with each line added. I tested adding/removing flex attribute/style rules in various places but none fixed both problems. So I decided to increase the max-height value. Setting to 12em makes it work fine on Windows 2000 and Ubuntu Linux. This should also work on Windows XP because the fields are less cut off than on Windows 2000 according to the screenshot. On Mac OS X the problem doesn't show at all - probably this was developed on Mac and 10em is the right size for this system. Note: This doesn't really fix the problem. It just makes it disappear for now. I suggest to use this change for 0.3 unless someone comes up with a better fix.
Attachment #237486 -
Flags: second-review?(dmose)
Attachment #237486 -
Flags: first-review?(mattwillis)
Comment 14•18 years ago
|
||
Comment on attachment 237486 [details] [diff] [review] increase the max-height value Still works on Mac okay.
Attachment #237486 -
Flags: first-review?(mattwillis) → first-review+
Comment 15•18 years ago
|
||
Comment on attachment 237486 [details] [diff] [review] increase the max-height value dmose's queue is a bit full.
Attachment #237486 -
Flags: second-review?(dmose) → second-review?(mvl)
Comment 16•18 years ago
|
||
Comment on attachment 237486 [details] [diff] [review] increase the max-height value This is totally the wrong way to fix this, but it seems that richlistbox is quite buggy. A simple testbox in a small window doesn't show a scrollbar... So guess we have to live with this workaround for now. But please add a big XXX comment. r=mvl
Attachment #237486 -
Flags: second-review?(mvl) → second-review+
Comment 17•18 years ago
|
||
Patch with big ol' comment checked in on MOZILLA_1_8_BRANCH and trunk. -> FIXED
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 18•18 years ago
|
||
(In reply to comment #17) > Patch with big ol' comment checked in on MOZILLA_1_8_BRANCH and trunk. Works here. Windows XP.
You need to log in
before you can comment on or make changes to this bug.
Description
•