View Issue Details

IDProjectCategoryView StatusLast Update
0017469phplist applicationInterface - Administratorpublic16-10-14 09:21
Reportercwrichardson 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.0.8 
Target Version3.0.XFixed in Version3.0.9 
Summary0017469: Bounce Rules table CSS precludes actually using the form
DescriptionThe table layout for applying candidate bounce regular expressions puts the checkboxes under the navigation sidebar, so you can't actually select them.
Steps To ReproduceDo
System -> Manage Bounces -> Generate Bounce Rules

Followed by
System -> Manage Bounces -> List Bounce Rules -> Candidate

Result is in attached screenshot.

This happens in both Safari and Firefox on OS X 10.9.5 on Macbook Air 13-inch, Mid 2012
phplist is running on
Linux 2.6.32-042stab092.2 #1 SMP Tue Jul 8 10:35:55 MSK 2014 x86_64 x86_64 x86_64 GNU/Linux
PHP 5.4.13 (cli)
Additional Information/lists/admin/ui/dressprow/css/style.css line 245 says:
tr.row td { max-width:100px;}

The DOM for the table says:
<tr class="">

I'm not yet familiar enough with phplist to know if
a) the .row class should be removed from that style line; or
b) a new style without the .row should be added; or
c) there's a bug somewhere in the backend, and it's failing to insert the class "row" in the DOM.

But doing (a) was sufficient to fix the problem for me.
TagsNo tags attached.

Activities

cwrichardson

11-10-14 13:03

reporter  

michiel

13-10-14 10:03

manager   ~0055402

great, thanks

michiel

14-10-14 21:26

manager   ~0055422


mariez can you check?

I don't have a Mac or Safari, and it renders fine for me (see att: rules1 and rules2)

Is it ok to remove the .row class?

See http://dev.phplist.com/lists/admin/?page=bouncerules&type=candidate

michiel

14-10-14 21:26

manager  

rules1.png (128,832 bytes)
rules1.png (128,832 bytes)

michiel

14-10-14 21:26

manager  

rules2.png (89,228 bytes)
rules2.png (89,228 bytes)

michiel

16-10-14 08:59

manager   ~0055441

I think it mostly happens when the 2nd column is pushed wide. Maybe we just need to restrict the size of that column.

michiel

16-10-14 09:21

manager   ~0055442

I've restricted the width. Should be fine now;