Project

General

Profile

Actions
Copy link

Bug #56418

closed

Missing margin/padding on content element fields

Added by Mathias Brodala about 10 years ago. Updated over 6 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 thClosed2014-03-23

Actions
Bug #56950: Additional margin on top of ExtJS context menusClosedErnesto Baschny2014-03-16

Actions

Related issues 2 (0 open — 2 closed)

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

Actions
Has duplicate TYPO3 Core - Bug #56567: Palette form fields have no left padding anymoreClosed2014-03-05

Actions
Actions
Copy link
 #1

Updated by Markus Klein about 10 years ago

  • Status changed from New to Accepted
  • Assignee set to Felix Kopp
  • Is Regression changed from Yes to No
Actions
Copy link
 #2

Updated by Mathias Brodala about 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
 #3

Updated by Markus Klein about 10 years ago

  • Is Regression changed from No to Yes

Of course it is, sorry for that.

Actions
Copy link
 #4

Updated by Ernesto Baschny about 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
 #5

Updated by Gerrit Code Review about 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
 #6

Updated by Ernesto Baschny about 10 years ago

  • Status changed from Under Review to Accepted
Actions
Copy link
 #7

Updated by Gerrit Code Review about 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
 #8

Updated by Gerrit Code Review about 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
 #9

Updated by Gerrit Code Review about 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

Updated by Felix Kopp about 10 years ago

  • Status changed from Under Review to Resolved
Actions
Copy link
 #11

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF