Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#7262 closed enhancement (wontfix)

Request for dojo.browser module

Reported by: ole Owned by: anonymous
Priority: high Milestone: tbd
Component: General Version: 1.1.1
Keywords: Cc:
Blocked By: Blocking:



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

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




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.


  • Ole

Attachments (1)

browser.js (1.6 KB) - added by ole 14 years ago.

Download all attachments as: .zip

Change History (4)

Changed 14 years ago by ole

Attachment: browser.js added

comment:1 Changed 14 years ago by ole

This ticket is related to Ticket #7028:

comment:2 Changed 14 years ago by James Burke

Resolution: wontfix
Status: newclosed

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.

comment:3 Changed 14 years ago by ole

Sounds good - Thanks for updating 7028.

Note: See TracTickets for help on using tickets.