Opened 15 years ago

Closed 14 years ago

#2928 closed defect (fixed)

LayoutContainer inside LayoutContainer has weird scrollbar

Reported by: guest Owned by: bill
Priority: high Milestone: 1.0
Component: Dijit Version: 0.4.2
Keywords: Cc:
Blocked By: Blocking:


If I have 2 nested LayoutContainers with the inner one having an alignment of "client". With this setup the inner LayoutContainer gets an unnecessary scrollbar. The scrollbar goes away if I force resize the window. This occurs in Firefox only. See testcase.

Workaround is to modify "dojo/src/widget/html/layout.js" where it says:

	".dojoLayoutContainer{ position: relative; display: block; overflow: hidden; }
" +
	"body .dojoAlignTop, body .dojoAlignBottom, body .dojoAlignLeft, body .dojoAlignRight { position: absolute; overflow: hidden; }
" +
	"body .dojoAlignClient { position: absolute }
" +
	".dojoAlignClient { overflow: auto; }

And swap the order of ".dojoAlignClient" and ".dojoLayoutContainer" so that ".dojoLayoutContainer" gets precedence.

Attachments (2)

splitcontainer.htm (752 bytes) - added by guest 15 years ago.
2928.html (1.0 KB) - added by bill 14 years ago.
Testcase against 0.9

Download all attachments as: .zip

Change History (6)

Changed 15 years ago by guest

Attachment: splitcontainer.htm added


comment:1 Changed 15 years ago by Adam Peller

Component: GeneralDijit
Owner: changed from anonymous to koranteng

comment:2 Changed 15 years ago by bill

Milestone: 1.0

Hmm it seems like we can get rid of dojoAlignClient altogether, since overflow: auto is the default.

comment:3 Changed 14 years ago by bill

Owner: changed from koranteng to bill

Changed 14 years ago by bill

Attachment: 2928.html added

Testcase against 0.9

comment:4 Changed 14 years ago by bill

Resolution: fixed
Status: newclosed

(In [10441]) Remove unnecessary dijitAlignClient { overflow: auto; }. It conflicts with the overflow:hidden for layout widgets when a layout widget is nested as a client of a LayoutContainer?.

Fixes #2928 and refs #4367 (fixes example #1 in #4367).

Note: See TracTickets for help on using tickets.