boognish-rising
commented
2 months ago Here's an illustration of what I'm taking about. This is after it occurred, but as you can see the space is still occupied in some capacity but tapping on it accomplishes nothing
This isn't major, or it wasn't for me but I could see it causing headaches for anyone that painstakingly customizes and/or obsesses over their shortcuts/tiles. I haven't determined how to reproduce it 100% of the time yet but I'll keep at that, however, several times now when moving tiles (either reordering or organizing into/out of folders) one or more tiles has simply vanished. However, strangely, it also seems like it's still there because on occasion, the space it occupied is still occupied, however clicking on it results in nothing, as you'd expect from tapping a nothing-filled space. This issue has occurred at least 3 or 4 times now and I don't edit my tiles all that often, so I'd label it a "somewhat common" issue, or one that's fairly likely to occur for users that actually use NextNTP beyond the default config, at any rate.
As for the request, if you would be so kind to either update the Firefox addon store version to 2.0.1 or as an alternative (and perhaps simpler for you), provide the requisite XPI file as you have done with the CRX files needed on Chromium-based browsers. That is, assuming that installing from file via XPI is as easy in Gecko-based browsers as installing via CRX is in Chromium-based browsers. If my understanding of things is off anywhere, just lemme know. As always, thanks for everything, Eduard!
PS - I made the same request as part of my Firefox addon review for NextNTP, which you can obviously disregard but in that review, I also mentioned that in addition to the desktop addon store, you might consider adding NextNTP to the mobile addon store, since NextNTP really shines brightest on mobile/touch devices IMO. I don't know what all this might entail but I wouldn't blame you if you concluded it wasn't worth the effort, as I know app stores usually don't make things easy for developers (generally the opposite). I would hope Firefox might be different in this regard but wouldn't be surprised to learn that they weren't.