Igor Kozlov

@peunoir thanks for `routeSegmentChange`. Haven't crossed my mind to look for an event in the code :)

@MatthieuLemoine Chrome 50+ allows receiving payloads within notification but to send this payload the back end needs those keys for encryption. https://developers.google.com/web/updates/2016/03/web-push-encryption

No progress here?

another bug related to this is that when you try to use the old syntax like ``` background-image -webkit-gradient(linear, left top, left bottom, from(#7497dd), to(#658cd9)) ``` it renders ``` background-image:...

looks like the JSX fragment issue was fixed in the original grammar long time ago (https://github.com/Microsoft/TypeScript-TmLanguage/pull/535) but the changes were never copied to this repo

I ended up with the same exact question. The issue is half a year old, so I'll try to bump it. @gaearon can you please answer this one?

What an awful hack. The same could be achieved by dropping everything related to the HTML5 history. ``` javascript // HTML5 History exists and new_location is a full path //...

Looks like nobody is getting this, so I'll try tagging @infininight

Actually I do miss something. Those constants should be separated into two types: objects and properties. Objects like `window`, `console`, etc should stay with the old `match` regexp ``` bash...

Per-runtime grammars sounds like a bad idea since I don't see any way to automatically distinguish Browser and node.js code for example.