Skip to main content
This topic is closed to new replies. Start a new post to keep the conversation going.
Willam van Weelden
Willam van WeeldenCorrect answer
Inspiring
Feb 27, 2015 8:11 AM UTC

I talked to Adobe about this and it is by design. I dropped the ball on this one.

You can add the Responsive output from RH to SP just fine. The file extension is aspx but the master page is not used.

The reason for this is as follows: The responsive output used media queries to determine the correct output view. Embedding it into SharePoint using master pages breaks the media queries. For Multiscreen HTML5, the device is determined by theoutput and there is no dynamic settings in the CSS. Therefore it can use master pages.

You can change the doctype for the ASPX headers and it should work. (You'll need a few more changes. Simply generate Multiscreen and apply the <% options in the index.aspx output file.)

A better solution might be the following:

  1. Upload your Responsive help to Sharepoint.
  2. Add a page viewer Web Part..
  3. For the link of the web part, add the URL to the help system you uploaded in part one.
  4. Change the dimensions of the page viewer to optimize you help.

You can now use Responsive Help in SharePoint while showing the SharePoint context.

Kind regards,

Willam

View reply

4 replies

Regiolanthe1Author
Known Participant
Feb 26, 2015 9:04 PM UTC

Stupid m5 can't post error!

Anyhow - all content is published successfully to SP library in native (aspx) format.

However, when I click the Index, the pages launch in full browser mode (without the SP navigation / banner wrapper).

Not sure if I need a special SP Master page. This is just a standard SP document library - and I do not have SP Designer privileges.

Are there some library settings that force content to show within library?

Translate
Regiolanthe1Author
Known Participant
Feb 26, 2015 10:27 PM UTC

Answering my own question - this appears to be related to the bug noted by Willam van Weelden (thank you!).

I generated Responsive HTML, and it simply did not port over as an .aspx file (even though it had the correct extension). Viewing file source indicated it was DOCTYPE HTML - as noted by Willam in this forum post.

Not impressed if this bug has indeed been kicking around since October or earlier ... I thought that the SharePoint piece was a selling point.

Regards,

George Oakes

Translate
Willam van Weelden
Willam van WeeldenCorrect answer
Inspiring
Feb 27, 2015 8:11 AM UTC

I talked to Adobe about this and it is by design. I dropped the ball on this one.

You can add the Responsive output from RH to SP just fine. The file extension is aspx but the master page is not used.

The reason for this is as follows: The responsive output used media queries to determine the correct output view. Embedding it into SharePoint using master pages breaks the media queries. For Multiscreen HTML5, the device is determined by theoutput and there is no dynamic settings in the CSS. Therefore it can use master pages.

You can change the doctype for the ASPX headers and it should work. (You'll need a few more changes. Simply generate Multiscreen and apply the <% options in the index.aspx output file.)

A better solution might be the following:

  1. Upload your Responsive help to Sharepoint.
  2. Add a page viewer Web Part..
  3. For the link of the web part, add the URL to the help system you uploaded in part one.
  4. Change the dimensions of the page viewer to optimize you help.

You can now use Responsive Help in SharePoint while showing the SharePoint context.

Kind regards,

Willam

Translate
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices