code: public boolean getRenderHiddenMarkersBeforeCheckboxes() {
          final Set<IDialect> dialects = getDialects();
          for (final IDialect dialect : dialects) {
              if (dialect instanceof SpringStandardDialect) {
                  return ((SpringStandardDialect) dialect).getRenderHiddenMarkersBeforeCheckboxes();
              }
          }
          return false;
      }
docs: <p>
  Returns whether the {@code <input type="hidden" ...>} marker tags rendered to signal the presence
  of checkboxes in forms when unchecked should be rendered <em>before</em> the checkbox tag itself,
  or after (default).
  </p>
  <p>
  (This is just a convenience method, equivalent to calling
  {@link SpringStandardDialect#getRenderHiddenMarkersBeforeCheckboxes()} on the dialect instance
  itself. It is provided here in order to allow users to modify this behaviour without
  having to directly create instances of the {@link SpringStandardDialect})
  </p>
  <p>
  A number of CSS frameworks and style guides assume that the {@code <label ...>} for a checkbox
  will appear in markup just after the {@code <input type="checkbox" ...>} tag itself, and so the
  default behaviour of rendering an {@code <input type="hidden" ...>} after the checkbox can lead to
  bad application of styles. By tuning this flag, developers can modify this behaviour and make the hidden
  tag appear before the checkbox (and thus allow the lable to truly appear right after the checkbox).
  </p>
  <p>
  Note this hidden field is introduced in order to signal the existence of the field in the form being sent,
  even if the checkbox is unchecked (no URL parameter is added for unchecked check boxes).
  </p>
  <p>
  This flag is set to {@code false} by default.
  </p>
  
  @return {@code true} if hidden markers should be rendered before the checkboxes, {@code false} if not.
  
  @since 3.0.10