Opened 5 years ago

Closed 5 years ago

#18097 closed defect (fixed)

[regression] BorderContainer: can't disable gutters

Reported by: vigb Owned by: bill
Priority: undecided Milestone: 1.10.1
Component: Dijit Version: 1.10.0
Keywords: Cc:
Blocked By: Blocking:

Description (last modified by bill)

When setting gutters="false" or data-dojo-props="gutters:false" in declarative creation it won't hide the gutters.

When I set the gutters property in the bordercontainer source to false it still shows the gutters.

It worked OK in 1.8

Change History (5)

comment:1 Changed 5 years ago by vigb

  • In 1.8 setting gutters=false also removed client borders and padding around bordercontainer.
  • In 1.10 it only removes the "gap" between the clients. Is there a setting to get the same results, or should I hack with css / styles?

comment:2 Changed 5 years ago by Philippe Soares

This ticket is assigned to component "dojox/layout", but please note that the same problem happens for dijit/layout/BorderContainer.

comment:3 Changed 5 years ago by bill

Component: DojoX LayoutDijit
Description: modified (diff)
Milestone: tbd1.10.1
Owner: set to bill
Status: newassigned
Summary: Can`t disable gutters on bordercontainer[regression] BorderContainer: can't disable gutters

Yes, understood. Maybe adfcd3bd30fae997a8cb8a3891b8c5aa324f1c76 was a mistake and needs to be rolled back. I'll look at it when I get a chance.

comment:4 Changed 5 years ago by Bill Keese <bill@…>

Resolution: fixed
Status: assignedclosed

In 56d3a146ea74e4a73fd8bbe8a510c7e18c9b0521/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:4 Changed 5 years ago by Bill Keese <bill@…>

Resolution: fixed
Status: assignedclosed

In 6aeb5dd99fb2a554ffc53e131baac0c856ed410a/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 
Note: See TracTickets for help on using tickets.