Hopeless battle with symptoms? Time to deal with the cause?
daffinm opened this issue · 8 comments
I found my way here after searching for a solution to the endlessly infuriating rubber-band-bounce issue on iOS. This project seems like the best solution to the problem on the internet. A lot of ingenuity, thought and effort has gone into it. And so it seemed like a good place to discuss this idea.
The problem here is that the damn rubber-band-bounce issue seems to keep coming back with each successive version of iOS - like some un-killable zombie creature... And the reason it keeps coming back to life is that this is a feature that Apple is deliberately adding because they think it is a good thing.
It seems to me, therefore, that the best solution would be to raise the issue with Apple and suggest that they provide a way of turning this feature off for people who don't want it. I think that there would be a lot of demand for such a switch and (given that the future of apps seems to be PWAs) this demand seems likely to grow.
Thoughts?
The reason why Apple isn't fixing this is because they want native apps where they get a 30% cut of the revenue whereas with a web app they get 0%.
You'd have a better shot at making your own browser than getting Apple to fix their UX conflicting with our web apps. Browser vendors view their browsers as what they are: "content browsers". So their intent is for people to be able to read articles and check medias like pictures in the best way possible.
The problem, is that we can't ship "apps built with web technologies". Instead, we have people accessing a "web page that behaves like an app".
You are probable right @AoDev. But a man can dream, can't he? :-)
Does anyone know where a person would go in order to raise my original idea with Apple?
@daffinm I suppose you can go to webkit website
Edit: this is their tracker
I've added another bug report. Here's hoping. This is a horrendous bug.
Anyone who's come here I encourage to submit another one. Let's inundate them with dupes.
This project was always just a hack, I hoped some day the behavior we were going for could be achieved with a simple meta tag, but here we are.
We probably need to get more creative in ways to prevent this behavior. I wonder if just dumping the entire page in an iframe and calling stopPropagation() on all touch events on the iframe itself would stop it...
Don't have any knowledge of IFrames myself but did almost have some luck with position fix on html but there's bad side effects.
My issue has at least got a response please add to it anything I've missed