Get Help app: Context Selector content not showing |
|||||
Issue descriptionArticle 96817 (https://support.google.com/chromebook/answer/96817) is shared with the Chromebook online Help Center, and has a small amount of content that's displayed via the tabbed "Context Selector," a gKMS/Redwood tool which surfaces platform-specific content for desktop, Android, & iOS. For example, Chrome OS content is under the "Computer" tab. However, the entire Context Selector element fails to appear in the Get Help app (see "Fix a problem" topic > "Start or stop automatically reporting errors & crashes" article). The reason for this is that only an HTML snippet is outputted into the JSON the app relies on for article content: <gkms-context-selector contenteditable=\"false\" id=\"7182441\"></gkms-context-selector> The Get Help app can do nothing with this. The snippet requires javascript to dynamically load tabbed content and URL parameters, which are not present on initial page load. And this does not work for the Get Help app which requires all content, that which is visible on load and/or visible later upon click, to be present in the article JSON at once, so that it can be displayed and utilized when a Chromebook is offline. An example of content which is not visible on load would be zippies (see "Get Started" topic > "Switch to a Chromebook" article or https://support.google.com/chromebook/answer/183061). Zippy content is hidden to users on page load, but exposed when a user clicks a zippy header. All zippy content is present in the article JSON which the Get Help app holds for offline use. In order for Context Selector elements to function properly for the Get Help app, all content needs to be present in article JSON. Once this content is made available via Redwood and/or the support content API, the Get Help app will need to be updated as well to include any necessary CSS and javascript required to make Context Selectors look and behave properly (as was done to make zippies work in the app). Example article JSON: chromiumos/src/platform/chromeos-assets/genius_app/offline/en/articles.json (note "zippy" classes present throughout for idea on how to structure Context Selector data).
,
Jun 8 2017
A secondary ticket needs to be created for the necessary updates to the Get Help app itself after the outputted JSON data is corrected. The new ticket would be dependent on, or "blocked by," this one since the work on the Get Help app cannot commence until the data is improved. The following can go into the new ticket, more or less: Once the content is made available for offline use via Redwood and/or the support content API, the Get Help app will need to be updated as well to include any necessary CSS and javascript required to make Context Selectors look and behave properly (as was done to make zippies work in the app; see http://crbug.com/514865 and http://cl/132015956)
,
Jul 13 2017
,
Aug 1
,
Aug 9
,
Jan 10
This bug had an unsupported status. Updating to Untriaged so someone will reevaluate.
,
Jan 10
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 Deleted