Viewing 3 replies - 16 through 18 (of 18 total)
  • Apparently the issue still persists on some configurations. I checked and is due to the fact that browser automatically adds attributes to the new “figure” element. Like this:

    figure {
        display: block;
        margin-block-start: 1em;
        margin-block-end: 1em;
        margin-inline-start: 40px;
        margin-inline-end: 40px;
    }

    The “figure” element appears to have the role of container or perhaps placeholder for the image, as the image is now lazy-loaded. At least that’s my theory.

    First I thought that there is a new option somewhere in the plugin’s settings page. I searched there but couldn’t “figure” it OUT.

    With version 3.0.5 installed, the problem is still there. Tried incognito. Decided not to fight with web server’s cache and throwed a new custom css rule to disable the margins.

    .crp_related figure {margin:0;}

    Anyways… it was ugly but fixable. Thanks for a great plugin otherwise.

    Plugin Author Ajay

    (@ajay)

    @wpsgas
    This CSS was implemented in the latest version of the plugin.

    I don’t think the browser implements its own CSS. But this is a common one that a lot of theme’s add which I hadn’t appreciated in previous versions.

    I wanted to share this fix worked for me too, and we don’t have any css defined for the figure tag FYI.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Missconfiguration of images’ is closed to new replies.