Sharing from webbrowserapp should include title of the page

As can be seen here: https://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/src/app/Share.qml#L51

The browser does share both the URL and the title, so it looks like the problem might be on the receiving end, i.e. the twitter webapp. I’m not familiar with that part of the webapp container, assigning to Alex for confirmation.

In the dekko browser is also only the url of the website like at the twitter app.

Status changed to 'Confirmed' because the bug affects multiple users.

I’m seeing this in dekko’s log file when sharing a URL from the browser:

qml: [handleContentHubImport] [INFO] ItemText:
qml: [handleContentHubImport] [INFO] ItemUrl: http://m.slashdot.org/
qml: [handleContentHubImport] [INFO] ContentType is Link: http://m.slashdot.org/
qml: [handleContentHubImport] [STATUS] Appending to text body
qml: [ComposePage::appendTextToBody] [INFO] passing text to composer: http://m.slashdot.org/
qml: Appending text to body: http://m.slashdot.org/
qml: [handleContentHubImport] [STATUS] Complete

So it looks like the title of the page is not shared, indeed, which probably is an issue in the browser (or in content-hub itself, need to investigate). That said, dekko doesn’t use the link title either, see https://git.launchpad.net/dekko/tree/qml/main.qml#n146. So I’ll mark dekko also affected.

I’ve addressed an issue in the browser (see linked branch) which wasn’t sharing the page title along with the URL.
However dekko is still not getting the page title, so I suspect there may be an issue in the content hub itself. Adding a task for it.

Ah! I hadn't noticed the page title was also available along with the link.

So in Dekko the page title needs to be added as the message subject. Simple enough to add :-)

@Olivier did you modify Dekko in any way to find out it still isn't receiving the title?

At the moment the code just assumes only a link is available with ContentType.Link and doesn't check the text property of the ContentItem for a value.

scrap that last comment. Just realised it logs the text value even if it doesn't sue it :-)

Yes, dekko’s logging is proving very useful!

Adding the webapps-core project to handle the title in the webapps themselves ...

It looks like when the transfer is charged, we are ignoring the text property if there is a url. We should ensure all properties set on the item makes it through to the dest app.

This bug was fixed in the package webbrowser-app - 0.23+16.04.20160509.3-0ubuntu1

---------------
webbrowser-app (0.23+16.04.20160509.3-0ubuntu1) xenial; urgency=medium

  [ CI Train Bot ]
  * Resync trunk.

  [ Olivier Tilloy ]
  * Fine-tune the custom memory-pressure handler, from data gathered on
    several devices. (LP: #1576639)
  * Update translation template.

 -- Olivier Tilloy <email address hidden> Mon, 09 May 2016 17:56:03 +0000

This needs a content-hub change still

This bug was fixed in the package content-hub - 0.1+16.10.20160610.2-0ubuntu1

---------------
content-hub (0.1+16.10.20160610.2-0ubuntu1) yakkety; urgency=medium

  * Ensure all the properties are set when the url is set on a
    ContentItem (LP: #1571361)

 -- Ken VanDine <email address hidden> Fri, 10 Jun 2016 14:02:46 +0000

hi guys, i've seen the interesting situation here in different apps , isn't shared webpage supposed to be displaying both page tittle and URL though every app ?

current build number: 375
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-07-03 23:26:54
version version: 375
version ubuntu: 20160702
version device: 20160606-ab415b2
version custom: 20160701-981-38-14

Steps:
1.Open browser app and visit a valid URL
2.Tap on share button to share the webpage to message app and twitter

Expectation:
No matter what app you choose to share , they all should include both page tittle and URL

Actual result:
In message app, there is only page tittle
In twitter, there is only URL

Confirmed. dekko and telegram only use the URL. But as demonstrated by the fact that the messaging app uses the page title, the problem is not in the browser app (it exposes both URL and title), it is in the destination app that chooses to use only one of the two items.

Apps like telegram are capable of displaying an embedded preview of the page along with the title when given a URL, so it seems reasonable that they would use only the URL. But messaging app should clearly use the URL too, I’ll mark it affected.