Opened 13 years ago

Closed 13 years ago

#7285 closed defect (fixed) methods are super-confusing

Reported by: alex Owned by: bill
Priority: high Milestone: 1.2
Component: Doc parser Version: 1.1.1
Keywords: Cc:
Blocked By: Blocking:


the current placeOnScreenAroundPoint, placeOnScreenAroundNode, etc methods all take a map of location preferences (e.g., "BT", "BL"), but their interaction with the actual placement code seems tenuous and difficult to predict. Furthermore, it's not documented nearly well enough by the in-code docs. The docs need to be updated and book pages added/expanded for these methods.

Change History (2)

comment:1 Changed 13 years ago by bill

Milestone: tbd1.2
Status: newassigned

OK, I'll fix for 1.2.

comment:2 Changed 13 years ago by bill

Resolution: fixed
Status: assignedclosed

(In [14611]) Proper documentation for dijit.placeOnScreen*() functions. Fixes #7285 !strict. (The aroundCorners argument is by it's nature confusing, but for back-compat concerns the best we can do now is to document it.)

Note: See TracTickets for help on using tickets.