14600 2011-10-30 20:30:50 +0000 Spec element.setCapture / document.releaseCapture 2014-02-10 22:37:08 +0000 1 1 1 Unclassified WHATWG Unwelcome unspecified Other other RESOLVED NEEDSINFO P3 normal Unsorted 1 contributor mike brunoabinader danya.postfactum ian mike Ms2ger www-dom sideshowbarker+unwelcome oldest_to_newest 59240 0 contributor 2011-10-30 20:30:50 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Multipage: http://www.whatwg.org/C#head Complete: http://www.whatwg.org/c#head Comment: Spec element.setCapture / document.releaseCapture Posted from: 91.181.84.233 by ms2ger@gmail.com User agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0a1) Gecko/20111001 Firefox/10.0a1 59241 1 Ms2ger 2011-10-30 20:31:05 +0000 http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html 61841 2 annevk 2011-12-20 20:50:57 +0000 Seems to be done elsewhere now. http://dvcs.w3.org/hg/webevents/raw-file/default/mouse-lock.html 61864 3 Ms2ger 2011-12-21 09:15:36 +0000 I don't see how it specs setCapture/releaseCapture. 61865 4 annevk 2011-12-21 09:19:04 +0000 It seems to suggest that it is not going to be defined and remains Gecko proprietary. In any event, it's not going to be done in the DOM specification I think. 65807 5 Ms2ger 2012-03-20 08:21:40 +0000 (In reply to comment #4) > In any event, it's not going to be done in the DOM specification I think. Agreed. Mike was so kind to create an orphanage for this bug. 65852 6 ian 2012-03-20 17:26:35 +0000 Who else implements this? If it's just Firefox, should we file a bug on Gecko to drop it? 75472 7 mike 2012-10-06 04:01:55 +0000 Not sure what action is needed from me on this. 93251 8 danya.postfactum 2013-09-11 14:50:35 +0000 Why is this marked as RESOLVED? I can not find any spec, describing setCapture/releaseCapture. 93278 9 mike 2013-09-12 00:49:24 +0000 (In reply to Danil Kostin from comment #8) > Why is this marked as RESOLVED? > I can not find any spec, describing setCapture/releaseCapture. It's marked as NEEDSINFO until somebody expresses willingness to take some concrete action on it; e.g., somebody decides to implement it in a UA other than Gecko, or somebody volunteers to write a spec for it, or Gecko drops it for lack of other implementations. 93280 10 mike 2013-09-12 01:04:22 +0000 (In reply to Ian 'Hixie' Hickson from comment #6) > Who else implements this? Apparently IE does. And IE had it before Gecko, which is part of why Gecko implemented it. See the following message from 2008 (from you...) where you're asking for info about setCapture() on the whatwg and public-webapps lists: http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html [[ Would it be possible to add setCapture() (as supported in IE; see below) to DOM3 Events? It seems more appropriate to have it there than in HTML5. Note that I don't think we'd need releaseCapture(); we should just say that capture is canceled when the mouse is released if it was captured. This gets around the problem of unbalanced set/release. ]] You got no responses at all to that message, as far as I can tell. Afterward, Gecko went ahead and implemented it: And see https://bugzilla.mozilla.org/show_bug.cgi?id=503943#c4 > If it's just Firefox, should we file a bug on Gecko to drop it? I doubt Mozilla is going to want to drop it, given that at the time they implemented they were well aware that there was no spec and nobody other than IE had it and nobody else was planning to implement it.