Closed Bug 393515 Opened 17 years ago Closed 17 years ago

LSFileQuarantine support

Categories

(Camino Graveyard :: Downloading, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Camino1.6

People

(Reporter: stuart.morgan+bugzilla, Assigned: stuart.morgan+bugzilla)

References

Details

(Keywords: fixed1.8.1.8, Whiteboard: [camino-1.5.4])

Attachments

(2 files)

Attached patch basic supportSplinter Review
Basic support for LSFileQuarantine.
Attachment #278008 - Flags: superreview?(mikepinkerton)
Comment on attachment 278008 [details] [diff] [review]
basic support

rs=pink
Attachment #278008 - Flags: superreview?(mikepinkerton) → superreview+
Landed on trunk and MOZILLA_1_8_BRANCH.
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: fixed1.8.1.7
Resolution: --- → FIXED
This stuff is Leopard-specific, right?

Now that it's about to come out, are you willing to let on what it's
supposed to do? :-)

I'm wondering if it might help with bug 400227 ... though so far my
tests indicate the answer is "no".
This opted us in to the quarantine system (the thing that pops up the "You download this from the internet, are you sure you want to open it" dialog) in a way that let us control the quarantine behavior on things we created but were not downloads (e.g., the profile).
... but this reminds me, I need to file a follow-up bug about having core support the part of the quarantine system that lets the dialog say where the file was downloaded from.
Thanks, Stuart.  So my guess was right.

But I can't get the Info.plist syntax from this bug working in
Firefox.  I suspect that Apple has simply not (yet) implemented the
LSFileQuarantine "exclusions" ... at least not as of build 9A559 (one
release before the gold master, which is build 9A581).

Have you been able to devise a test to see if Camino's "exclusions"
are working?
I've found out why this bug's patch's syntax doesn't work in Firefox
(at least as of Leopard client build 9A559):  You may only specify one
exclusion.  If you specify more than one (as this bug's patch does),
neither will work.  For more info see bug 400227 comment #24.
The follow up bug I alluded to is now bug 401748. Quick tests suggest Camino's exclusion isn't working, but I haven't dug into it to be sure I'm not just doing the test incorrectly.
Reopening because this isn't working right all the time, per our investigations.
Status: RESOLVED → REOPENED
Flags: camino1.5.4?
Resolution: FIXED → ---
Is this worth landing as-is for 1.5.4 when it appears not to be working?
I landed a modification that uses the same thing Firefox uses (~/Library/*) which is working in my testing, so if we want that version for 1.5.x we can take that.
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
Landed on the CAMINO_1_5_BRANCH for 1.5.4 with the new syntax.
Flags: camino1.5.4? → camino1.5.4+
Whiteboard: [camino-1.5.4]
Blocks: 407215
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: