OP here. This might be a classic Hacker News sentiment that's not shared by normal users. Being able to instantly return to where you were without having to navigate apps is probably appreciated by a lot of people. (As would be preloading in this instance).
FWIW when I first started browsing HN a common complaint was websites being mobile sized. The sentiment here was they should be rendered in full desktop and require pinch-zooming and scrolling in all directions.
My wife just didn't know what a web view was (she still doesn't), but she prefers using the browser after I showed her how to "escape" Facebook's web view and open pages in Safari where the content blocker and ad blocker extensions could do their work. You probably have a point about preloading pages, but until content and ad blockers start working in all web views, then I agree with the person you're replying to: nobody wants a damn web view.
Meanwhile a WebView will show whatever HTML you throw at it, but it won't do any of that other fun stuff because the app that created it can access and manipulate the content (e.g. stealing your passwords) and the OS doesn't know if content filtering is relevant in that webview (since it's just the "show some HTML in a browser-type view" control and maybe it's important to see everything as-is). Being able to access the WebView also means the app can watch where you browse, what URLs, etc. so it can see what you're looking at even once you leave the page it opened to.
So yeah, apps can have a user-friendly experience; Telegram for the longest time used a SafariWebView so that everything was nice and neat. Then they decided to change their UI to a regular WebView and suddenly everything was full of trash again and I had to set it to "open in Safari" instead.
That was partly due to websites being broken. You can still find some old discussions on Stack Overflow about features of their websites not working correctly in it: https://stackoverflow.com/questions/27000708/file-upload-con...
And if they didn't, it was not for lack of trying... What does it take for people to delete this shit?
I remember that this "became news" some time ago, but it's always pretty obvious the moment it loads.
App presenting an SFSafariViewController? "Convenience" that's intended to keep users in the app.
App presenting a WKWebView? Assume it's loaded with spyware scripts.
TBF it's "only" sites with a meta pixel, and on Android. But in my book this does not matter, it shows their intentions
I'm sure there's also no user-controlled firewall to stop it on Android either.
The back button supplied by the OS is perfectly capable of this (at least on Android I have witnessed this)
The webviews don't have adblock so they fall for ads and scams, sometimes they don't properly follow UI scaling, they don't have the cookies or saved passwords needed to, for example, read a paywalled newspaper article that someone linked...
I think you misunderstood. The problem wasn't/isn't that sites were mobile sized on mobile devices. The problem was/is sites that optimize for mobile, and look terrible or are hard to use on a desktop or laptop screen.
They're also often very confused why they can't find links they've opened in web views in their browser's tabs or history.
Slack, Teams, confluence, jira, etc all open a pdf in a in-browser preview thing. Then if you try scrolling, it makes the PAGE contents bigger, but does NOT zoom into the pdf.
Who thought of this? Who thought it was a good idea?
Never have I wanted to open a preview of the pdf.
Also, it can be useful to keep the PDF in the context of the app you opened it in. Unfortunately, I'm not aware of a window manager that surfaces the fact that, for example, one macOS Preview window was opened from the browser, another from Slack, another from Finder, etc. Compare to iOS, where opening a PDF viewer from an app will result in a button at the top-left corner to go back to the app you opened it from.
The previous comment was not talking about the browser viewer, it was talking about various website viewers, like the one by Jira.
I agree website viewers are pointless. But most of the time I actually like the browser viewer better, if it opens links directly, than offline viewers. Because I regard PDFs as websites (similar to jpeg files), and I normally don't want to accumulate them in my download folder.
I agree though that the browser viewers are often too bare-bones.
Which tend to be, imo, even worse! I think I'd rather have a toner container explode on me than try to suffer through the experience of using Aconex's PDF utility ever again.
Twitter's handling of opening links in its own webview is a bit different, unless Slack, Teams, Confluence, Jira all open these browser instances within some sort of webview wrapper as well(I wouldn't think so). So its a little bit different
I assume they are trying to be "helpful" but 99% of the time the user's browser can render the PDF more conveniently than the app's embedded viewer (not breaking scrolling and zooming etc.)
I didn't think IG does something similarly shady