Project

General

Profile

Actions

Bug #2248

closed

J16: backend: radio parameters not aligned (visible e.g. in CB Privacy plugin)

Added by nant almost 14 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
26 January 2011
Due date:
% Done:

100%

Estimated time:
0:30 h

Description

See screenshot from latest CB 1.4 and J160.


Files

radio-parms.png (84.3 KB) radio-parms.png nant, 26 January 2011 09:23
2248.patch (997 Bytes) 2248.patch krileon, 27 January 2011 15:44
Actions #1

Updated by krileon almost 14 years ago

  • Status changed from New to Feedback
  • Assignee set to nant

This due to the following CSS in Joomla 1.6.x backend template.

IN: administrator/templates/bluestork/css/template.css
ON: Line 841
fieldset label, fieldset span.faux-label {
clear: left;
display: block;
float: left;
margin: 5px 0;
}

The below would need to be removed or overridden.

clear: left;
display: block;
float: left;

This would fix the labels. The below is causing the inputs to float.

IN: administrator/templates/bluestork/css/template.css
ON: Line 858
fieldset input, fieldset textarea, fieldset select, fieldset img, fieldset button {
float: left;
margin: 5px 5px 5px 0;
width: auto;
}

The below would need to be removed or overridden.

float: left;

Should be handled within CBs backend CSS file if possible?

Actions #2

Updated by krileon almost 14 years ago

Attached proposed patch, would need to be applied only to Luna as believe is only template were CSS is applied to backend.. probably should go in all templates anyway.

Actions #3

Updated by krileon almost 14 years ago

  • Status changed from Feedback to Resolved
  • Assignee changed from nant to beat
  • % Done changed from 80 to 100
Actions #4

Updated by beat almost 14 years ago

  • Subject changed from Wierd radio parameters for CB Privacy plugin parameters in J16 to J16: backend: radio parameters not aligned (visible e.g. in CB Privacy plugin)
  • Status changed from Resolved to Closed
  • Estimated time set to 0:30 h

Fixed as suggested in r1374
Thank you Kyle

Actions

Also available in: Atom PDF