1024832 - Permission to use offline storage based on offline-apps.allow_by_default shouldn't set "Allow" permissions

Status: NEW

(SeaMonkey :: Passwords & Permissions, defect)

Description

[rsx11m]

(In reply to [e-mail] from bug 1019583 comment #15)
> Strangely enough setting this preference still sets the permissions in the
> permission manager, although deleting them seems to have little effect
> because they'll just get recreated all the time,

I can't reproduce this on Firefox 33.0a1, it stays at "Use default" even when the offline storage is used based on the "allow_by_default" setting. Since Firefox doesn't have a Data Manager, I can't tell for sure though that no site-specific setting has been established, but filing for SeaMonkey for now.

STR:

  1. Set offline-apps.allow_by_default to true
  2. clear any html5demos.com permissions in the Data Manager
  3. clear in Advanced > Offline Apps any existing content
  4. visit http://html5demos.com/offlineapp as a testing site

Actual results:

  5. Data Manager says "Allow" for Offline Web Applications

Expected result:

  5. entry in Data Manager shouldn't have been created as it reflects a
     conscious decision of the user having permitted that site specifically
     to use the offline storage.

Comment 1

[rsx11m]

> I can't reproduce this on Firefox 33.0a1, it stays at "Use default" even
> when the offline storage is used based on the "allow_by_default" setting.

Looking at the permissions.sqlite files of Firefox vs. SeaMonkey in a new profile, both have an entry for html5demos.com in the offline-apps category. Thus, maybe Firefox is affected the same and just doesn't expose it in the Page Info UI.

Comment 2

[rsx11m]

I've installed KaiRo's Data Manager on Firefox 33.0a1, and it shows that Firefox indeed behaves the same (i.e., the "Allow" permission is automatically set with "allow_by_default" being active, but without the user explicitly consenting to it). So, unless that's something that SeaMonkey can fix on its side, this bug should probably be moved to some Core component.