Adding a feedback button to your Flare HTML5 output


Are you looking for instructions on how to add an e-mail feedback button to the toolbar of your MadCap Flare HTML5 output? And would you like a copy of the relevant URL included in the e-mails you get? Keep reading.

Open your Flare project, and follow these steps to add a feedback button to the toolbar:

  1. Go to the Project Explorer > Skins and open the HTML5 skin.
  2. Go to the Toolbar tab and add a new button called (e.g.) Feedback.
  3. Go to the Styles tab and find the sub-node called Toolbar Button > Feedback.
  4. In the Properties section, expand the Event node and add the following Javascript to the node: window.location=’mailto:your@emailhere?subject=<‘ + escape(window.location.href) + ‘>’;
  5. Expand the Background node and set Background Image to (e.g.) feedback.png ().
  6. Save the HTML5 skin and view your HTML5 output.  Here’s an example of the output.

When you click the feedback button, your default e-mail client opens, and the URL of the current page is displayed in the subject field.

Have fun! 🙂

Advertisements
Tagged with: , , ,
Posted in Javascript, MadCap Flare
3 comments on “Adding a feedback button to your Flare HTML5 output
  1. […] To reduce the administration effort even further, you can set up a nightly webhelp batch build of e.g. the topics that are ready for review, and automatically send an e-mail to your reviewers asking for their feedback. To make it as easy as possible for them to supply comments, you can add a feedback button to your topics (for more info, see Adding a feedback button to your HTML5 output) […]

    Like

  2. rhh8Ruth says:

    Hi! help! I’ve implemented this but my Flare 9 compilation is reporting a couple of errors:

    CSS Parser: Line: 1. Char: 12. Invalid token (.)
    CSS Parser: Line: 1. Char: 108. Missing identifier (property)

    I don’t know which “.” is invalid or what property might be missing (Flare’s usual brilliant error reporting).

    It works fine and there are no javascript errors on the page but I don’t like my build output to contain warnings/errors/precuations about missing things.

    Any ideas?
    Thanks
    Ruth

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: