Closed stienessen closed 12 years ago
Well, it’s actually not possible to bind XV on specific content-type (because of Chrome API limitations), but I’m thinking about adding a button on omnibar to force any page to be viewed in XV
I would love to see a button to force content to XV!!
sorry - didn't mean to close the issue -
Is there a way to force content to view in XV? I want to use it to view .log files.
It’s possible only if content page is served with xml content-type
I was actually looking in the code to see if I could modify for other content-types to see OData feeds. Button idea would be a nice workaround. If you have some pointers as to how to accomplish that I'd be happy to contribute.
When viewing a site which produces "Content-Type:text/xml;charset=UTF-8" the extension does not kick-in when using Chrome. RFC3023 has standardised:
I
Just pushed update of XV extension. It provides page action (icon in address bar) which can force rendering of current document with XV. If document is valid XML, it will be rendered with XV. Let me know if it works for you.
love the viewer - any possiblity of adding support (maybe by configuration) for other content-types? i.e. I'm looking for application/atom+xml to view OData feeds.