Bug #56418: Missing margin/padding on content element fields - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (3)

Felix Kopp
Lorenz Ulrich
Marcin Sągol

Actions

Copy link

Bug #56418

closed

Missing margin/padding on content element fields

Added by Mathias Brodala over 10 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Felix Kopp

Category:

Backend User Interface

Target version:

6.2.0

Start date:

2014-03-16

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

TYPO3 Version:

6.2

PHP Version:

5.3

Tags:

Complexity:

Is Regression:

Yes

Sprint Focus:

Description

Editing a content element in the backend currently shows some fields without margin/padding:

Files

ce-fields-padding.png (6.26 KB) ce-fields-padding.png

Mathias Brodala, 2014-02-28 10:12

Subtasks 2 (0 open — 2 closed)

Bug #57211: ExtJS / normalize table th

Closed

2014-03-23

Actions

Bug #56950: Additional margin on top of ExtJS context menus

Closed

Ernesto Baschny

2014-03-16

Actions

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Task #55316: Upgrade normalize.css to version 3.0.0

Closed

2014-01-24

Actions

Has duplicate TYPO3 Core - Bug #56567: Palette form fields have no left padding anymore

Closed

2014-03-05

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Markus Klein over 10 years ago

Status changed from New to Accepted
Assignee set to Felix Kopp
Is Regression changed from Yes to No

Actions

Copy link

Updated by Mathias Brodala over 10 years ago

Do you care to explain why this is not a regression? It did look fine before and does not anymore now.

Actions

Copy link

Updated by Markus Klein over 10 years ago

Is Regression changed from No to Yes

Of course it is, sorry for that.

Actions

Copy link

Updated by Ernesto Baschny over 10 years ago

The problem is the new order of loading of the CSS files.

normalize now comes before ext-all-notheme, where the margin:0/padding:0 is set for many elements (including fieldset). This used to be the other way around.

The problem is that ext-all-notheme also contains his own "reset" CSS (line 21) which now takes precedence over normalize (as it overwrites it).

What to do?

Easiest and most backwards compatible way would be to switch them around again (loading ext-all-notheme as a "library" even before normalize) to get back the old behaviour.

Actions

Copy link

Updated by Gerrit Code Review over 10 years ago

Status changed from Accepted to Under Review

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28069

Actions

Copy link

Updated by Ernesto Baschny over 10 years ago

Status changed from Under Review to Accepted

Actions

Copy link

Updated by Gerrit Code Review over 10 years ago

Status changed from Accepted to Under Review

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28069

Actions

Copy link

Updated by Gerrit Code Review over 10 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28069

Actions

Copy link

Updated by Gerrit Code Review over 10 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/28069

Actions

Copy link

#10