Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misaligned legends in Duplicator #1205

Closed
nilshoerrmann opened this issue Mar 27, 2012 · 22 comments
Closed

Misaligned legends in Duplicator #1205

nilshoerrmann opened this issue Mar 27, 2012 · 22 comments
Labels
Milestone

Comments

@nilshoerrmann
Copy link
Contributor

This looks wrong:

Legends

@brendo
Copy link
Member

brendo commented Apr 3, 2012

Are you taking care of this one @nilshoerrmann?

@nilshoerrmann
Copy link
Contributor Author

If anyone else around could fix this, that would be great.

@brendo
Copy link
Member

brendo commented Apr 3, 2012

What should happen? The legend line up with the left edge of the field?

Is this only noticeable on the DateTime field?

@nilshoerrmann
Copy link
Contributor Author

It's a global issue – and yes the legend should line up.

@brendo
Copy link
Member

brendo commented Apr 4, 2012

Can you confirm if the above commit fixes the issue?

@brendo
Copy link
Member

brendo commented Apr 6, 2012

bump @nilshoerrmann

@nilshoerrmann
Copy link
Contributor Author

I can't confirm yet, because I haven't tested it yet :p
But I will have a look at it soon.

@brendo
Copy link
Member

brendo commented Apr 6, 2012

Ty :)

@nilshoerrmann
Copy link
Contributor Author

There still seem to be issues with the fieldset – I will have a look at it now.

@brendo
Copy link
Member

brendo commented Apr 6, 2012

I'm curious as how you are testing this?

I've been using the DateTime field on the Section Editor

@nilshoerrmann
Copy link
Contributor Author

I'm changing the markup in the Webkit inspector and I the legend is a few pixels off for me (to the left).

@brendo
Copy link
Member

brendo commented Apr 6, 2012

Must be a difference between Firefox and Webkit then ;)

edit, indeed it is. padding: .5em; fixes Webkit, but indents Firefox. padding-left: 0 pulls the Webkit indent back, but in Firefox it aligns. Fun times!

@nilshoerrmann
Copy link
Contributor Author

Only if Firefox doesn't apply the margin-left: -0.5em definition in admin.css ;)

@brendo
Copy link
Member

brendo commented Apr 6, 2012

Yet margin-left: -0.5em is required for Webkit's fix. Haha

@brendo
Copy link
Member

brendo commented Apr 6, 2012

Setting padding: 0; margin: 0 actually seems to resolve it in both Firefox and Webkit

@nilshoerrmann
Copy link
Contributor Author

No, no! We need the margin in the preferences. It should be padding-left: 0.5em, see: 6e98ff4#L0R381

@brendo
Copy link
Member

brendo commented Apr 6, 2012

Setting padding-left: 0.5em will resolve the alignment issue in Webkit, but it will break the alignment in Firefox.

You mentioned removing margin-left: -0.5em will fix Firefox, but doing this then breaks Webkit again.

Heh, I'm confused.

@nilshoerrmann
Copy link
Contributor Author

Damn. We should deprecate the usage of Firefox in connection with Symphony. I only know of a single developer using it …

@brendo
Copy link
Member

brendo commented Apr 6, 2012

Where is that margin required for Preferences? From what I can see legends on the Preferences page are absolutely positioned and won't be affected by this change as we are only applying it from within .collapsible context?

@nilshoerrmann
Copy link
Contributor Author

You are right, it was required but has since been changed.

The problematic rule is fieldset.settings fieldset legend on line 338 of admin.css. But I think we can safely remove margin and padding settings there.

@brendo brendo closed this as completed in 9cc9993 Apr 6, 2012
@brendo
Copy link
Member

brendo commented Apr 6, 2012

Looks like it! Teamwork. Thanks :)

@nilshoerrmann
Copy link
Contributor Author

:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants