User tests: Successful: Unsuccessful:
Pull Request for New Issue.
The Created by alias in com_content articles view is using a p tag inside the results table.
The usage of padds an extra spacing to the bottom of the row.
Very simple
| Status | New | ⇒ | Pending |
| Labels |
Added:
?
|
||
| Category | ⇒ | Components UI/UX |
@andrepereiradasilva the div elemet by which you replaced the p element is also a block element, see here: http://www.w3schools.com/html/html_blocks.asp.
So if p is not allowed, then div is also not allowed I assume.
@andrepereiradasilva A span should be ok because span is inline element. So maybe you can use a span instead of a div?
lol! i think you're right, let me test in the html validator.
The validator will tell you the same
forget it, i think that was only a rule on XHTML Strict DOCTYPE or something. You can have block level inside tables.
Anyhow this solves the space problem.
I have tested this item
successfully on eb0cb0a
I think it is more a question of css then p or div tag. P seems to me semantic more correct.
yes, true. was mistaken reggarding HTML block elements as said.
i think div or span or a simple br (when no css classes) is used most of the times.
hum ... just noticed the same problem in featured articles ...
@richard67 just ignore me this time :-), I think there is not right or wrong here, if div's are used most of the time, then I can live with div's
ok will correct the featured articles too
| Title |
|
||||||
| Milestone |
Added: |
||
| Title |
|
||||||
| Title |
|
||||||
I have tested this item
successfully on eb0cb0a
thanks
I have tested this item
successfully on eb0cb0a
| Status | Pending | ⇒ | Ready to Commit |
| Labels |
Added:
?
|
||
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-04-23 08:55:28 |
| Closed_By | ⇒ | rdeutz |
| Labels |
Removed:
?
|
||
| Milestone |
Removed: |
||
| Milestone |
Added: |
||
| Milestone |
Added: |
||
| Milestone |
Removed: |
||
I have tested this item
successfully on eb0cb0a
Good spot
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10050.