Confirmed users
169
edits
Services/F1/Design: Difference between revisions
→Outline of F1 Design
Mixedpuppy (talk | contribs) |
Mixedpuppy (talk | contribs) |
||
| Line 24: | Line 24: | ||
4. The chrome component of F1 accesses information in the browser content that currently includes: url, title, site name, short url, image previews. This data is gathered from OpenGraph meta tags, title elements, other meta tags, etc. | 4. The chrome component of F1 accesses information in the browser content that currently includes: url, title, site name, short url, image previews. This data is gathered from OpenGraph meta tags, title elements, other meta tags, etc. | ||
''Some of this data is inserted into DOM to be displayed to the user in the show panel browser.'' | |||
5. The chrome component posts messages to the share panel content. Data includes the user account object (including OAuth tokens), contacts gathered from the services, data gathered about the current tab (see #4). Some of these post messages may be in response to a post message received from the share panel content. It is assumed that the content will not store this data. It is assumed any or all this data may be sent onwards to the Python API server when a user shares. It is important to note that the URL to the Python API server is stored in the user preferences and may be overridden to point to any server. | 5. The chrome component posts messages to the share panel content. Data includes the user account object (including OAuth tokens), contacts gathered from the services, data gathered about the current tab (see #4). Some of these post messages may be in response to a post message received from the share panel content. It is assumed that the content will not store this data. It is assumed any or all this data may be sent onwards to the Python API server when a user shares. It is important to note that the URL to the Python API server is stored in the user preferences and may be overridden to point to any server. | ||