Closed Bug 1127006 Opened 11 years ago Closed 11 years ago

[META] IOS-1 - Firefox Ecosystem - Sharing

Categories

(Firefox for iOS :: General, defect, P5)

All
iOS 8
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: jchaulk, Unassigned)

References

Details

(Keywords: meta)

Attachments

(1 file)

47 bytes, text/x-github-pull-request
st3fan
: review+
Details | Review
No description provided.
Keywords: meta
Hardware: x86_64 → All
Attached file Pull request
Attachment #8562566 - Flags: review?(sarentz)
Un-metaing this bug. While I think there will be additions and follow ups (adding screenshots, "Share image" in pages, etc.), the core feature is simple.
Summary: [META] IOS-2 - Firefox Ecosystem - Supporting share extensions from other applications → IOS-2 - Firefox Ecosystem - Supporting share extensions from other applications
Summary: IOS-2 - Firefox Ecosystem - Supporting share extensions from other applications → [META] IOS-2 - Firefox Ecosystem - Supporting share extensions from other applications
Comment on attachment 8562566 [details] [review] Pull request Wes, the screenshot is added already :-) Try to share some pages to Twitter. I compared the results between our app and Safari and the resulting screenshots are exactly the same. Looks like the extension framework downloads the page to grab screenshots. I think the only thing that needs a quick fix is this: I don't think the `selected.title ?? url` bit is correct. If it is good practice to attach the URL if a title is missing (i don't know if it is, we should check what safari does probably) then we should attach `url.absoluteString` instead. Otherwise we are just attaching two similar items of type `public.url` and the receiving extension would not see the difference between them.
Comment on attachment 8562566 [details] [review] Pull request I'm +ing but i think that title issue needs to be resolved before we merge.
Flags: needinfo?(wjohnston)
Attachment #8562566 - Flags: review?(sarentz) → review+
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(wjohnston)
Resolution: --- → FIXED
Which Meta should those dependencies belong to then? I'm marking this one done, and those aren't, they belong elsewhere in the dependency tree.
Flags: needinfo?(wjohnston)
Yeah Wes. This one really can't be FIXED if the dependencies are not. How do we correct the links?
I am not sure why those bugs are dependent on this one. i.e. why does "Supporting share extensions from other applications" depend on "Create a share extension to allow sharing into Firefox" or "Send tab"? I revamped the other metabug (bug 1109663) that seemed to be specifically about Twitter/Facebook into a generic sharing one and we can hang these off there if you want (since it was fixed by this as well). But this was marked iOS-2 and that was iOS-1, so I regret doing that now. This is not a meta bug. The dependencies here were wrong. I'm leaving them until I know where they go, but this bug did not depend on them.
Flags: needinfo?(wjohnston)
Wes - Keep in mind that there are two distinct types of sharing: 1. I am inside Firefox and want to share to another app 2. I am in a different app and want to share to Firefox Let's not use one meta bug for both concepts. Also, #2 has two sub components: 1. Add URL to the Firefox bookmarks or reading list 2. Send URL to a different device The early mockups used two different UI entry points for these.
Looking at the pull request, this code is for #1 in comment 8, "I am inside Firefox and want to share to another app". That is not what the title of this bug is about. It's about #2. So I am changing the titles between this bug and bug 1109663 (the Twitter and Facebook part confused you).
Summary: [META] IOS-2 - Firefox Ecosystem - Supporting share extensions from other applications → [META] IOS-1 - Firefox Ecosystem - Sharing
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: