• S
    silvan

    At the moment the stacking order is as it is normal with HTML: following elements are on top of the elements before. So when using x-offset for an element, only elements that are an the right side of an other element or in the next row can be on top of other elements.

    It would be great, if the stacking order could be changed (for example in the context menu). I already tried setting a z-index on elements but this doesn't help since the rows have their own stacking context (I think). So maybe it's a bit tricky.

    But another way to do this would be swapping elements by using x-offset. So you put the element you want to be on top to the right, the other one to the left, and then change their position in the grid by setting an according x-offset. This does not work at the moment due to the bug report I filed concerning vw and percentage units for the offset. So maybe this puts a higher priority on the bug report. 🙂

    Thanks for listening to everything posted!

    posted in Feature Requests read more
  • S
    silvan

    Thank you Marius! It's a simple fix but it will break any previous set offsets…

    posted in Bug Reports read more
  • S
    silvan

    Thank you Marius!

    Sorry, my inner perfectionist is bothered when opening the source code in the browser… 🙂

    posted in Bug Reports read more
  • S
    silvan

    @silvan said in LayGridder's <noscript> tag impacts image search results with search engines:

    Somehow the <noscript> tag's content ends up in many (or all?) descriptions of image search results. Just search for images with the term made with LayGridder and you fill find images from pages that use LayGridder.

    I think this is neither user-friendly (the description is misleading when looking at image search results for some search term) nor an intended use of the <noscript> tag, as searching for the term laygridder should not bring up images from pages that just use the plugin and have nothing else to do with the plugin.

    I mean it should say "please turn on JavaScript to view this webpage" or something—which is not really better as a description for an image search result.

    Why is the <noscript> tag needed in the first place? The grid works perfectly for me without JavaScript.

    I guess this is related to this feature request.

    posted in Bug Reports read more
  • S
    silvan

    When using x- and y-offset to move an element around it says % as the unit in the popup. What is used in the actual CSS on the other hand (in the front- and in the backend) is vw.

    This causes two problems:

    • While resizing the window in the backend, the element that was moved using offset is changing its position, moving around in the grid, ignoring the columns. When changing the unit inside the translate() statement to percentage, it works perfectly.
    • The same happens on the frontend, as soon as you have the grid inside a container with a fixed or max-width. The grid with its columns uses the grid's container as reference (due to percentage units), while the elements with x- or y-offset use the viewport (due to vw units)—which in this case are not the same.

    posted in Bug Reports read more
  • S
    silvan

    Somehow the <noscript> tag's content ends up in many (or all?) descriptions of image search results. Just search for images with the term made with LayGridder and you fill find images from pages that use LayGridder.

    I think this is neither user-friendly (the description is misleading when looking at image search results for some search term) nor an intended use of the <noscript> tag, as searching for the term laygridder should not bring up images from pages that just use the plugin and have nothing else to do with the plugin.

    posted in Bug Reports read more
  • S
    silvan

    I don't know if it's possible, but at the moment any page of the Wordpress install has the LayGridder specific CSS styles in the <head> tag, which should only be the case on pages that actually use the plugin.

    Probably it's not a big performance issue, but it looks like “lazy” programming and clutters the <head> tag.

    You would somehow have to check beforehand if a grid will be used in the post.

    posted in Bug Reports read more
  • S
    silvan

    Thank you @hack_nug. I wont' use the plugin but the linked guide it is based on—didn't know it!

    posted in Feature Requests read more

Looks like your connection to LayGridder Forum was lost, please wait while we try to reconnect.