Apple is about to make a series of improvements to the Safari mobile browser. These fixes in the latest update are said to make web browsing experience, especially scrolling web pages, way smoother than ever. As of now, a lot of web pages doesn’t let you scroll smoothly while certain pages and mostly the Google’s AMP pages let you scroll smoothly without any lags. Also Read - Apple iPhone 15 is rumored to support Wi-Fi 6E networkAlso Read - Android 14 might block outdated apps to help reduce malware attack
AMP or the Accelerated Mobile Pages system by Google speeds up page navigation and scrolling. Scrolling web pages in Safari is different to all other scrolling in iOS. AMP breaks certain key features on the Safari browser such as tapping on the top of the screen can take you to the top of the page and top and bottom bars auto-hide, Engadget quotes and Apple engineer named OM2. Also Read - Apple files a new patent for crack-resistant foldable display tech
So if a page is AMP-ed then Google gains a lot of control on its behavior across devices. In the case of Safari, the search engine giant uses an aspect of the iOS system which allows it to override the default scrolling and subsequently AMP Pages become faster to browse. Certainly, AMP saves data and boosts speed but not all developers and content managers like it. ALSO READ: Apple HR head Denise Young Smith promoted to VP of Diversity and Inclusion
According to HackerNews and DaringFireball notes, the issue was reported to Apple and now the Cupertino giant has promised ‘to make the default scrolling like the overflow scrolling’. With the new release of Apple Safari, all web pages will be offer smooth scrolling as the AMP pages. Notably, the issue seems to be in place because Apple made an intention decision to do so in the first place.
Also, an another bug is noted in Safari’s Reader Mode while browsing AMP pages. If you perform an in-page search then it doesn’t let the browser find instances of the search keywords on an AMP page. Apple is said to have WebKit update planned to fix this issue soon.