Not sure linking to the FTP mirror is all that useful. Here are the release notes: https://www.mozilla.org/en-US/firefox/22.0/releasenotes/
Highlights: WebRTC, asm.js, flexbox, and web notifications are present and enabled by default.
Highlights: WebRTC, asm.js, flexbox, and web notifications are present and enabled by default.
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...
The upcoming versions address this issue (in the end, it's all just CSS; for example: [0]).
[0] http://dxr.mozilla.org/mozilla-central/source/browser/themes...
[0] Opera, as far as I remember, has neither clipboard access nor a "paste" event, the POS.
This is one of the ways that pasting images from your clipboard into, say, an image hosting site can work.
I had a difficult time finding fuller explanations of the capabilities - mostly because there isn't a standard API across browsers yet - but here[1] are the relevant Safari docs.
There's also a working draft[2] from the W3C for a standardized API.
[1] http://developer.apple.com/library/mac/documentation/AppleAp...
Yes and no, the website can access clipboard data specifically when you're pasting as a user-triggered operation (C-v/M-v or "Paste" from a contextual menu) (that is the clipboard data is only accessible from the `paste` event).
This allows an application to access alternative representations (the clipboard can store multiple representations of the same data e.g. text and html and image and whatever, and the application can then pick the most appropriate — or all of them) and to pre-process clipboard data before inserting it programmatically. Very useful with e.g. RTE. Arbitrary clipboard access most definitely isn't allowed.
See http://www.w3.org/TR/clipboard-apis/#pasting-html-and-multi-... for security and privacy considerations.
> if yes, how can we disable this "feature"?
In firefox, probably by going to about:config and setting `dom.event.clipboardevents.enabled` to `false`. In webkit and MSIE (which have had the feature for ages) I have no idea.
document.body.addEventListener("paste", function(e){
console.log("paste event fired")
})
http://jsbin.com/odupog/1/edit
Either way, should alleviate some of the privacy concerns, as you can only get ClipboardData from elements where "paste" has a visible effect.
www.tokbox.com
disclaimer: BD @ tokbox
This is about the new syntax and current CR.
I'm not sure why you're asserting that when you're completely wrong. Not only did Firefox support the old flexbox, it still does as of Firefox 22: [0] still works and uses the old (and prefixed) flexbox syntax, and said old (and prefixed) syntax remains documented on MDN with a note that it's deprecated[1]
[0] http://www.the-haystack.com/2010/01/23/css3-flexbox-part-1/
[1] https://developer.mozilla.org/en-US/docs/Web/CSS/-moz-box-fl...
The old flexbox draft is similar to XUL boxes in some ways, and quite different in other ways. Trying to use XUL boxes and expecting the old-flexbox behavior as a result will land you in trouble, as happens with depressing regularity when people use "display: -moz-box".
The MDN documentation is sadly wrong, because it ignores the fact that the properties _look_ similar but have totally different behavior. Thank you for pointing that out; I'll make sure it gets fixed.