chrome-extension:// is not a supported protocol

[gkovacs]

I'm trying to use this extension to develop the options page for a chrome extension of my own, which was side-loaded from the filesystem. However, when I click the LivePage icon while navigated to the options page URL (which has protocol chrome-extension:// ) it tells me that it is an unsupported protocol. Could you either add support for the chrome-extension:// protocol, or make it such that I can just specify the path to my extension's files and it'll reload that page whenever a file is edited?

[MikeRogers0]

This is a duplicate of #86 - I'm working on making this option a power feature in the next release. I'm aiming to for an early February release :)

Also, best of luck on your extension!