User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/20090715 Firefox/3.5.1 Build Identifier: The ability to pull tabs from other Firefox instances via Weave is very handy to me but could be improved for certain scenarios. While at work I frequently stumble across something that I want to look at when I get home. I could wait until I get home, then pull the interesting tab from my work computer, but that means I have to keep the tab open all day at work, then remember to pull it when I get home. I'd like to send tabs from my work computer to my home computer, have them magically open there (immediately, if the browser is open, or whenever I next sync). This would be a very handy feature for me. Reproducible: Couldn't Reproduce
Really, you want something more like Read It Later or something similar.
Read It Later's functionality is close, but I'm particularly interested in the automatic-tab-open feature. Read It Later requires me to remember that there was something I wanted to read. To me, Weave is the logical place for this feature because it already has the code in place to manipulate browser instances, and Weave already does something somewhat close to sending tabs between browsers.
I think this is on our roadmap for mobile, at the very least... but not super high priority.
This is on the roadmap and is being tracked at https://wiki.mozilla.org/Services/Sync/Push_to_device. The current plan is to implement the functionality in phases: 1) Implement "send URI to other device" feature in the Sync core API 2) Implement UX in desktop and mobile We will be tracking both independently, in separate bugs. It is possible the core feature/API will be released before the UI is present.
Figured I'd drop a link to this here, save me searching for it in the future: https://addons.mozilla.org/firefox/addon/send-tab-to-device/
Should you consider bug 777799 in the implementation of this - if you're going to push a mobile-oriented page to another device, it might be better to use the canonical URL (or some similar mechanism).
(In reply to Oliver Henshaw from comment #8) > Should you consider bug 777799 in the implementation of this - if you're > going to push a mobile-oriented page to another device, it might be better > to use the canonical URL (or some similar mechanism). If you can come up with a 100%-reliable method for finding out the canonical URL for a page from its mobile URL, then we can think about doing that!
Note that this would really be part of the bookmark and history formats of the browser itself, not Sync. Sync doesn't see the page that you load, so it can't see <link> elements.
(In reply to Richard Newman [:rnewman] from comment #9) > > If you can come up with a 100%-reliable method for finding out the canonical > URL for a page from its mobile URL, then we can think about doing that! Well, you can only use the canonical url when its provided somehow: according to http://support.google.com/webmasters/bin/answer.py?hl=en&answer=139066 it can be provided by the page itself or in the HTTP header. I see that it can be specified out-of-band in a sitemap, too.
(In reply to Oliver Henshaw from comment #11) > Well, you can only use the canonical url when its provided somehow: See my last comment: it's more than that.
Would love to see this prioritised to make Firefox on Android even higher value