This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24797 - Stop using AbstractView
Summary: Stop using AbstractView
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Travis Leithead [MSFT]
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-25 11:11 UTC by Ms2ger
Modified: 2014-04-25 00:20 UTC (History)
6 users (show)

See Also:

Attachments

Description Ms2ger 2014-02-25 11:11:27 UTC 
In particular, UIEvent still has "readonly attribute AbstractView? view;". AbstractView is long dead.
Comment 1 Anne 2014-04-08 17:02:52 UTC 
Please link to the changelog.
Comment 2 Arthur Barstow 2014-04-08 21:04:42 UTC 
https://dvcs.w3.org/hg/dom3events/rev/ce11666f2d43
Comment 3 Anne 2014-04-08 21:10:04 UTC 
At least in Gecko this returns WindowProxy... Are we sure this should return Window?
Comment 5 Boris Zbarsky 2014-04-08 21:19:12 UTC 
WindowProxy and Window are the same thing in Gecko's WebIDL.  There is never a raw Window returned to script as a capturable object; it's always a WindowProxy.

I have no clue what the spec behavior of that is, since the spec state of WindowProxy is pretty broken (e.g. it's not an IDL object at all).

My suggestion would be to consistently use Window in WebIDL, with the understanding that in practice what you actually get is a WindowProxy...
Comment 6 Anne 2014-04-08 21:50:41 UTC 
"understanding" is not a requirement. We need to fix this somehow and it needs to be crystal clear. What is the bug on WindowProxy? I suggest we make this depend on that.
Comment 7 Boris Zbarsky 2014-04-08 22:01:15 UTC 
I'm not sure there's a bug (apart from bug 20701), just mailing list threads.
Comment 8 Travis Leithead [MSFT] 2014-04-22 00:22:05 UTC 
Since WindowProxy is the secure way to return Window (which is the pattern used in HTML5), DOM Events needs to have this be a WindowProxy as well.
Comment 9 Boris Zbarsky 2014-04-22 02:42:15 UTC 
Fwiw, since there is no actual IDL for WindowProxy, writing "WindowProxy" in WebIDL is technically just invalid WebIDL...
Comment 10 Travis Leithead [MSFT] 2014-04-25 00:20:14 UTC 
I changed the IDLs to WindowProxy, and did a pass through the document for the terms "defaultView" which was the term in vogue prior to a more standardized and well-defined window object. Now there is no more use of the term defaultView, and instead Window and WindowProxy are used where appropriate.

https://dvcs.w3.org/hg/dom3events/rev/c2837d35f150