Twenty Sixteen: Margin error with Portfolio and no widgets

[ashercantrell]

Using Portfolio projects in Twenty Sixteen on a site with no widgets in the sidebar leads to some strange margin issues. There's a lot of white space to the side of the content, making the text start nearly in the center, like this:

If you inspect the area, you can see some very odd margins in the CSS:

If that's difficult to read, it says there's a 389.141 left margin and a -1111.840 right margin, which is causing the unusual white space.

I did find a workaround: Adding any sidebar widgets, including a blank text widget, will correct the margin issue:

The margins with the widget(s) in place look like this:

[davidakennedy]

Created an issue here where Twenty Sixteen is maintained: ​https://github.com/WordPress/twentysixteen/issues/494

[SergeyBiryukov]

Reopening, as Twenty Sixteen was merged into core SVN in #36497.

[laurelfulford]

I can recreate a similar issue with another plugin that creates custom post types (Events Manager).

A note from the GitHub issue about the second screenshot:

If that's difficult to read, it says there's a 389.141 left margin and a -1111.840 right margin, which is causing the unusual white space.

This looks like the styles that are used on regular posts, to create space for the post meta.

A better style for all non-post post types may have been to follow pages, which centre the title above the content. But I'm not sure how big of an issue this is, and if switching it now could cause other issues (whether that be with existing CPTs, or just causing unexpected behaviour with child themes/custom CSS).

I'm inclined to wontfix at this point, but am open to more discussion!

@davidakennedy I'd appreciate your thoughts on this one!

[ianbelanger]

I tend to agree with @laurelfulford on this one. The margins mentioned 389.141 left margin, -1111.840 right margin are not much different than the margins in a post - 420px left margin, -1200px right margin

I am going to close this as a wontfix

@ashercantrell if you feel strongly that this should be fixed, please feel free to reopen this ticket and state your case.