111–120 of 176 posts
Earlier quoted context omitted.
Yeah, don't go to booking.com :-)
So a particular website goofing something up is Safari's fault? (Incidentally, just went to Booking.com on iOS Safari. Works fine here.)
Earlier quoted context omitted.
There's easier ways to irritate your users. Most websites irritate their users, actually.
Speaking of clipboard shenanigans. Could be imagining it, but I seem to remember a while ago there being something certain websites were doing where if you selected and copied text from them, the text that ended up on your clipboard would have a synthesized paragraph about copyright/attribution appended to it.
Anyone know if they plan on introducing support for Service Workers ("Progressive Web Apps" in Google parlance) soon?
Earlier quoted context omitted.
most of my settings came over through iCloud - I don't think last browser session or extensions are very important for them to support pulling across.
I have about 10 windows with umpteen tabs open. I do not want to go through the process of replicating that. Same with extensions.
[Edit: A brief look makes it appear that native OS X apps can, not sure about Safari extensions. But a native app could be sufficient.]
Earlier quoted context omitted.
WebKit runs on Windows. It's not Apple's task to package it nicely for you. Chrome was using WebKit a long time, Blink is a WebKit fork. Both run on Windows.
> WebKit runs on Windows. WebKit != Safari or Chrome or anything else. Safari has quirks that you cannot experience without using Safari itself, which you still cannot run without a Mac. When you've wasted hours trying to track down one of these issues and realise it's a Safari quirk you'll understand my annoyance. > It's not Apple's task to package it nicely for you. I'm not sure where you get this idea from given t…
Programmatic cut and copy to the clipboard It’s now possible to programmatically copy and cut text in response to a user gesture with document.execCommand('copy') and document.execCommand('cut'). Having this ability may eliminate some websites’ last need for the Flash plug-in. --- :'( - So much pain erased in a single stroke!
Unfortunately as far as I know the text selection API is still broken on mobile Safari. At least as of a few weeks ago the JS events associated with force touch seem to randomly wipe out the text selection, so even if you can now theoretically copy stuff to the clipboard it's largely irrelevant if users can't actually select text in the first place.
Apple's been taking a number of steps over the last few months to show that they take Safari/WebKit development seriously. This is another positive step in the right direction. While I never agreed with the nonsensical "Safari is the New IE" meme that was going around, I did fear that Apple's tendency to develop things in a vacuum would continue to harm WebKit relative to Blink, Gecko, etc. But all signs are pointing…
Their time to fix bugs and regressions in iOS is 3 months! Edit: Again, I write a very unpopular opinion. Yet there are hundreds of regressions that have bit developers. Some of those bugs require workarounds that would be otherwise unnecessary on any normal environment with rapid updates - like Chrome or Firefox. That increases developer effort, and there have been cases that Apple have entirely missed their update…
OP posited: “Apple's been taking a number of steps over the last few months to show that they take Safari/WebKit development seriously. This is another positive step in the right direction.”
You basically responded, “They're still not as good as I want them to be!” It's a point that has nothing to do with the original comment, which was about improvement, not perfection, and about how seriously they take Safari/Webkit development, not about their release process (which remains roughly the same as it has been for the past many years).
Additionally, regarding the workarounds you mention: they are unnecessary in a “normal environment with rapid updates” only when those developers decide to fix your bug. Again: rapid updates are only useful if your bug is being addressed. I've got workarounds in my code for issues in Firefox that probably won't be fixed anytime soon, and features that Firefox and Chrome support poorly that they won't support well for a while, etc, etc.
I'm not saying Apple couldn't be releasing bug fixes for Safari on any platform faster—they certainly could. But you made an unrelated complaint as a reply to a specific comment, and your argument seems suspect to boot.
Earlier quoted context omitted.
Unfortunately as far as I know the text selection API is still broken on mobile Safari. At least as of a few weeks ago the JS events associated with force touch seem to randomly wipe out the text selection, so even if you can now theoretically copy stuff to the clipboard it's largely irrelevant if users can't actually select text in the first place.
Can you file a bug with a specific example or two? http://bugs.webkit.org/
The basic issue we were encountering is that when selecting text via force touching and then dragging the selection, the text selection object was empty. (Though you can still hit Copy in the Safari UI.)
There wasn't any issue when selecting text via regular press or long press.
Anyone know if they plan on introducing support for Service Workers ("Progressive Web Apps" in Google parlance) soon?
This is what sticks in my craw about Safari: it feels like they are intentionally dragging their feet on this because it would bring the Open Web to parity with Native Mobile and their App Store. At least IE never had a built-in conflict of interest in upgrading.
As an end user, I really don't want the result of following a link to a website (or 'web app' if you must, because app all the things) to be a progressive web app that a) consumes 100s of MB of my mobile device storage, b) runs in the background draining my battery and using my limited cell data plan, and c) send who know what information to god knows where. All because I clicked on a link and hit OK on an innocuous prompt...
Some of the capabilities presumed by service workers aren't even available to native apps on iOS because of these very same issues - why would Apple grant them to random websites?