Closed Bug 399526 Opened 17 years ago Closed 15 years ago

let the offline-app permission apply to subdomains

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- final+

People

(Reporter: dcamp, Assigned: mayhemer)

References

Details

Attachments

(1 file)

testExactPermission() is used to decide whether a site can use the offline APIs, so subdomains don't inherit the permission.

testPermission() is used in most (all?) other consumers of the permission manager.  So for consistency's sake it would make sense to switch the offline-app permission to be used this way too.
Blocks: 398161
Assignee: nobody → honzab
Status: NEW → ASSIGNED
This is tougher than just switching to testPermission().  When you clear out an offline domain, we clear its globalStorage and offline cache entries by looking for entries which match the domain.  We'll miss data added by subdomains if we just switch to testExactPermission.
Blocks: 367373
This seems to be a sufficient solution with what we have now.
Attachment #391096 - Attachment description: wip 1 → v1
Attachment #391096 - Flags: review?(jst)
Attachment #391096 - Flags: superreview+
Attachment #391096 - Flags: review?(jst)
Attachment #391096 - Flags: review+
Comment on attachment 391096 [details] [diff] [review]
v1 [Checkin comment 3]

http://hg.mozilla.org/mozilla-central/rev/c726007b8eef

This bug is blocking all-wanted bug, we have to get this patch on all branches.
Attachment #391096 - Attachment description: v1 → v1 [Checkin comment 3]
Attachment #391096 - Flags: approval1.9.2?
Attachment #391096 - Flags: approval1.9.1.5?
Attachment #391096 - Flags: approval1.9.0.16?
Attachment #391096 - Flags: approval1.8.1.next?
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment on attachment 391096 [details] [diff] [review]
v1 [Checkin comment 3]

We certainly don't need this on 1.8.1 anymore -- we've got no supported offline-app-using products on that branch.

Didn't quite understand the reasons for needing this on the other old branches, and would be more comfortable approving if it's deemed important enough for 1.9.2
Attachment #391096 - Flags: approval1.8.1.next? → approval1.8.1.next-
This blocks bug 367373 that is wanted on 1.9.2 and 1.9.1. Probably not on 1.8.1 and older.
Comment on attachment 391096 [details] [diff] [review]
v1 [Checkin comment 3]

I don't think we want to mess with this on the 1.9.0 branch if we don't have to.
Attachment #391096 - Flags: approval1.9.0.16? → approval1.9.0.16-
Flags: wanted1.9.0.x-
Component: General → DOM
Product: Firefox → Core
QA Contact: general → general
Comment on attachment 391096 [details] [diff] [review]
v1 [Checkin comment 3]

We won't take this on 1.9.1. We're getting close to releasing 1.9.2 and are hoping to eventually auto-update users from 1.9.1 so you should get approval for that release.
Attachment #391096 - Flags: approval1.9.1.6? → approval1.9.1.6-
Comment on attachment 391096 [details] [diff] [review]
v1 [Checkin comment 3]

approval1.9.2 requests aren't currently being monitored, since we're nearing RC freeze and there are too many outstanding requests, so I'm clearing this request. Feel free to re-request approval if you are confident that it's worth drivers' time to consider whether this non-blocker needs to land for 1.9.2 at this stage.
Attachment #391096 - Flags: approval1.9.2?
Nominating for 1.9.3 blocking.
blocking2.0: --- → ?
blocking2.0: ? → final+
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: