Ignore:
Timestamp:
01/19/11 14:18:18 (13 years ago)
Author:
vronk
Message:
 
File:
1 edited

Legend:

Unmodified
Added
Removed
  • MDService2/trunk/MDService2/WebContent/style/cmds-ui.css

    r1076 r1081  
    7070.cmds-ui-block { margin: 2px; text-align: left;}
    7171
     72.cmds-elem-plus .detail,
    7273.ui-context-dialog { display:none; position:absolute; border 1px solid #A6C9E2; background-color: #fafaff; z-index:1; }
    7374
    74 .cmds-elem-plus .detail { display: none; border: 1px solid #A6C9E2;}
     75/* .cmds-elem-plus .detail { display: none; border: 1px solid #A6C9E2;} */
    7576
    7677.cmds-elem-prop {}
     
    8889.cmds-xmlelem .attributes .label {}
    8990.cmds-xmlelem .attributes .value {}
     91
    9092
    9193
     
    114116.value_input { width:32%; }
    115117.sc_cmds { }
     118
     119.result-header { float: right; }
     120.cmds-navi-header { float:right;}
     121/* hack, for weird behaviour, the (appearingly) same rules for result-header.paging-input and cmds-navi-header.paging-input
     122different render (cmds-navi-header.paging-input too small) */
     123.cmds-navi-header .paging-input { height: 1.2em;}
     124
    116125.paging-input { width: 3em; text-align: right; height: 1em;}
    117126
    118 .result-header { float: right; }
    119127.query {margin-right: 4px;}
    120128 
Note: See TracChangeset for help on using the changeset viewer.