Twenty Fourteen: Be more specific with the transitions in CSS.

[georgestephanis]

Split out the CSS transition statements. Currently it targets

#page a,
.more-link .meta-nav,
.more-formatted-posts-link .meta-nav,
.attachment-featured-featured img,
.attachment-featured-thumbnail img,
.social-links-toggle,
.search-toggle,
button,
html input[type="button"],
input[type="reset"],
input[type="submit"],
#infinite-handle span

which is far too broad.

For the featured images, for example, if it's narrower than the area it's going to, you can see it expand on page load, which looks funky and moves the layout about a bit.

[celloexpressions]

Remove unneeded prefixes, unset transitions on more specific elements directly after setting them

[celloexpressions]

24881.diff removes unneeded prefixes (considering our timeline, we could probably also drop webkit, see ​http://caniuse.com/#feat=css-transitions). See #23582 for related discussion from Twenty Thirteen.

I think it might be best to remove transitions from more specific elements, or set them to only apply to certain properties, directly after setting transitions more broadly. There was one instance of removing the transitions; I moved that up to where the transitions are set.

[obenland]

For the featured images, for example, if it's narrower than the area it's going to

Can you elaborate more on this? What steps would I have to take to recreate this?

[lancewillett]

I'm also confused on this one. Is it in all browsers and platforms? Maybe a screencast would help.

[lancewillett]

George confirmed this is no longer an issue now that post thumbnails are no longer 100% width. ​Chat log.