pigdog234

Yes that does a nice job of it. Should I mark this resolved or leave it for the twentysixteen people to sort a bit more?

Following up on this, I did exactly as stephencottontail suggested by creating a child theme.

There was exactly one more gotcha. If like me you are an old fogie and like to use bookmarkify, you will have to make a change to bookmarkify itself because twentysixteen’s CSS prefers “display: block” and bookmarkify relies on “display: inline”. Otherwise you get a vertical listing of the images.

Unfortunately bookmarkify hasn’t been touched in a long time, but I’ll post a quick diff here and see if I can goad the author into accepting it.

diff -c bookmarkify.php~ bookmarkify.php
*** bookmarkify.php~	Sun Sep  5 13:43:33 2010
--- bookmarkify.php	Fri Feb  5 11:22:38 2016
***************
*** 602,608 ****
  				else
  				{
  					$d.= "<a href='".$link[2]."' title='".$link[1]."' onclick='target=\"".$bookmarkifyLinkTarget."\";' rel='nofollow'>"
! 							. "<img src='".$iconFolder."/".$link[3]."' style='width:16px; height:16px;' alt='[".$link[0]."] ' $endTag>"
  							. "</a> ";
  				}
  			}
--- 602,608 ----
  				else
  				{
  					$d.= "<a href='".$link[2]."' title='".$link[1]."' onclick='target=\"".$bookmarkifyLinkTarget."\";' rel='nofollow'>"
! 							. "<img src='".$iconFolder."/".$link[3]."' style='width:16px; height:16px; display: inline' alt='[".$link[0]."] ' $endTag>"
  							. "</a> ";
  				}
  			}

Thanks for tracking down the CSS, stephencottontail. It’d be good if the developers could explain their reasoning. I guess at this point because the theme is out there it will not be changed in any significant way.

So I did a bit of looking. The theme is adding a callout:
twentysixteen_widget_tag_cloud_args in functions.php, which is causing part of the problem. There’s also a CSS problem, but I haven’t isolated it.

Hi,

Thank you very much, @namklim, for your response. I do note that the bug I experienced related to height: auto. I see that the issue seems to be a compatibility problem with IE8, but is that confirmed?

Thanks!