which I'd rather not do, because I like Postman, but that's what happens when inconveniences are branded as Chrome deprecated the existing Chrome app platform (legacy-chrome-apps) a while back. If there's no way to resolve this issue by reverting to Postman 1, I'll have to give up and start using a different product. In other words: running Postman 2 makes it significantly harder to use the entire rest of my browser, which I'm sure you understand is a non-starter for a web developer.) Any time I switch back to Chrome from another app, I get the Postman window instead of the Chrome window. (It's not that having Postman as a separate window or app is problematic in itself, it's that Chrome still considers the Postman window to be one of its windows, so if I app-switch from Postman back to Chrome, the "real" Chrome window with all my tabs in it will not pop to the front. It was working just fine for me, and the upgrade to Postman 2 is causing some serious aggravation in my workflow. But then for me the question becomes: is there any way at this time to re-obtain a copy of Postman 1? If it's truly impossible to force Postman 2 to behave like other extensions, then I can accept that. Can you explain what it is about Postman that prevents the same approach from working? This doesn't appear to be a "restriction" that other extensions suffer from. They all work with a url of the form chrome-extension:///.html. There are several Chrome extensions that open in tabbed windows just fine: LastPass, AdBlock Plus, etc. I don't mean to beat a dead horse, but can you explain a little more about this?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |