Closed
Bug 404976
Opened 17 years ago
Closed 17 years ago
calendar.autorefresh.timeout limit to max 3-digit numbers in options
Categories
(Calendar :: Preferences, defect)
Calendar
Preferences
Tracking
(Not tracked)
VERIFIED
FIXED
0.8
People
(Reporter: aryx, Assigned: Fallen)
Details
Attachments
(1 file)
|
1.19 KB,
patch
|
dbo
:
review+
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.10pre) Gecko/20071120 Calendar/0.8pre
calendar.autorefresh.timeout is shown only with 3 digits in the options, the user can't enter more (the input looks like it could take 5 digits). My preference value and was and still is (seen in config editor) 1440.
Flags: blocking-calendar0.8?
|
||
Updated•17 years ago
|
Flags: wanted-calendar0.8+
Flags: blocking-calendar0.8?
Flags: blocking-calendar0.8-
|
||
Comment 1•17 years ago
|
||
Not going to happen for 0.8.
Flags: wanted-calendar0.8+ → wanted-calendar0.8-
|
Assignee | |
Comment 2•17 years ago
|
||
This should do it, 0x7FFFF should be high enough for everyone.
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Attachment #309823 -
Flags: review?(Berend.Cornelius)
|
|
Assignee | |
Comment 3•17 years ago
|
||
Minimally invasive, I don't see a regression risk for this patch. Requesting wanted-calendar0.8
Flags: wanted-calendar0.8- → wanted-calendar0.8?
|
|
||
Comment 4•17 years ago
|
||
Comment on attachment 309823 [details] [diff] [review]
Fix v1
r=dbo
Attachment #309823 -
Flags: review?(Berend.Cornelius) → review+
|
|
||
Updated•17 years ago
|
Flags: wanted-calendar0.8? → wanted-calendar0.8+
|
|
||
Comment 5•17 years ago
|
||
Philipp on low bandwidth -- Checked in on HEAD and MOZILLA_1_8_BRANCH and SUNBIRD_0_8_BRANCH
-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.8
|
||
Updated•17 years ago
|
OS: Windows XP → All
Hardware: PC → All
Version: Trunk → unspecified
|
|
||
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
Flags: wanted-calendar0.8+
Flags: blocking-calendar0.8-
You need to log in
before you can comment on or make changes to this bug.
Description
•