Radek Matěj

I struggled with the same thing and I solved that by setting class to the map element and styling it with CSS. Which I believe should be the best practice...

I don't think so. I settled up with deleting cache manually using [cron](https://en.wikipedia.org/wiki/Cron).

I have found a workaround. This scrolls the focused input to the top of visible area: ```javascript document.addEventListener('deviceready', function() { Keyboard.shrinkView(true) window.addEventListener('keyboardDidShow', function () { document.activeElement.scrollIntoView() }) }) ``` If...

Here is the minimal code to reproduce this issue in the browser: ```js import React from 'react' import { Router, Switch, Route } from 'react-router-dom' import { createBrowserHistory } from...

Sure. If user input is: `Take look at https://www.google.cz/?gfe_rd=cr&ei=GYmlWM-VG_Tf8geNmIfYDA#q=autolinker and hi` I need to render: `Take look at https://www.google.cz/?gfe_rd=cr&ei=GYmlWM-VG_Tf8geNmIfYDA#q=autolinker and <a href="javasript:alert('hi')">hi</a>` So html characters `&"'` are escaped **everywhere except...

We both probably agree that Autolinker output is meant to be inserted into HTML. And that the original input we want to transform comes from the website user. For example...

Side note: I already decided for Linkify over Autolinker because of this. But I would like to understand how do you expect this to be handled. Probably I'm just missing...

After further investigation it seems that Autolinker behavior is very similar to [linkifyHtml method](http://soapbox.github.io/linkifyjs/docs/linkify-html.html), which preserves HTML tags compared to [linkifyStr method](http://soapbox.github.io/linkifyjs/docs/linkify-string.html) which escapes them. **Input:** `Pause & look at...