Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

mobiledoc-dom-renderer

Package Overview
Dependencies
Maintainers
2
Versions
52
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

mobiledoc-dom-renderer

Renders Mobiledoc input to DOM output

  • 0.6.4-0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
6.1K
increased by2.08%
Maintainers
2
Weekly downloads
 
Created
Source

Mobiledoc DOM Renderer Build Status

This is a DOM renderer for the Mobiledoc format used by Mobiledoc-Kit.

To learn more about Mobiledoc cards and renderers, see the Mobiledoc Cards docs.

The renderer is a small library intended for use in browser clients.

Usage

var mobiledoc = {
  version: "0.3.0",
  markups: ["B"],
  atoms: [],
  cards: [],
  sections: [
    [1, 'P', [ // array of markers
      // marker
      [ 0,            // marker type 0 (standard text)
        [0],          // open markups (by index)
        0,            // close count
        'hello world'
      ]
    ]
  ]
};
var renderer = new MobiledocDOMRenderer({cards: []});
var rendered = renderer.render(mobiledoc);
var result = rendered.result;
document.getElementById('output').appendChild(result);
// renders <div><p><b>hello world</b></b></div>
// into 'output' element

The Renderer constructor accepts a single object with the following optional properties:

  • cards [array] - The list of card objects that the renderer may encounter in the mobiledoc
  • atoms [array] - The list of atom objects that the renderer may encounter in the mobiledoc
  • cardOptions [object] - Options to pass to cards and atoms when they are rendered
  • unknownCardHandler [function] - Will be called when any unknown card is enountered
  • unknownAtomHandler [function] - Will be called when any unknown atom is enountered
  • sectionElementRenderer [object] - A map of hooks for section element rendering.
    • Valid keys are P, H1, H2, H3, H4, H5, H6, BLOCKQUOTE, ASIDE
    • Arguments are tagName, dom
    • A valid value is a function that returns an element
  • markupElementRenderer [object] - A map of hooks for inline element rendering.
    • Valid keys are B, I, STRONG, EM, A, U, SUB, SUP, S, CODE
    • Arguments are tagName, dom, attributes={}
    • A valid value is a function that returns an element
  • dom [object] - A native or SimpleDOM implementation of the DOM.

The return value from renderer.render(mobiledoc) is an object with two properties:

  • result [DOM Node] - The rendered result
  • teardown [function] - When called, this function will tear down the rendered mobiledoc and call any teardown handlers that were registered by cards when they were rendered
Rendering HTML

In a browser, rendering to HTML is simple:

var renderer = new MobiledocDOMRenderer();
var rendered = renderer.render(mobiledoc);
var html = rendered.result.outerHTML;

However on the server in Node.js, native DOM APIs are not available. To make server-rendering easy, this DOM renderer is SimpleDOM compatible. You may pass an instance of a SimpleDOM document and serialize its output. For example:

var renderer = new MobiledocDOMRenderer({
  dom: new SimpleDOM.Document()
});
var rendered = renderer.render(mobiledoc);
var serializer = new SimpleDOM.HTMLSerializer([]);
var html = serializer.serializeChildren(rendered.result);

This usage of the DOM renderer for rendering HTML has the advantage of allowing developers to easily implement cards that work in a server and client context.

sectionElementRenderer

Use this renderer option to customize what element is used when rendering a section.

var renderer = new MobiledocDOMRenderer({
  sectionElementRenderer: {
    P: function(_, dom) { return dom.createElement('span'); },
    H1: function(_, dom) { return dom.createElement('h2'); },
    H2: function(tagName, dom) {
      var element = dom.createElement(tagName);
      element.setAttribute('class', 'subheadline');
      return element;
    }
    /* Valid keys are P, H1, H2, H3, H4, H5, H6, BLOCKQUOTE, ASIDE */
  }
});
var rendered = renderer.render(mobiledoc);
markupElementRenderer

Use this renderer option to customize what inline tags are used when rendering a section's content.

var renderer = new MobiledocDOMRenderer({
  markupElementRenderer: {
    B: function(_, dom) { return dom.createElement('strong'); },
    A: function(tagName, dom, attrs={}) {
      let element = dom.createElement(tagName);

      for (let attr in attrs) {
        element.setAttribute(attr, attrs[attr]);
      }

      element.setAttribute('rel', 'nofollow');
      return element;
    }
  }
});
var rendered = renderer.render(mobiledoc);
markupSanitizer

Use this renderer option to customize how markup attribute values are sanitized. The renderer's default markupSanitizer only sanitizes href values, prefixing unsafe values with the string "unsafe:". All other attribute values are passed through unchanged.

To change this behavior, pass your own markupSanitizer function when instantiating the renderer. If your markupSanitizer function returns a string, that value will be used when rendering. If it returns a falsy value, the renderer's default markupSanitizer will be used.

var renderer = new MobiledocDOMRenderer({
  markupSanitizer: function({tagName, attributeName, attributeValue}) {
    // This function will be called for every attribute on every markup.
    // Return a sanitized attributeValue or undefined (in which case the
    // default sanitizer will be used)
  }
});

The default sanitization of href values uses an environment-appropriate url parser if it can find one. It's unlikely, but if the renderer is in an environment where it cannot determine a url parser it will throw. (This can happen when running the renderer in a VM Sandbox, like ember-cli-fastboot does.) In this case you must supply a custom markupSanitizer that can handle href sanitization.

Tests

Releasing

  • Use np (install with npm install -g np)
  • np <version> (e.g. np 0.5.2)
  • git push --tags

Keywords

FAQs

Package last updated on 06 Mar 2017

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc