4 ms·
Apple broke a fundamental rendering issue in iOS 9.2 - if you put overflow hidden into the body tag then it screws up the viewport. Thousands and thousands of
by chris_wot 11y ago
Apple broke a fundamental rendering issue in iOS 9.2 - if you put overflow hidden into the body tag then it screws up the viewport.
Thousands and thousands of pages broke. They fixed it three months later.
Basically, Apple Safari support sucks. Why the hell is their web page renderer only updated in minor releases of iOS?
- chris_wot 11y agoOh? Genuinely curious: what's so awful about my comment? If Apple can stuff up a fundamental rendering issue [1] and it takes them 3 months to release a simple revert of the unreviewed commit, then how are my comments on their incredibly slow bug fix timeframes for browser issues out of line? 1. https://bugs.webkit.org/attachment.cgi?id=268394&action=diff https://bugs.webkit.org/attachment.cgi?id=268394&action=diff
- uxp 11y agoWhile I agree with the content of your comment, this one at the bottom of the page seems to be the third of nearly identical comments about this one WebKit bug made by your account on the page. It's approaching my SPAM threshold.
- chris_wot 11y agoIndeed - I found this bug to be totally relevant to the issues being discussed. The first was to point out the issue. The second (the parent comment) was to ask why Safari rendering bugs take so long to fix and I used that bug as context for my question. The third was to respond to the huge downvotes of this comment at https://news.ycombinator.com/item?id=11376114 https://news.ycombinator.com/item?id=11376114 Each of those are entirely relevant in their context. It's hardly spam. If you want, I'll find more regressions, it won't be hard. Apple are utterly useless when it comes to Safari rendering regressions. (were you the one downvoting, incidentally? And what do you mean by the "third at the bottom of the page"? The comments shift around in ordering you know)
- mikestew 11y agoAnd what do you mean by the "third at the bottom of the page"? The commenter meant that the referenced comment was the third such comment you've made in relation to this bug. IOW, you're sounding like a broken record. I tend to agree with this assessment. You made your point, move on. And before you ask, meh, maybe I down voted you, maybe I didn't. That's not what you should be focusing on.
- chris_wot 11y agoMeh. I had no intention of referencing it again, those comments were entirely relevant. That's indeed what I'm focussing on. In fact, I'm focussing on the fact that Apple's updates for Safari entirely suck and used that bug as the primary example of just how bad they are. I don't apologise for being a "broken record" on this issue. Maybe you should also. Next time I'll find one of the dozens of other regressions that have bit me in the arse if that would make you happy. This bug was so bad that if Apple hadn't fixed the issue in iOS 9.3 then I would have asked for a refund on every single one of my devices and returned them. Under Australian law they'd have to.