[Paid Software Announcement and Discussion] polobunny:
[MENTION=4317380]aminaked[/MENTION]

> You have provided me with version 21 to 38

Yet you accuse me of ignoring the issue. Admit that your accusations are unfounded and ignorant.

>>Which were all previous versions of Naked Browser. I don't believe that's a very difficult process uploading these. Correct me if I'm wrong.

> The issue only EVER happens on Naked Browser.

That is not in question. The question is how many people can reproduce the bug?

>> If you have access to a d2xxx device I can give you a CWM/TWRP backup of my current or a "blank" setup for you to experience the bug. I can make a freaking video of it, a thousand screenshots. Stock or AOSP based rom. I can't test on a crespo platform anymore, but I was able to reproduce it on it too.

> We're at least 2 users here with the bug present

Not really. azrash says "perhaps this is a webview bug" which sounds like he sees it in more than just Naked Browser.

>> Arguably, but does get the bug in NB (and not necessarily in other browsers...)

As for no other user, I don't believe android404 ever fixed the problem. Just moved on. You were in contact with him through PM if I'm not mistaken.

> If you're trying to put the blame on the users for using a widely accepted keyboard, then so be it.

If you are talking about SwiftKey go here: http://support.swiftkey.net/forums/116693-2-bug-reports/suggestions/3749006-nothing-is-written

I take requests and bug reports/write code/make apps available. What you are pulling here with me--getting emotional/blaming/arguing--is just wasting time.

>> I don't disagree with you on this one. I've offered my time at multiple times for you through PM with sporadic answers that lead to little. Do you have a bug tracker where users can comment/vote on current votes? This could help you keep your head out for a possible number of users affected by different bugs, including this one. As well as potential clues.

> But hey Tony, I love this browser and the only reason I am a bit miffed is because I care and I can see the potential in it.

Get angry at potential and you risk destroying it. Be angry at lack of potential.

>> My apologies, I'll agree this is getting a bit big. But I've waited a month between each private message session, requesting ANY sort of indication or suggestion from your part to help fix this. I have to bring it up otherwise you don't get back to me. Source code isn't available, I can't see how I am in power to fix this issue without your help. I don't think reverse engineering software to fix it is logical. And it's a great browser, with once again ton of potential.

> I want to see this bug get fixed once and for all.

If you knew how much time I have spent on this typing issue, you would know that no one wants it fixed more than I do. Yet in all this time, only 5 or so people have contacted me about it and some/all of them were experiencing a known WebView bug.

>> Which goes back to users finding a bug most likely just dropping the software or ignoring if they don't think it's relevant to comment on it. Most people don't go the effort of troubleshooting, they just ditch it.

You think I want bugs in Naked Browser? You think I have not been working on this and countless other bugs and features? I have never been able to reproduce your bug. You may be the only one experiencing it. Do not use Naked Browser if it does not work. Stay on topic and respect XDA forum rules.

>> Once again, I can't provide anything you need without you asking me anything you need... And NB used to work, I'm pretty sure.