Request for dojo.browser module

[ole]

Hi,

I think it would be intuitive to have a dojo.browser module that houses:

dojo.browser.getViewport() - currently slated for dojo.html...

dojo.browser.isFF

dojo.browser.isIE

etc.

So all things related specifically to the browser.

My personal feeling is that this declutters the dojo namespace, and puts getViewport() in a more intuitive place.

One positive side effect of having getViewport() in something like dojo.browser is it "frees" the concept / meaning of the namespace 'html' to focus on things HTML markup specific. I'm imagining dojo functions / classes that are markup specific laid out in a package / module structure like:

• html

• xml

• xml/svg

• xml/xhtml

• xml/mathml

• wml

• etc.

So when looking for utilities for processing mathml it's in the module dojo.xml.mathml, and when needing html specific code it's dojo.html.

Cheers,

• Ole

[ole]

This ticket is related to Ticket #7028:

​http://trac.dojotoolkit.org/ticket/7028

[James Burke]

I put your suggestion about the methods in #7028 might best be placed in another module besides dojo.html.

As for the other suggestions about moving things like isFF and isIE to browser modules: that sort of structure was explicitly avoided in the 1.0 redesign, to make common, Dojo Base functionality directly available off of dojo directly. So closing as wontfix.

[ole]

Sounds good - Thanks for updating 7028.