Closed
Bug 680877
Opened 13 years ago
Closed 13 years ago
Allow providers to specify auth prompt and calendar id
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
RESOLVED
FIXED
1.1
People
(Reporter: Lenni, Assigned: Lenni)
Details
Attachments
(1 file)
4.67 KB,
patch
|
Fallen
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20100101 Firefox/6.0
Build ID: 20110811165603
Steps to reproduce:
In the current version a auth-prompt appears. I adjusted the code so that providers can use their own implementation for authentication.
In addition the provider is able to set a id for the calendar to support for example displaying the calendar in a calendar-list-tree without registering.
Assignee | ||
Comment 1•13 years ago
|
||
Updated•13 years ago
|
Status: UNCONFIRMED → ASSIGNED
Component: General → Internal Components
Ever confirmed: true
QA Contact: general → base
Comment 2•13 years ago
|
||
Comment on attachment 554833 [details] [diff] [review]
Bug 680877 - Allow providers to specify auth prompt and calendar id
>- * NOTE: If the server only provides one realm for all calendars, be sure that
>- * the |this| object implements calICalendar. In this case the calendar name
>- * will be appended to the realm. If you need that feature disabled, see the
>- * capabilities section of calICalendar.idl
>- *
Any specific reason you took this comment out? I'd rather leave it in and will revert that part before checkin.
>- }
>-
>- try {
>+ try {
Spacing seems incorrect here, I'll fix that too while I'm at it.
Aside from those minor nits, r=philipp
Attachment #554833 -
Flags: review+
Updated•13 years ago
|
Attachment #554833 -
Attachment is patch: true
Comment 3•13 years ago
|
||
Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/83a9601b834c>
-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Trunk
Updated•13 years ago
|
Assignee: nobody → Lennart.Bublies
You need to log in
before you can comment on or make changes to this bug.
Description
•