281376 - Provide interfaces for DOM host objects

Status: RESOLVED INACTIVE

(Rhino Graveyard :: Core, enhancement, P5)

Description

[Daniel Gredler]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Most JavaScript is used to manipulate HTML documents (ICEBrowser, HttpUnit,
HtmlUnit, etc). It would be nice if Rhino had interfaces for the DOM objects
(Window, Input, Page, Navigator,etc) that each of these projects could then
implement as necessary when creating their host objects. Would such interfaces
be accepted for inclusion? For example:

public interface INavigator {
    public String  jsGet_appCodeName();
    public String  jsGet_appMinorVersion();
    public String  jsGet_appName();
    public String  jsGet_appVersion();
    public String  jsGet_browserLanguage();
    public boolean jsGet_cookieEnabled();
    public String  jsGet_cpuClass();
    public boolean jsGet_onLine();
    public String  jsGet_platform();
    public String  jsGet_systemLanguage();
    public String  jsGet_userAgent();
    public String  jsGet_userLanguage();
    public Object  jsFunction_plugins();
    public boolean jsFunction_javaEnabled();
    public boolean jsFunction_taintEnabled();
}

The interface could also include documentation for each property/method,
including browser-specific anomalies, doc links, etc.

Thoughts?

Reproducible: Always

Steps to Reproduce:

Comment 1

[Igor Bukanov]

Reassigning to [e-mail] pending resolution of bug 288433

Comment 2

[Norris Boyd]

Changing priority to P5 based on recent bug triage.

Comment 3

[Sylvestre Ledru [:Sylvestre]]

Closing. Bug management is now done here:
https://github.com/mozilla/rhino