AlanOfTheBerg wrote:I think I found a bug: enter "barview, or" for a search. Two results, looking identical will come up. Clicking on or selecting either will not result in the Waze map showing the location, but looks like the search is being re-executed.
(There are two Barview, OR cities separated by a few hundred miles.)
pvaladares wrote:mike-bronner wrote:Timbones wrote:How hard will it be to port this to Chrome/Firefox?
I was thinking about this, but will need to do some more research. In theory, all the meat and potatoes is there, it would just need to be wrapped as a userscript.robin1979 wrote:Rename the .safariextz to .gz and see for yourself . Might just work as is (but I'm not that experienced extension coder, but you seem to be ).
That probably won't work, but you never know. I think the Framework that Safari Extensions are built upon is very different from other toolbars or userscripts like Greasemonkey.
I managed to unpack the .gzip safari extension.
At the Chrome Extensions Page, chrome://chrome/extensions, there is a "Pack extension"...
mike-bronner wrote:Patch 0.0.17 is now out -- more in the initial post.
AlanOfTheBerg wrote:mike-bronner wrote:Patch 0.0.17 is now out -- more in the initial post.
Bug in code:
console.log("Wazebar: error handling was triggered, but error object is empty.";
Missing closing paren.
Users browsing this forum: Google Feedfetcher, WC40WC