Calendar:WCAP Provider: Difference between revisions

Jump to navigation Jump to search
no edit summary
mNo edit summary
No edit summary
Line 28: Line 28:
If you cancel login, you won't be asked
If you cancel login, you won't be asked
again anymore.
again anymore.
<code>HTTPS</code> is enforced, even if you have specified plain <code>HTTP</code>,
<code>HTTPS</code> is preferred, even if you have specified plain <code>HTTP</code>,
because the password is transmitted.  If the calendar server does not
because the password is transmitted.  If the calendar server does not
support <code>HTTPS</code> (at least for login), you will be asked whether to
support <code>HTTPS</code> (at least for login), you will be asked whether to
continue the login.  For calendar data retrieval, the specified protocol
continue the login.
(<code>HTTP</code>, <code>HTTPS</code>) of the URL is used.


===UI===
===UI===
Line 38: Line 37:
can be confusing if the selected calendar is not shown (unchecked), i.e.
can be confusing if the selected calendar is not shown (unchecked), i.e.
you won't see your newly created event.  IMO we have to improve this.
you won't see your newly created event.  IMO we have to improve this.
===Alarms===
Alarms are  currently turned ''off'' by default, because of [http://groups.google.de/group/mozilla.dev.apps.calendar/browse_thread/thread/3bd7188c29309452/311545e3d102642c?hl=de#311545e3d102642c exception bloat (#3)]. You can switch them on defining
user_pref("calendar.wcap.suppress_alarms", false);


==Logging==
==Logging==

Navigation menu