Live data from Hacker News

Introducing Safari Technology Preview

webkit.org

101–110 of 176 posts

Re: Introducing Safari Technology Preview

#101
post #94
post #71

Earlier quoted context omitted.

That's why they only get the ability to programmatically trigger cut and copy, not paste.

Mozilla has it documented. Didn't see anything on the linked site. https://developer.mozilla.org/en-US/docs/Web/API/Document/ex...

Firefox only makes execCommand("paste") available in trusted contexts aka extensions. You can't execCommand("paste") on a regular web page for fairly obvious security reasons.

Re: Introducing Safari Technology Preview

#102
post #86

Earlier quoted context omitted.

I guess there's room for an attack of irritation where a user with something meaningful on their clipboard unwittingly triggers having it overwritten by some nonsense. (Most clipboards effectively being a single mutable item without history or stack/queue behaviour).

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.

Re: Introducing Safari Technology Preview

#103

Earlier quoted context omitted.

I do wonder why they didn't go with an API that other browsers are already supporting, though: https://developer.mozilla.org/en-US/docs/Web/API/ClipboardEv...

Did you consider reading the page you linked to? Clipboard events are already supported by safari (which the page you've linked to notes) and they've got nothing to do with execCommand, they are about hooking and reacting to user-triggered clipboard operations e.g. the user pastes (via contextual menu or shortcut), the software can know about it and alter the content before it's pasted. execCommand is about programma…

Did you consider removing the first sentence of your post and it would have been less smug and taunting, leaving behind something that lifts up the conversation?

Re: Introducing Safari Technology Preview

#104
post #77

Earlier quoted context omitted.

They did release Safari for Windows. Nobody used it, and I guess they figured the cost of upkeep wasn't worth it.

As an end user it was pretty bad (with all the libraries they were using). It mainly seemed to exist so Windows only shops could develop/test their websites on iPhones and iPads without having to own that hardware. As iPhones and iPads became ubiquitous (as well as the popularity of Macs with developers) that didn't seem to be enough reason to keep it going. I don't think Apple ever intended to win the browser war, I…

Yep Safari for Windows was released at WWDC 2007 (~2 weeks before the iPhone went on sale), and I'm sure part of the rationale was for Windows developers to be able to test their web sites with it.

Also note that Google Chrome wasn't released until September 2008, so there was a year+ where Safari was the most prominent WebKit-based browser on Windows.

Re: Introducing Safari Technology Preview

#105
post #77

Earlier quoted context omitted.

They did release Safari for Windows. Nobody used it, and I guess they figured the cost of upkeep wasn't worth it.

As an end user it was pretty bad (with all the libraries they were using). It mainly seemed to exist so Windows only shops could develop/test their websites on iPhones and iPads without having to own that hardware. As iPhones and iPads became ubiquitous (as well as the popularity of Macs with developers) that didn't seem to be enough reason to keep it going. I don't think Apple ever intended to win the browser war, I…

Yep Safari for Windows was released at WWDC 2007 (~2 weeks before the iPhone went on sale), and I'm sure part of the rationale was for Windows developers to be able to test their web sites with it.

Also note that Google Chrome wasn't released until September 2008, so there was a year+ where Safari was the most prominent WebKit-based browser on Windows.

Re: Introducing Safari Technology Preview

#106
post #86
post #71

Earlier quoted context omitted.

That's why they only get the ability to programmatically trigger cut and copy, not paste.

I guess there's room for an attack of irritation where a user with something meaningful on their clipboard unwittingly triggers having it overwritten by some nonsense. (Most clipboards effectively being a single mutable item without history or stack/queue behaviour).

Tynt basically did this exact thing as a business model[0].

[0] http://daringfireball.net/2010/05/tynt_copy_paste_jerks

Re: Introducing Safari Technology Preview

#107
post #93

Earlier quoted context omitted.

They did release Safari for Windows. Nobody used it, and I guess they figured the cost of upkeep wasn't worth it.

While it was pretty bad, I remember Safari for Windows rendering text much nicer than any Windows browser (or app) at the time - particularly, the font smoothing. I recall using Win Safari to take "marketing" screenshots of an web app.

I agree. Sleipnir claims to still provide this font smoothing on Windows. http://www.fenrir-inc.com/us/sleipnir/

Re: Introducing Safari Technology Preview

#108

Earlier quoted context omitted.

Did you consider reading the page you linked to? Clipboard events are already supported by safari (which the page you've linked to notes) and they've got nothing to do with execCommand, they are about hooking and reacting to user-triggered clipboard operations e.g. the user pastes (via contextual menu or shortcut), the software can know about it and alter the content before it's pasted. execCommand is about programma…

Did you consider removing the first sentence of your post and it would have been less smug and taunting, leaving behind something that lifts up the conversation?

> Did you consider removing the first sentence of your post and it would have been less smug and taunting

Did you consider taking your own advice?

> leaving behind something that lifts up the conversation?

What are you talking about? There is no conversation, and what this subthread needs is not uplifting is euthanising.

Re: Introducing Safari Technology Preview

#109

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!

It's probably only a matter of time but I worry that some advertisers copy ad links to my clipboard. With flash, I had to allow it at least...

Re: Introducing Safari Technology Preview

#110
I find Safari to be the nicest browser to use in general, but Chrome seems to have a leg up on performance in key areas like new tab creation especially when opening a link in a new tab.

It's weird lapse for Safari to lag in certain situations. I hope they continue to iteratively improve the performance of the general UI and improve the general behavior of the developer tools in addition to adding these new techs.

Post reply on HN