Closed Bug 819189 Opened 12 years ago Closed 12 years ago

Importing a read only calendar and trying to view the event - should not be able to edit the event

Categories

(Firefox OS Graveyard :: Gaia::Calendar, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+)

VERIFIED FIXED
B2G C3 (12dec-1jan)
blocking-basecamp +

People

(Reporter: jsmith, Assigned: jlal)

Details

(Whiteboard: [mentor=jlal@mozilla.com][LOE:S])

Attachments

(1 file)

Build:

Device - Unagi

Hashes

  <project name="releases/gaia" path="gaia" remote="mozillaorg" revision="3ad4e525a43a44b3c6eb905304fc0648ca5fd9b8"/>
  <project name="releases/gecko" path="gecko" remote="mozillaorg" revision="74bff8c0506e6ff91666095b432fbc6aed9621fe"/>

Steps:

1. Import a calendar that is read only
2. Try to edit the event for the calendar

Expected:

You shouldn't be able to edit the event.

Actual:

Editing capabilities and saving the edits is possible. Obviously the server won't update with the changes, since this is read only (silently fails).

Noming here mainly cause this could be relatively common scenario and the silent failure is likely to spurt some confusion (user expectation is it was saved, but in reality, it wasn't).
blocking-basecamp: --- → ?
This should be easy we already have the permission information (from caldav) and we also have readonly hooks that we use for recurring events.
Whiteboard: [mentor=jlal@mozilla.com][LOE:S]
Assignee: nobody → jlal
blocking-basecamp: ? → +
Priority: -- → P1
Assigning to C3 hopefully that is correct.
Target Milestone: --- → B2G C3 (12dec-1jan)
Its not strictly related but the format google returns its "Contact's Birthdays" calendar events is very malformed. I made various workarounds at the ICAL layer so we could support that calendar and those changes will land here as well.
Comment on attachment 690057 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6903

Harder to review this bit without knowing a little about caldav.
I made an attempt to document this fairly well so it was clear what each permission actually does.
Attachment #690057 - Flags: review?(lorchard)
Attachment #690057 - Flags: review?(kgrandon)
Quick note- I don't automatically upgrade anyone to have these permissions the effects of this patch will be visible after the user syncs (it will remove all options to modify read only calendars).

It should also now be impossible to sync write only calendars.
Additionally we hide the "Save" text for readonly events.
Comment on attachment 690057 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6903

I have lack of knowledge on CalDav/iCal interfaces, but this makes sense logically and looks pretty good from a style/syntax PoV. R+ from me.
Attachment #690057 - Flags: review?(kgrandon) → review+
Hi Jason,

This patch _should_ resolve the last of the google issues related to syncing events (and correctly handing permissions in calendars in general). I have some special workarounds included in this patch for the issues I found but its possible there are other oddities I am unaware of.

Can you give your google calendar another shot?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Keywords: verifyme
Comment on attachment 690057 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6903

Doesn't look like I'm needed for a review here
Attachment #690057 - Flags: review?(lorchard)
Hmm...confirmed to be working with my zimbra calendar that's read only. Not sure if it works with google accounts though...digging into this now.
Looks good.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: